| 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
| ||
|
Message-ID: <1408131124.11617.25.camel@HansenPartnership.com> Date: Fri, 15 Aug 2014 12:32:04 -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>, Linus Torvalds <torvalds@...ux-foundation.org> Subject: Re: [ANNOUNCE] scsi patch queue tree updated On Fri, 2014-08-15 at 12:25 -0700, Christoph Hellwig wrote: > On Thu, Aug 14, 2014 at 10:47:08AM -0700, James Bottomley wrote: > > 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? > > core-for-3.17 is entirely bug fixes, the drivers side is all except > for 4 tiny patches, and even Linus isn't that anal I think. You rebased the tree before doing it ... that's the one thing that excites his process gene. I can't send a rebased tree in on the last day of merging. I'll send in the unrebased tree which has been sitting in linux-next for the past week. The two additional changes in core-for-3.17 can be picked out and sent as eligible bug fixes for -rc1. The only addition in drivers-for-3.17 is eata: remove driver_lock ... I'm in two minds about whether we treat that as a bug fix or not. 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/
Powered by blists - more mailing lists