From: "Guilherme G. Piccoli" <gpiccoli@canonical.com>
To: Greg KH <gregkh@linuxfoundation.org>,
Thomas Gleixner <tglx@linutronix.de>
Cc: jan.kiszka@siemens.com, jbeulich@suse.com,
linux-kernel@vger.kernel.org, marc.zyngier@arm.com,
stable@vger.kernel.org,
"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 13:59:00 -0300 [thread overview]
Message-ID: <14968c46-ad8f-fbdf-88d6-0ded954534c9@canonical.com> (raw)
In-Reply-To: <20200817164924.GA721399@kroah.com>
On 17/08/2020 13:49, Greg KH wrote:
> [...]
>> I'm sorry, I hoped the subject + thread would suffice heh
>
> There is no thread here :(
>
Wow, that's odd. I've sent with In-Reply-To, I'd expect it'd get
threaded with the original message. Looking in lore archive [1], it
seems my first message wasn't threaded but the others were...apologies
for that, not sure what happened...
>> So, the mainline commit is: f8a8fe61fec8 ("x86/irq: Seperate unused
>> system vectors from spurious entry again") [0]. The backport to 4.19
>> stable tree has the following id: fc6975ee932b .
>
> Wow, over 1 1/2 years old, can you remember individual patches that long
> ago?
>
> Anyway, did you try to backport the patch to older kernels to see if it
> was possible and could work?
>
> If so, great, please feel free to submit it to the
> stable@vger.kernel.org list and I will be glad to pick it up.
>
I'm working on it, it is feasible. But I'm seeking here, in this
message, what is the reason it wasn't backported for pre-4.19 - is there
anything on these patches that is known to break old kernels? I'll
certainly submit my backported patch to stable 4.14 once I'm sure it's
working and there's no specific reason to not have it done before.
Thanks again!
[1]
https://lore.kernel.org/stable/a2788632-5690-932b-90de-14bd9cabedec@canonical.com/T/#mf0b26d5a7ff880cfd63bcda80136296275d3682e
next prev parent reply other threads:[~2020-08-17 17:30 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
2020-08-17 16:43 ` Guilherme G. Piccoli
2020-08-17 16:49 ` Greg KH
2020-08-17 16:59 ` Guilherme G. Piccoli [this message]
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=14968c46-ad8f-fbdf-88d6-0ded954534c9@canonical.com \
--to=gpiccoli@canonical.com \
--cc=gregkh@linuxfoundation.org \
--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).