netdev - Re: d80211-drivers updated (zd1211rw-d80211 synced with zd1211rw)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <200612040920.11583.flamingice@sourmilk.net>
Date:	Mon, 4 Dec 2006 09:20:07 -0500
From:	Michael Wu <flamingice@...rmilk.net>
To:	"John W. Linville" <linville@...driver.com>
Cc:	Daniel Drake <dsd@...too.org>, Ulrich Kunitz <kune@...ne-taler.de>,
	netdev@...r.kernel.org
Subject: Re: d80211-drivers updated (zd1211rw-d80211 synced with zd1211rw)

On Monday 04 December 2006 07:51, John W. Linville wrote:
> On Mon, Dec 04, 2006 at 02:50:39AM -0500, Michael Wu wrote:
> > Other (d80211) wireless drivers are welcome
> > to send patches this way if they do not have their own git tree for
> > Linville to pull.
>
> Please don't do this.  It adds to my pain for reviewing patches.
>
Sure.

> While I'm complaining :-), I would probably prefer it if you had
> adm8211 and p54 in separate git trees (or at least on separate
> branches) as well.  That way, if there is a problem in a p54 patch
> series, I can still pull adm8211 (or vice versa).
>
I will keep separate branches for each driver then.

> It is not my intent to scold (so please don't feel scolded).  It just
> is counter-productive to prematurely consolidate merging duties.
>
No problem. It seemed like a good idea for zd1211rw, so I was offering to do 
the same for other drivers.

Thanks,
-Michael Wu

Content of type "application/pgp-signature" skipped