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-06
Date: Tue, 07 Oct 2008 16:28:57 -0700 (PDT) [thread overview]
Message-ID: <20081007.162857.183096613.davem@davemloft.net> (raw)
In-Reply-To: <20081007030013.GQ3448@tuxdriver.com>
From: "John W. Linville" <linville@tuxdriver.com>
Date: Mon, 6 Oct 2008 23:00:23 -0400
> Here is the latest round of wireless updates intended for 2.6.28. There
> are a couple of merge damage fixups, a new rate scaling algorithm for
> mac80211, and some miscellaneous drivers fixes and such.
>
> Let me know if there are problems!
Applied, thanks John.
I'll push this out to net-next-2.6 after some build testing.
prev parent reply other threads:[~2008-10-07 23:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-07 3:00 pull request: wireless-next-2.6 2008-10-06 John W. Linville
2008-10-07 23:28 ` 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=20081007.162857.183096613.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).