linux-kernel - Re: SCSI "staging" tree for linux-next?

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:	Fri, 16 May 2014 15:01:16 -0700
From:	James Bottomley <James.Bottomley@...senPartnership.com>
To:	Hannes Reinecke <hare@...e.de>
Cc:	Christoph Hellwig <hch@...radead.org>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-scsi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: SCSI "staging" tree for linux-next?

On Fri, 2014-05-16 at 15:38 +0200, Hannes Reinecke wrote:
> On 05/15/2014 07:26 AM, Christoph Hellwig wrote:
> > Hi James,
> >
> > we're past -rc5 and no SCSI patches have been collected for 3.16 yet,
> > despite a lot of patches including a lot of reviewed ones pending on the
> > list.
> >
> > I'd really love to get at least some testing for all the work that
> > sometimes has been pending for months in linux-next and would offer to
> > put together a tree of reviewed patches for linux-next.  Is this fine
> > with you?
> >
> Seconded. Having a staging tree would make my life _so_ much easier.

OK, I think we can do this easily.  Send me your staging branches and
I'll pull them into a global staging branch and merge it with for-next
in linux-scsi ... this will ensure we don't get yelled at for duplicate
commits causing merge rejections in linux-next.  Since staging will be
volatile and for the purposes of testing patches on upstream track, we
don't need signed tags or anything.

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/