[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAGXu5jK7qXKo_P3gE7Fp+NO+46yTLq24=JgvdKoQcnJ7cCkmig@mail.gmail.com>
Date: Mon, 19 Jun 2017 11:56:04 -0700
From: Kees Cook <keescook@...omium.org>
To: "Luis R. Rodriguez" <mcgrof@...nel.org>
Cc: Sumit Semwal <sumit.semwal@...aro.org>,
Brian Norris <computersforpeace@...il.com>,
Fengguang Wu <fengguang.wu@...el.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Shuah Khan <shuah@...nel.org>,
LKML <linux-kernel@...r.kernel.org>,
"# 3.4.x" <stable@...r.kernel.org>,
linux-kselftest@...r.kernel.org,
Martin Fuzzey <mfuzzey@...keon.com>,
Alan Cox <alan@...ux.intel.com>
Subject: Re: LTS testing with latest kselftests - some failures
On Fri, Jun 16, 2017 at 9:46 AM, Luis R. Rodriguez <mcgrof@...nel.org> wrote:
>> 47e0bbb7fa98 (test: firmware_class: report errors properly on failure)
>
> Hrm, come to think of it, this *might* have been a stable fix, however the
> fix did not mention any specific about real issue with this. Kees?
This was mostly a cosmetic fix, though it does fix the return code. It
can certainly go to stable, but I try to only push more critical
things to -stable.
-Kees
--
Kees Cook
Pixel Security
Powered by blists - more mailing lists