stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: "Jürgen Groß" <jgross@suse.com>
Cc: stable@vger.kernel.org, Stefan Bader <stefan.bader@canonical.com>,
	Boris Ostrovsky <boris.ostrovsky@oracle.com>
Subject: Re: [PATCH] xen/events: don't use chip_data for legacy IRQs
Date: Wed, 14 Oct 2020 11:51:08 +0200	[thread overview]
Message-ID: <20201014095108.GB3597464@kroah.com> (raw)
In-Reply-To: <f0b0b56e-512a-84ed-f03f-86ef54c10e96@suse.com>

On Wed, Oct 14, 2020 at 11:31:33AM +0200, Jürgen Groß wrote:
> Any reason this has not made it into 5.4.y and older by now?
> 
> This patch is fixing a real problem...

What is the git commit id of this patch in Linus's tree?

thanks,

greg k-h

  reply	other threads:[~2020-10-14  9:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-05  6:19 [PATCH] xen/events: don't use chip_data for legacy IRQs Juergen Gross
2020-10-14  9:31 ` Jürgen Groß
2020-10-14  9:51   ` Greg KH [this message]
2020-10-14 10:44     ` Jürgen Groß
2020-10-16  8:06       ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2020-09-30  9:16 Juergen Gross
2020-09-30 12:06 ` Stefan Bader
2020-09-30 13:51 ` boris.ostrovsky

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=20201014095108.GB3597464@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=boris.ostrovsky@oracle.com \
    --cc=jgross@suse.com \
    --cc=stable@vger.kernel.org \
    --cc=stefan.bader@canonical.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 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).