From: Christoph Hellwig <hch@infradead.org>
To: Michael Buesch <mb@bu3sch.de>
Cc: Jiri Benc <jbenc@suse.cz>,
"John W. Linville" <linville@tuxdriver.com>,
netdev@vger.kernel.org
Subject: Re: d80211 merge plans
Date: Wed, 9 Aug 2006 10:16:29 +0100 [thread overview]
Message-ID: <20060809091629.GA31005@infradead.org> (raw)
In-Reply-To: <200608090703.45651.mb@bu3sch.de>
On Wed, Aug 09, 2006 at 07:03:41AM +0200, Michael Buesch wrote:
> Hi,
>
> I am wondering about d80211 mainline merge plans.
http://marc.theaimsgroup.com/?l=linux-netdev&m=115477844206917&w=2
has the highlevel merge requirement. Only mentioned there as a side-note
we'll of course need a full codereview like the one Jeff is doing now.
prev parent reply other threads:[~2006-08-09 9:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-09 5:03 d80211 merge plans Michael Buesch
2006-08-09 5:40 ` Jeff Garzik
2006-08-09 14:37 ` Dan Williams
2006-08-09 20:47 ` Jouni Malinen
2006-08-09 5:48 ` David Miller
2006-08-09 8:19 ` Ivo Van Doorn
2006-08-09 20:09 ` Mohamed Abbas
2006-08-10 6:11 ` Jeff Garzik
2006-08-09 9:16 ` Christoph Hellwig [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=20060809091629.GA31005@infradead.org \
--to=hch@infradead.org \
--cc=jbenc@suse.cz \
--cc=linville@tuxdriver.com \
--cc=mb@bu3sch.de \
--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).