From: "John W. Linville" <linville@tuxdriver•com>
To: Ken Lewis <kennylewis@gmail•com>
Cc: linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>,
netdev <netdev@vger•kernel.org>
Subject: Re: PATCH 0/1: rt2x00dev.c / rt2x00lib.h fixes build breakage
Date: Fri, 25 Sep 2009 00:53:17 -0400 [thread overview]
Message-ID: <20090925045316.GB2722@tuxdriver.com> (raw)
In-Reply-To: <5a44caba0909231358y23f21c0drb2a3451084028a6f@mail.gmail.com>
On Wed, Sep 23, 2009 at 09:58:35PM +0100, Ken Lewis wrote:
> The headers in drivers/net/wireless/rt2x00/rt2x00lib.h don't match the
> use of the function in rt2x00dev.c The build fails as a result.
>
> This has been a problem in linux-next since early September. I've
> e-mailed a patch to linux-next and to linux-net, but the 2.6.32 merge
> window has brought the problem to the mainline and so I'm re-sending
> my patch. I've opened a bug on bugzilla:
> http://bugzilla.kernel.org/show_bug.cgi?id=14217
Always make sure to send wireless LAN patches to
linux-wireless@vger•kernel.org. Anyway, the following patch is in
the pull request I sent to Dave yesterday (and which I believe he
has already pulled):
commit fe2475633676b0a976400dfc53f8d7006f56543e
Author: Andrew Price <andy@andrewprice•me.uk>
Date: Thu Sep 17 21:15:48 2009 +0100
rt2x00: fix the definition of rt2x00crypto_rx_insert_iv
Remove the redundant l2pad parameter from the definition of
rt2x00crypto_rx_insert_iv which is used when only CONFIG_RT2500PCI but
none of the other rt2x00 family drivers is configured.
Signed-off-by: Andrew Price <andy@andrewprice•me.uk>
Signed-off-by: John W. Linville <linville@tuxdriver•com>
Hth!
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver•com might be all we have. Be ready.
prev parent reply other threads:[~2009-09-25 4:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-23 20:58 PATCH 0/1: rt2x00dev.c / rt2x00lib.h fixes build breakage Ken Lewis
2009-09-25 4:53 ` John W. Linville [this message]
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=20090925045316.GB2722@tuxdriver.com \
--to=linville@tuxdriver$(echo .)com \
--cc=kennylewis@gmail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--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