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:	Mon, 13 Aug 2007 14:42:26 +0200
From:	Jens Axboe <jens.axboe@...cle.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	James Bottomley <James.Bottomley@...elEye.com>,
	Jeff Garzik <jeff@...zik.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-scsi <linux-scsi@...r.kernel.org>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PATCH] scsi bug fixes for 2.6.23-rc2

On Tue, Aug 07 2007, Andrew Morton wrote:
> On Tue, 07 Aug 2007 10:38:44 -0500 James Bottomley <James.Bottomley@...elEye.com> wrote:
> 
> > On Tue, 2007-08-07 at 11:11 -0400, Jeff Garzik wrote:
> > > James Bottomley wrote:
> > > > The initial bsg submit went via the block git tree ... which I believe
> > > > you have in -mm.  We only started taking the updates via the scsi tree
> > > 
> > > Seven hours before you posted this, in 
> > > <20070807001429.f8cb3b22.akpm@...ux-foundation.org>, Andrew already 
> > > noted it was not in -mm.
> > > 
> > > A trivial examination of the broken-out mm patches backs up the absence 
> > >   of Jens' block tree, too.
> > > 
> > > So let's put this myth / bad assumption to rest, shall we?
> > 
> > Sorry ... I just assumed from the fact that it had been in the block git
> > tree for six months that it was also in -mm.
> 
> bsg was never in the #for-akpm branch of git-block.  So I assume that
> Jens had it in some other branch and for some reason never pulled it
> across into #for-akpm.

#for-akpm is usually only in very few -mm release anyway, so it's not
like it would have made much difference. We/you/I need to improve that,
certainly.

Honestly, for bsg, it wasn't much of an issue. We had build problems
when bsg was merged which was unfortunate but got fixed quickly. Having
bsg in -mm would not have caused any testing of the driver in question
outside of what it already received, given the nature of it.

-- 
Jens Axboe

-
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/