[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180509084440.GW13402@sirena.org.uk>
Date: Wed, 9 May 2018 17:44:40 +0900
From: Mark Brown <broonie@...nel.org>
To: Ulf Hansson <ulf.hansson@...aro.org>
Cc: Tony Lindgren <tony@...mide.com>,
Sasha Levin <Alexander.Levin@...rosoft.com>,
Guenter Roeck <linux@...ck-us.net>,
"ksummit-discuss@...ts.linuxfoundation.org"
<ksummit-discuss@...ts.linuxfoundation.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Greg KH <gregkh@...uxfoundation.org>, "w@....eu" <w@....eu>,
Stephen Rothwell <sfr@...b.auug.org.au>
Subject: Re: [Ksummit-discuss] bug-introducing patches
On Fri, May 04, 2018 at 04:21:26PM +0200, Ulf Hansson wrote:
> Then, why don't we have a pre-integration tree for fixes? That would
> at least simply automated testing of fixes separately from new
> material.
> Perhaps this has already been discussed, and concluded and it's not
> worth it, then apologize for my ignorance.
I think this is an excellent idea, copying in Stephen for his input.
I'm currently on holiday but unless someone convinces me it's a terrible
idea I'm willing to at least give it a go on a trial basis once I'm back
home.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists