From: "John W. Linville" <linville@tuxdriver.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Luis Carlos Cobo <luisca@cozybit.com>,
linux-wireless@vger.kernel.org,
Stefano Brivio <stefano.brivio@polimi.it>
Subject: Re: [PATCH 00/13 v2] o11s: mesh interface support for mac80211
Date: Fri, 22 Feb 2008 10:59:51 -0500 [thread overview]
Message-ID: <20080222155951.GE3067@tuxdriver.com> (raw)
In-Reply-To: <1203693709.7082.35.camel@johannes.berg>
On Fri, Feb 22, 2008 at 04:21:49PM +0100, Johannes Berg wrote:
> > The patches are to be applied on top of wireless-2.6/everything HEAD. Even
> > though I am sure there will be some issues, it would be great if we could
> > integrate this as soon as possible to make it easier for other people to
> > collaborate and to make my life a bit easier :-)
>
> Hm. I think you'd have to rebase on top of wireless-testing/master but
> I'm not sure how they currently differ. See John Linville's mail on the
> new tree structure.
They were euivalent until day before yesterday. No
wireless-2.6/everything is gone and wireless-testing/master has
progressed. Please use wireless-testing/master for any future patches.
Thanks,
John
--
John W. Linville
linville@tuxdriver.com
next prev parent reply other threads:[~2008-02-22 16:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-22 4:05 [PATCH 00/13 v2] o11s: mesh interface support for mac80211 Luis Carlos Cobo
2008-02-22 15:21 ` Johannes Berg
2008-02-22 15:59 ` John W. Linville [this message]
2008-02-22 16:34 ` Johannes Berg
2008-02-23 10:58 ` Johannes Berg
2008-02-25 19:47 ` Luis Carlos Cobo
2008-02-25 19:45 ` Luis Carlos Cobo
2008-02-25 19:50 ` Johannes Berg
2008-02-26 1:03 ` David Woodhouse
2008-02-26 8:22 ` Johannes Berg
-- strict thread matches above, loose matches on Subject: below --
2008-02-22 4:05 Luis Carlos Cobo
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=20080222155951.GE3067@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=luisca@cozybit.com \
--cc=stefano.brivio@polimi.it \
/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).