From: "John W. Linville" <linville@tuxdriver.com>
To: linux-wireless@vger.kernel.org
Subject: Re: wireless-next rebased from 94c514fe
Date: Tue, 8 May 2012 22:52:09 -0400 [thread overview]
Message-ID: <20120509025208.GA15753@tuxdriver.com> (raw)
In-Reply-To: <20120509024300.GC2533@tuxdriver.com>
On Tue, May 08, 2012 at 10:43:01PM -0400, John W. Linville wrote:
> Regrettably, I found it necessary to rebase the wireless-next tree
> starting from commit 94c514fe. If you maintain a tree derived from
> wireless-next then you may need to adjust your tree accordingly.
>
> I apologize for the inconvenience!
I should note that I pulled back from net-next into wireless-next as
part of this process. This was necessary to resolve some continuing
merge issues related to the NLA_PUT_* removal. This also means that
net-next bits have made their way into wireless-testing much earlier
than they usually would have done so.
Again, I apologize for the inconvenience and/or confusion that this
might cause. Please bear through this with me.
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
prev parent reply other threads:[~2012-05-09 2:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-09 2:43 wireless-next rebased from 94c514fe John W. Linville
2012-05-09 2:52 ` John W. Linville [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=20120509025208.GA15753@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=linux-wireless@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).