LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: James Ketrenos <jketreno@linux.intel.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Pavel Machek <pavel@ucw.cz>,
	linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
	ipw3945-devel@lists.sourceforge.net, netdev@vger.kernel.org
Subject: Re: [ANNOUNCE] d80211 based driver for Intel PRO/Wireless 3945ABG
Date: Tue, 13 Feb 2007 15:18:24 -0800	[thread overview]
Message-ID: <45D24740.3070804@linux.intel.com> (raw)
In-Reply-To: <1171391771.10344.93.camel@johannes.berg>

Johannes Berg wrote:
> On Tue, 2007-02-13 at 18:13 +0000, Pavel Machek wrote:
> 
>> Yes... is there merged .git tree somewhere? I downloaded iwl git tree,
>> but it did not contain d80211 stack. I'm now downloading wireless-dev
>> git tree...
> 
> I would expect Intel to post patches some time soon to get into
> wireless-dev.
> 
> johannes

Some of the patches contained in the d80211-1.0.1 'pending/' directory 
have already been submitted to netdev in the past.  The rest will be 
submitted soon (I would have liked them to have been submitted a few 
weeks back, but that slipped through my task list)

The d80211 packages I've pushed to date haven't done a very good job of 
accounting regarding the pending/ directory.  Those were the patches our 
team here had been working with internally, and I wanted to get them out 
to the users ASAP.  I'm working to get better descriptions added to the 
headers of those patches, as well as adding a status line indicating 
when the patches were submitted to the mailing lists for discussion.

The goal is to only include patches in the d80211 tarballs which have 
been submitted for eventual in-tree inclusion.

James

  reply	other threads:[~2007-02-14  0:00 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-09 21:12 James Ketrenos
2007-02-09 22:14 ` Alon Bar-Lev
2007-02-09 22:26 ` Neil Brown
2007-02-09 21:52   ` James Ketrenos
2007-02-10  3:26     ` Nick Kossifidis
2007-02-09 22:37   ` Stefan Schmidt
2007-02-10  0:46 ` [ipw3945-devel] " Norbert Preining
2007-02-13 23:23   ` James Ketrenos
2007-02-10 13:23 ` Hesse, Christian
2007-02-10 14:25   ` Hesse, Christian
2007-02-12 16:32     ` [ipw3945-devel] " dragoran
2007-02-12 18:35     ` James Ketrenos
2007-02-11 13:19   ` Johannes Berg
2007-02-10 16:22 ` Theodore Tso
2007-02-10 16:39   ` John W. Linville
2007-02-10 17:53     ` [ipw3945-devel] " Pavel Roskin
2007-02-10 22:41       ` John W. Linville
2007-02-10 18:42   ` Michael Buesch
2007-02-13 13:58 ` Ismail Dönmez
2007-02-13 15:10   ` Jeff Chua
2007-02-13 16:57     ` Ismail Dönmez
2007-02-13 22:55       ` James Ketrenos
2007-02-13 18:13 ` Pavel Machek
2007-02-13 18:36   ` Johannes Berg
2007-02-13 23:18     ` James Ketrenos [this message]
2007-02-14  0:16   ` [ipw3945-devel] " James Ketrenos
2007-02-19 22:44     ` Pavel Machek
2007-02-21  6:23       ` iwlwifi warnings Stephen Hemminger
2007-02-21  7:32         ` Randy Dunlap
2007-02-21 19:38         ` Pavel Machek

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=45D24740.3070804@linux.intel.com \
    --to=jketreno@linux.intel.com \
    --cc=ipw3945-devel@lists.sourceforge.net \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --subject='Re: [ANNOUNCE] d80211 based driver for Intel PRO/Wireless 3945ABG' \
    /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

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).