From: "Guy, Wey-Yi" <wey-yi.w.guy@intel.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: wireless-next-2.6 rebased from b4e69ac670d71b5748dc81e536b2cb103489badd
Date: Thu, 27 Jan 2011 13:29:02 -0800 [thread overview]
Message-ID: <1296163742.27623.0.camel@wwguy-huron> (raw)
In-Reply-To: <20110127210953.GB2271@tuxdriver.com>
On Thu, 2011-01-27 at 13:09 -0800, John W. Linville wrote:
> I rebased wireless-next-2.6 to drop a patch that I should have merged
> through the fixes track. I just merged it yesterday, so if you haven't
> pulled in the last day or so (i.e. you don't have anything beyond
> commit b4e69ac670d71b5748dc81e536b2cb103489badd) you should be fine.
>
> Otherwise, I apologize for the inconvenience to Gustavo, Luca, Wey-yi,
> and whomever else might be following wireless-next-2.6 directly.
>
Thanks to let me know :-)
Wey
prev parent reply other threads:[~2011-01-27 21:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-27 21:09 wireless-next-2.6 rebased from b4e69ac670d71b5748dc81e536b2cb103489badd John W. Linville
2011-01-27 21:29 ` Guy, Wey-Yi [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=1296163742.27623.0.camel@wwguy-huron \
--to=wey-yi.w.guy@intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/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).