linux-kernel - Re: [PATCH 0/3] Openrisc 4.10 fixes

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] [day] [month] [year] [list]

Message-ID: <CAFLxGvyvLoSRfENYKF7dCOC9uQ1S_toXm05KGVvfiGykViDgSw@mail.gmail.com>
Date:   Mon, 2 Jan 2017 12:15:55 +0100
From:   Richard Weinberger <richard.weinberger@...il.com>
To:     Jonas Bonn <jonas@...thpole.se>
Cc:     Stafford Horne <shorne@...il.com>,
        stefan.kristiansson@...nalahti.fi, geert+renesas@...der.be,
        LKML <linux-kernel@...r.kernel.org>,
        openrisc@...ts.librecores.org
Subject: Re: [PATCH 0/3] Openrisc 4.10 fixes

On Mon, Jan 2, 2017 at 11:34 AM, Jonas Bonn <jonas@...thpole.se> wrote:
> On 12/31/2016 11:50 PM, Stafford Horne wrote:
>>
>> Hi Jonas,
>>
>> On Sat, Dec 31, 2016 at 03:10:37PM +0100, Jonas Bonn wrote:
>>>
>>> Hi Stafford,
>>>
>>> Post-merge window patches should  be bug fixes, only.  Patch 1/3 probably
>>> qualifies, but the others are far too trivial to be pushing now.  Just
>>> put
>>> them on your 4.11 branch.
>>
>> Thanks, for some reason I thought minor changes like this were ok too.
>> I will only push the one change in this case.  The rest will go to my
>> 4.11 queue, which I'll send for review in the next few days.
>
> Actually, it's not even bug-fixes, just fixes for regressions. Patch 1 fixes

Well, it is not that strict.
Fixes for real bugs are perfectly fine in early -rcX releases and don't have to
wait for a merge window.

-- 
Thanks,
//richard