All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: "Guilherme G. Piccoli" <gpiccoli@canonical.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	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 19:05:22 +0200	[thread overview]
Message-ID: <20200817170522.GA795695@kroah.com> (raw)
In-Reply-To: <14968c46-ad8f-fbdf-88d6-0ded954534c9@canonical.com>

On Mon, Aug 17, 2020 at 01:59:00PM -0300, Guilherme G. Piccoli wrote:
> 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...

reply to is fine, but how do you know what my email client has (hint,
not a copy of 1.5 years of history sitting around in it at the
moment...)  So there is no "thread" here as far as it is concerned...

Anyway, not a big deal, just properly quote emails in the future, that's
good to get used to no matter what :)

> >> 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

Try reading the stable mailing list archives, again, you are asking
about a patch 1.5 years ago.  I can't remember information about patches
sent _yesterday_ given the quantity we go through...

thanks,

greg k-h

  reply	other threads:[~2020-08-17 17: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
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 [this message]
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=20200817170522.GA795695@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 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.