From: Borislav Petkov <bp@alien8.de>
To: Thor Thayer <thor.thayer@linux.intel.com>
Cc: stable@vger.kernel.org, mchehab@kernel.org, tony.luck@intel.com,
james.morse@arm.com, rrichter@marvell.com,
linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org,
Meng Li <Meng.Li@windriver.com>
Subject: Re: [PATCH] EDAC/altera: Use fast register IO for S10 IRQs
Date: Wed, 20 Nov 2019 20:13:35 +0100 [thread overview]
Message-ID: <20191120191335.GL2634@zn.tnic> (raw)
In-Reply-To: <5bfe9cc4-6cd4-7edb-9ed2-abe5fadff06d@linux.intel.com>
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@vger.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@windriver.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
next prev parent reply other threads:[~2019-11-20 19:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-20 17:38 [PATCH] EDAC/altera: Use fast register IO for S10 IRQs thor.thayer
2019-11-20 18:07 ` Borislav Petkov
2019-11-20 18:52 ` Thor Thayer
2019-11-20 19:13 ` Borislav Petkov [this message]
2019-11-20 19:28 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191120191335.GL2634@zn.tnic \
--to=bp@alien8.de \
--cc=Meng.Li@windriver.com \
--cc=james.morse@arm.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=rrichter@marvell.com \
--cc=stable@vger.kernel.org \
--cc=thor.thayer@linux.intel.com \
--cc=tony.luck@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.