linux-kernel - Re: [PATCH] EDAC/altera: Use fast register IO for S10 IRQs

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]

Message-ID: <20191120191335.GL2634@zn.tnic>
Date:   Wed, 20 Nov 2019 20:13:35 +0100
From:   Borislav Petkov <bp@...en8.de>
To:     Thor Thayer <thor.thayer@...ux.intel.com>
Cc:     stable@...r.kernel.org, mchehab@...nel.org, tony.luck@...el.com,
        james.morse@....com, rrichter@...vell.com,
        linux-edac@...r.kernel.org, linux-kernel@...r.kernel.org,
        Meng Li <Meng.Li@...driver.com>
Subject: Re: [PATCH] EDAC/altera: Use fast register IO for S10 IRQs

On Wed, Nov 20, 2019 at 12:52:18PM -0600, Thor Thayer wrote:
> This patch should to be applied to the stable branches to fix the issue in
> older branches.

Do stable folks pick up stable fixes which are not upstream?

AFAIK, a patch needs to be upstream to be backported to stable first.

> Although I knew the To: had to be to stable@...r.kernel.org,
> I wasn't sure how that worked with the EDAC reviewers. This was a weird
> situation where I couldn't fix the upstream because it had already been
> fixed a different way.

Yah.

> Meng sent me the notification and the patch with a SOB so I put Meng first
> in the order.

If he sent you the patch, then he's the author and you need to keep his

From: Meng Li <Meng.Li@...driver.com>

at the beginning of the file so that git preserves his authorship.

Thx.

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette