netdev - Re: [PATCH 0/15] spidernet driver bug fixes

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] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 13 Jun 2007 23:53:18 +1000
From:	Michael Ellerman <michael@...erman.id.au>
To:	Jeff Garzik <jeff@...zik.org>
Cc:	Linas Vepstas <linas@...tin.ibm.com>, netdev@...r.kernel.org,
	cbe-oss-dev@...abs.org
Subject: Re: [PATCH 0/15] spidernet driver bug fixes

On Tue, 2007-06-12 at 21:54 -0400, Jeff Garzik wrote:
> Michael Ellerman wrote:
> > Linas posted the patches, I responded querying whether the bug fixes
> > should go into 2.6.22, and then you told him "you need to order your bug
> > fixes first in the queue". Which seemed pretty clear to me that you'd
> > wait for the reordered series.
> 
> This was presuming Linas actually knew what he himself had submitted 
> previously, and had been accepted...
> 
> I explicitly emailed Linas on May 24, 2007 detailing each patch that had 
> been applied, and to which netdev-2.6.git branch it had been applied 
> (and thus whether it was queued for 2.6.22 or 2.6.23).  Relevant 
> Message-id is <4656033F.1060505@...zik.org>, and was sent not only to 
> Linas but also to netdev@...r.kernel.org, linuxppc-dev@...abs.org, and 
> cbe-oss-dev@...abs.org.
> 
> These changes were subsequently made public immediately via 
> git://git.kernel.org/.../jgarzik/netdev-2.6.git branches 
> 'upstream-fixes' and 'upstream', and were followed a few days later by 
> akpm's public tree, starting with 2.6.22-rc3-mm1 (and all subsequent 
> releases).
> 
> All of the above seemed pretty clear, too.

Yeah fair enuf, that's fairly clear.

> To move forward, it sounds like the best thing to do is drop all 
> spidernet patches and start over, yes?

Well see what Linas thinks, but that is probably easiest. I was just
keen to see the "major bugfixes" get into 22, rather than waiting
another few months for 23.

cheers

-- 
Michael Ellerman
OzLabs, IBM Australia Development Lab

wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)

We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person

Download attachment "signature.asc" of type "application/pgp-signature" (190 bytes)