linux-kernel - Re: [GIT PATCH] scsi bug fixes for 2.6.23-rc2

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:	Tue, 07 Aug 2007 10:21:18 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	FUJITA Tomonori <tomof@....org>
CC:	akpm@...ux-foundation.org, James.Bottomley@...elEye.com,
	torvalds@...ux-foundation.org, linux-scsi@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [GIT PATCH] scsi bug fixes for 2.6.23-rc2

FUJITA Tomonori wrote:
> On Tue, 7 Aug 2007 00:14:29 -0700
> Andrew Morton <akpm@...ux-foundation.org> wrote:
> 
>> On Mon, 06 Aug 2007 22:55:41 -0500 James Bottomley <James.Bottomley@...elEye.com> wrote:
>>
>>> The real root cause of all of this is that there's no tree I can
>>> persuade all the interested parties to test that includes all of these
>>> features.  In spite of the fact they've all been incubating in -mm for
>>> at least 3 months, no-one apparently tested all the features together
>>> until 2.6.23-rc1 was released, so then we're scrambling to address the
>>> issues as they arise.
>> I pulled git-scsi-misc on July 19 and there was no bsg code in there at
>> all.  I pulled again on July 20 and all the bsg code was in mainline.  So
>> it appears that the bsg code went mailing-list -> mainline in less than 24
>> hours, so there wasn't a lot of opportunity for -mm testing there.
> 
> bsg was merged via Jens' branch. After that, I asked James to send
> some fixes via the scsi-rc-fixes.

ISTR that Jens doesn't regularly push / get picked up by -mm?  That 
seems like an easy problem to solve.

	Jeff




-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/