From: "Tomas Winkler" <tomasw@gmail.com>
To: "David Miller" <davem@davemloft.net>
Cc: linville@tuxdriver.com, netdev@vger.kernel.org,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: pull request: wireless-next-2.6 2008-07-02
Date: Sun, 6 Jul 2008 10:07:42 +0300 [thread overview]
Message-ID: <1ba2fa240807060007i572d054va60aa16b41cadce3@mail.gmail.com> (raw)
In-Reply-To: <20080705.214752.85024966.davem@davemloft.net>
On Sun, Jul 6, 2008 at 7:47 AM, David Miller <davem@davemloft.net> wrote:
> From: "John W. Linville" <linville@tuxdriver.com>
> Date: Wed, 2 Jul 2008 16:26:53 -0400
>
>> Here is another slew of updates for 2.6.27. The bulk of this batch is
>> for iwlwifi, with some mac80211 and other bits thrown-in.
>>
>> Let me know if there are problems!
>
> Pulled and pushed back out to net-next-2.6, thanks.
>
> Here are some warnings I noticed during an allmodconfig build
> on sparc64, please fix:
>
> drivers/net/wireless/hostap/hostap_hw.c:3422: warning: 'prism2_suspend' defined but not used
> drivers/net/wireless/iwlwifi/iwl-rfkill.c:114: warning: label 'freed_rfkill' defined but not used
John what happened to to those patches?
http://marc.info/?l=linux-wireless&m=121489830307988&w=2
http://marc.info/?l=linux-wireless&m=121481826531792&w=2
Thanks
Tomas
next prev parent reply other threads:[~2008-07-06 7:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-30 21:56 pull request: wireless-next-2.6 2008-06-30 John W. Linville
2008-07-02 19:37 ` John W. Linville
2008-07-02 20:24 ` David Miller
2008-07-02 20:26 ` pull request: wireless-next-2.6 2008-07-02 John W. Linville
2008-07-02 21:33 ` David Miller
2008-07-06 4:47 ` David Miller
2008-07-06 7:07 ` Tomas Winkler [this message]
2008-07-07 13:15 ` John W. Linville
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=1ba2fa240807060007i572d054va60aa16b41cadce3@mail.gmail.com \
--to=tomasw@gmail.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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
all inboxes | Powered by JetHome®