From: "John W. Linville" <linville@tuxdriver.com>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: pull request: wireless-next-2.6 2008-06-13
Date: Fri, 13 Jun 2008 23:21:16 -0400 [thread overview]
Message-ID: <20080614032116.GA9171@tuxdriver.com> (raw)
In-Reply-To: <20080613214114.GA1077@tuxdriver.com>
On Fri, Jun 13, 2008 at 05:41:14PM -0400, John W. Linville wrote:
> Another slew of updates intended for 2.6.27...please let me know if
> there are problems!
If you are not in a hurry, you may want to delay this one. One of
the mac80211 cleanup patches has a one-line endian problem. Beer and
fatigue suggest that I should look at reworking the tree tomorrow
instead of now.
Thanks,
John
--
John W. Linville
linville@tuxdriver.com
next prev parent reply other threads:[~2008-06-14 3:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-13 21:41 pull request: wireless-next-2.6 2008-06-13 John W. Linville
2008-06-13 21:41 ` John W. Linville
2008-06-14 3:21 ` John W. Linville [this message]
2008-06-14 3:47 ` David Miller
2008-06-14 17:45 ` pull request: wireless-next-2.6 2008-06-14 John W. Linville
2008-06-14 17:45 ` John W. Linville
2008-06-15 0:32 ` David Miller
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=20080614032116.GA9171@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=davem@davemloft.net \
--cc=linux-wireless@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.