From: Greg KH <gregkh@linuxfoundation.org>
To: "Guilherme G. Piccoli" <gpiccoli@canonical.com>
Cc: jan.kiszka@siemens.com, jbeulich@suse.com,
linux-kernel@vger.kernel.org, marc.zyngier@arm.com,
stable@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>,
"Guilherme G. Piccoli" <kernel@gpiccoli.net>,
pedro.principeza@canonical.com
Subject: Re: [PATCH 4.19 35/47] x86/irq: Seperate unused system vectors from spurious entry again
Date: Mon, 17 Aug 2020 18:21:56 +0200 [thread overview]
Message-ID: <20200817162156.GA715236@kroah.com> (raw)
In-Reply-To: <c2b7a96a-122e-bdec-7368-d54700a55915@canonical.com>
On Mon, Aug 17, 2020 at 12:36:25PM -0300, Guilherme G. Piccoli wrote:
> Hi Greg / Thomas and all involved here. First, apologies for
> necro-bumping this thread, but I'm working a backport of this patch to
> kernel 4.15 (Ubuntu) and then I noticed we have it on stable, but only
> in 4.19+.
>
> Since the fixes tag presents an old commit (since ~3.19), I'm curious if
> we have a special reason to not have it on long-term stables, like 4.9
> or 4.14. It's a subtle portion of arch code, so I'm afraid I didn't see
> something that prevents its backport for previous versions.
What is the git commit id of this patch you are referring to, you didn't
provide any context here :(
thanks,
greg k-h
next prev parent reply other threads:[~2020-08-17 16:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-17 15:36 [PATCH 4.19 35/47] x86/irq: Seperate unused system vectors from spurious entry again Guilherme G. Piccoli
2020-08-17 16:21 ` Greg KH [this message]
2020-08-17 16:43 ` Guilherme G. Piccoli
2020-08-17 16:49 ` Greg KH
2020-08-17 16:59 ` Guilherme G. Piccoli
2020-08-17 17:05 ` Greg KH
2020-08-17 17:13 ` Guilherme Piccoli
-- strict thread matches above, loose matches on Subject: below --
2019-07-18 3:01 [PATCH 4.19 00/47] 4.19.60-stable review Greg Kroah-Hartman
2019-07-18 3:01 ` [PATCH 4.19 35/47] x86/irq: Seperate unused system vectors from spurious entry again Greg Kroah-Hartman
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=20200817162156.GA715236@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=gpiccoli@canonical.com \
--cc=jan.kiszka@siemens.com \
--cc=jbeulich@suse.com \
--cc=kernel@gpiccoli.net \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=pedro.principeza@canonical.com \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).