From: David Miller <davem@davemloft.net>
To: linville@tuxdriver.com
Cc: linux-wireless@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: pull request: wireless-next-2.6 2008-10-31
Date: Fri, 31 Oct 2008 17:03:58 -0700 (PDT) [thread overview]
Message-ID: <20081031.170358.188963325.davem@davemloft.net> (raw)
In-Reply-To: <20081031233735.GH4310@tuxdriver.com>
From: "John W. Linville" <linville@tuxdriver.com>
Date: Fri, 31 Oct 2008 19:37:35 -0400
> Here is a spooky Halloween pull request for wireless bits intended for
> 2.6.29 -- Boo! Are you scared?
Best pull request ever :-)
> There is a ton of stuff here. The good news is that it has been cooking
> in wireless-testing for a while and it seems OK. :-) There are some
> warning in the build like "‘__IEEE80211_CONF_SHORT_SLOT_TIME’ is
> deprecated". Don't worry, I already have more patches cooking in
> wireless-testing that will take care of those warnings in the next
> round.
>
> Please let me know if there are problems!
Pulled, thanks a lot!
prev parent reply other threads:[~2008-11-01 0:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-31 23:37 pull request: wireless-next-2.6 2008-10-31 John W. Linville
2008-11-01 0:03 ` David Miller [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=20081031.170358.188963325.davem@davemloft.net \
--to=davem@davemloft.net \
--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;
as well as URLs for NNTP newsgroup(s).