From: David Kimdon <david.kimdon@devicescape.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Jeff Garzik <jeff@garzik.org>,
David Kimdon <david.kimdon@devicescape.com>,
netdev@vger.kernel.org, Jiri Benc <jbenc@suse.cz>
Subject: Re: [take3 0/5] d80211: remove bitfields from include/net/d80211.h
Date: Wed, 8 Nov 2006 07:39:44 -0800 [thread overview]
Message-ID: <20061108153944.GA26557@devicescape.com> (raw)
In-Reply-To: <20061103033049.GD2989@tuxdriver.com>
On Thu, Nov 02, 2006 at 10:30:56PM -0500, John W. Linville wrote:
> David, may I presume there will be a "take4"?
yes, refreshing is in progress.
prev parent reply other threads:[~2006-11-08 15:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-25 18:42 [take3 0/5] d80211: remove bitfields from include/net/d80211.h David Kimdon
2006-10-25 19:01 ` Jeff Garzik
2006-10-25 19:17 ` David Kimdon
2006-10-25 19:28 ` Jeff Garzik
2006-11-03 3:30 ` John W. Linville
2006-11-08 15:39 ` David Kimdon [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=20061108153944.GA26557@devicescape.com \
--to=david.kimdon@devicescape.com \
--cc=jbenc@suse.cz \
--cc=jeff@garzik.org \
--cc=linville@tuxdriver.com \
--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).