From: David Miller <davem@davemloft.net>
To: mb@bu3sch.de
Cc: jbenc@suse.cz, linville@tuxdriver.com, netdev@vger.kernel.org
Subject: Re: d80211 merge plans
Date: Tue, 08 Aug 2006 22:48:38 -0700 (PDT) [thread overview]
Message-ID: <20060808.224838.41637123.davem@davemloft.net> (raw)
In-Reply-To: <200608090703.45651.mb@bu3sch.de>
From: Michael Buesch <mb@bu3sch.de>
Date: Wed, 9 Aug 2006 07:03:41 +0200
> I am wondering about d80211 mainline merge plans.
I think this is a non-started until the SMP problems are worked
out. Is it still SMP challenged?
next prev parent reply other threads:[~2006-08-09 5:48 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 [this message]
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
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=20060808.224838.41637123.davem@davemloft.net \
--to=davem@davemloft.net \
--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).