From: David Miller <davem@davemloft.net>
To: linville@tuxdriver.com
Cc: linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: pull request: wireless-2.6 2009-07-29
Date: Thu, 30 Jul 2009 10:36:22 -0700 (PDT) [thread overview]
Message-ID: <20090730.103622.35100964.davem@davemloft.net> (raw)
In-Reply-To: <20090729203007.GB10056@tuxdriver.com>
From: "John W. Linville" <linville@tuxdriver.com>
Date: Wed, 29 Jul 2009 16:30:07 -0400
> Here is a small collection of fixes intended for 2.6.31. Several of
> them are small fixes dug-out by the usual static analysis suspects.
> There are also a couple of iwlwifi fixes that the Intel team thinks are
> important -- they look reasonably safe to me and they should only effect
> their drivers. Their are also some small fixes from Luis and Johannes.
Pulled, thanks John.
prev parent reply other threads:[~2009-07-30 17:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-29 20:30 pull request: wireless-2.6 2009-07-29 John W. Linville
2009-07-30 17:36 ` 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=20090730.103622.35100964.davem@davemloft.net \
--to=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;
as well as URLs for NNTP newsgroup(s).