linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ivo van Doorn <ivdoorn@gmail.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: rt2400-devel@lists.sourceforge.net, linux-wireless@vger.kernel.org
Subject: Re: rt2x00 updated in wireless-dev
Date: Fri, 2 Mar 2007 17:21:50 +0100	[thread overview]
Message-ID: <200703021721.50283.IvDoorn@gmail.com> (raw)
In-Reply-To: <20070302153116.GC6676@tuxdriver.com>

On Friday 02 March 2007 16:31, John W. Linville wrote:
> I have applied the 30 or so patches Ivo sent to the linux-wireless
> list a couple of days ago. 

Thanks!

> Hopefully that brings the rt2x00 driver 
> in wireless-dev almost up-to-date?

Well the only patches that are not in are:
	- development stuff of today, which is still a bit buggy and not completed
	- software sequence support for rt2400pci/rt2500pci,
	  but that depends on the mac80211 patch that had been send earlier.
	- rfkill support patch. The last RFC I had send
	  out has not yet been replied, although Dmitry has send me a message
          he has seen the mail and will reply as soon as he has time.

> Via wireless-dev, the rt2x00 driver family is now in -mm and in
> Fedora rawhide, possibly elsewhere.  I think it will be best for all
> concerned to keep wireless-dev closely synchronized with rt2x00 fixes
> and developments.  I hope you agree.

I absolutely agree, unfortunately lack of time on my side prevented me often
to create those regular patches, although that is just a weak excuse since
I had made enough patches into rt2x00. ;)

> Ivo seems to have (almost!) mastered the patch posting process for
> upstream.  His last round of patches were easy to handle and merge.
> They would have been merged faster, if there weren't so many of them
> all at once.  A higher frequency of patches posted to linux-wireless
> will continue to improve the merge delay upstream.

Well like I mentioned in the patch mail, I have experimented a bit with git
this time. So hopefully there will be a git tree within a few weeks from where
you can pull new updates. :)

> The rt2x00 project is important to the upstream community, and hence
> to all the distros and their users.  I appreciate and applaud your
> efforts in bringing the rt2x00 driver family this far.  I hope you
> will now take the opportunity to more closely integrate your efforts
> with those of the greater linux-wireless community.

I'll do my best. :)

Ivo

      reply	other threads:[~2007-03-02 16:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-02 15:31 rt2x00 updated in wireless-dev John W. Linville
2007-03-02 16:21 ` Ivo van Doorn [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=200703021721.50283.IvDoorn@gmail.com \
    --to=ivdoorn@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=rt2400-devel@lists.sourceforge.net \
    /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).