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 2010-03-12
Date: Fri, 12 Mar 2010 12:36:47 -0800 (PST) [thread overview]
Message-ID: <20100312.123647.91351325.davem@davemloft.net> (raw)
In-Reply-To: <20100312202848.GC17689@tuxdriver.com>
From: "John W. Linville" <linville@tuxdriver.com>
Date: Fri, 12 Mar 2010 15:28:48 -0500
> Here is a round of fixes intended for 2.6.34. I don't think there is
> anything controversial here -- they are all reasonably small, targeted,
> and are fixes to real problems. I believe they are all well represented
> by their changelog entries as well.
>
> Please let me know if there are problems!
Thanks John.
I'll pull this in after Linus pulls in my most recent
pull request, in order to avoid confusion.
prev parent reply other threads:[~2010-03-12 20:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-12 20:28 pull request: wireless-2.6 2010-03-12 John W. Linville
2010-03-12 20: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=20100312.123647.91351325.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).