linux-kernel - Re: [ANNOUNCE] scsi patch queue tree updated

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:	Thu, 14 Aug 2014 10:47:08 -0700
From:	James Bottomley <James.Bottomley@...senPartnership.com>
To:	Christoph Hellwig <hch@...radead.org>
Cc:	linux-kernel@...r.kernel.org,
	linux-scsi <linux-scsi@...r.kernel.org>
Subject: Re: [ANNOUNCE] scsi patch queue tree updated

On Thu, 2014-08-14 at 05:54 -0700, Christoph Hellwig wrote:
> On Mon, Aug 04, 2014 at 07:20:04AM -0700, James Bottomley wrote:
> > > The drivers side are a bunch of smaller fixes for iscsi and pm8001 which
> > > never have been a problem to put in near the end of the merge window,
> > > especially if they have a few more days linux-next exposure in
> > > Linux-next even after the 3.16 release.  They absolutely would be
> > > candidates for a second pull even if they'd miss the first pull.
> > 
> > OK, since I have to do a second pull anyway we might as well follow the
> > rules.
> 
> Ok, new tree is out, the core-for-3.17 has the one 64-bit lun format
> string fix that didn't make it into the first pull request, the
> queuecommand device busy regression fix, and the cmd_pool fix.
> 
> The drivers-for-3.17 just has the driver updates I pushed earlier that
> didn't make the cut.

So this is a bit late to get through linux-next and into a pull request.
I was planning on sending the final pull tomorrow (in case Linus planned
a surprise early release).  Can we redo some of these as bug fixes and
send them in for -rc1?

James


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