From: Stephen Rothwell <sfr@canb•auug.org.au>
To: David Miller <davem@davemloft•net>, netdev@vger•kernel.org
Cc: "John W. Linville" <linville@tuxdriver•com>,
LKML <linux-kernel@vger•kernel.org>,
linux-next@vger•kernel.org
Subject: Re: [PATCH] ar9170: fix for driver-core ABI change
Date: Tue, 9 Mar 2010 12:52:45 +1100 [thread overview]
Message-ID: <20100309125245.c25e5ca4.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20100309104221.aedc5e7e.sfr@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 965 bytes --]
Hi Dave,
On Tue, 9 Mar 2010 10:42:21 +1100 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>
> Signed-off-by: Stephen Rothwell <sfr@canb•auug.org.au>
> ---
> drivers/net/wireless/ath/ar9170/usb.c | 5 +++--
> 1 files changed, 3 insertions(+), 2 deletions(-)
>
> I have been carrying this patch in linux-next for some time as a fixup
> for the driver-core tree. It is now needed in net-2.6 (i.e. my
> net-current) (since you merged the wireless tree) *after* you merge with
> Linus' tree i.e. the down()/up() are present in the net-2.6 tree and the
> changes to the driver core to use mutexes are in Linus' tree.
Greg tells me that the semaphore to mutex change didn't go into Linus'
tree. However, this patch can still be applied as the device_lock/unlock
primitives did go in. I guess that the include of mutex.h is not needed.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-03-09 1:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-08 23:42 [PATCH] ar9170: fix for driver-core ABI change Stephen Rothwell
2010-03-09 1:52 ` Stephen Rothwell [this message]
2010-03-09 18:00 ` Stefan Richter
2010-03-09 22:08 ` Stephen Rothwell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100309125245.c25e5ca4.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=davem@davemloft$(echo .)net \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linville@tuxdriver$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox