From: "John W. Linville" <linville@tuxdriver.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Jiri Pirko <jpirko@redhat.com>, Netdev <netdev@vger.kernel.org>,
linux-wireless <linux-wireless@vger.kernel.org>,
davem <davem@davemloft.net>
Subject: Re: [RFC] net: refactor multicast/unicast address list
Date: Wed, 17 Jun 2009 08:26:16 -0400 [thread overview]
Message-ID: <20090617122616.GB2791@tuxdriver.com> (raw)
In-Reply-To: <1245231024.19769.0.camel@johannes.local>
On Wed, Jun 17, 2009 at 11:30:24AM +0200, Johannes Berg wrote:
> On Wed, 2009-06-17 at 09:21 +0200, Jiri Pirko wrote:
>
> > >I guess we could stick this one into wireless-testing, and then take it
> > >out again once your patch hits the tree and offers me similar API for
> > >list_head based multicast lists?
> >
> > Or wait, I hope the patch will be ready in week tops.
>
> Yeah, that's fine, I'll ask people to throw in the simple export patch
> for testing. Thanks for considering! Please disregard my work on
> mac80211, I'll rebase over your work.
If you need Jiri's patch in wireless-testing I can make arrangements
to cherry-pick it.
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2009-06-17 12:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1244889678.13033.6.camel@johannes.local>
[not found] ` <1244896094.13033.8.camel@johannes.local>
[not found] ` <20090616111842.GG3521@psychotron.englab.brq.redhat.com>
[not found] ` <1245151771.9256.3.camel@johannes.local>
[not found] ` <20090616123808.GK3521@psychotron.englab.brq.redhat.com>
2009-06-16 23:09 ` [RFC] net: refactor multicast/unicast address list Johannes Berg
2009-06-16 23:19 ` Johannes Berg
2009-06-17 7:21 ` Jiri Pirko
2009-06-17 9:30 ` Johannes Berg
2009-06-17 12:26 ` John W. Linville [this message]
2009-06-17 12:58 ` Johannes Berg
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=20090617122616.GB2791@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=davem@davemloft.net \
--cc=johannes@sipsolutions.net \
--cc=jpirko@redhat.com \
--cc=linux-wireless@vger.kernel.org \
--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).