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]
Message-ID: <466F4E64.5070303@garzik.org>
Date:	Tue, 12 Jun 2007 21:54:44 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	michael@...erman.id.au
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

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.

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

	Jeff


-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ