[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180503020550.GP2714@sirena.org.uk>
Date: Thu, 3 May 2018 11:05:50 +0900
From: Mark Brown <broonie@...nel.org>
To: Sasha Levin <Alexander.Levin@...rosoft.com>
Cc: Daniel Vetter <daniel.vetter@...ll.ch>,
"Theodore Y. Ts'o" <tytso@....edu>,
"ksummit-discuss@...ts.linuxfoundation.org"
<ksummit-discuss@...ts.linuxfoundation.org>,
Greg KH <gregkh@...uxfoundation.org>, "w@....eu" <w@....eu>,
"julia.lawall@...6.fr" <julia.lawall@...6.fr>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [Ksummit-discuss] bug-introducing patches
On Wed, May 02, 2018 at 07:46:34PM +0000, Sasha Levin wrote:
> As you said, the regression should be fixed "asap", not "immediately".
> It should go through some sort of review and testing the maintainers are
> happy with, but unfourtenately it doesn't happen now.
Doesn't happen some of the time. It's not like this is a universal
problem.
Especially for driver specific things there's at times no realistic
prospect of getting useful independent review of fixes, the hardware
isn't always widely available and if the fix isn't a pure software thing
at some point you just have to trust the judgement of the vendor.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists