From: Greg KH <gregkh@linuxfoundation.org>
To: Rui Salvaterra <rsalvaterra@gmail.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Marc Zyngier <maz@kernel.org>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
Bjorn Helgaas <bhelgaas@google.com>,
kernel-team@android.com, stable@vger.kernel.org
Subject: Re: [PATCH 0/2] PCI: MSI: Deal with devices lying about their masking capability
Date: Fri, 19 Nov 2021 15:05:59 +0100 [thread overview]
Message-ID: <YZevR+LnK2Fbk4Jh@kroah.com> (raw)
In-Reply-To: <YZOOYN6x3NCaC3qH@kroah.com>
On Tue, Nov 16, 2021 at 11:56:32AM +0100, Greg KH wrote:
> On Tue, Nov 16, 2021 at 10:47:23AM +0000, Rui Salvaterra wrote:
> > Hi, Greg,
> >
> > On Tue, 16 Nov 2021 at 10:39, Greg KH <gregkh@linuxfoundation.org> wrote:
> > >
> > > What is the git commit ids of these changes in Linus's tree?
> >
> > 2226667a145d ("PCI/MSI: Deal with devices lying about their MSI mask
> > capability")
> > f21082fb20db ("PCI: Add MSI masking quirk for Nvidia ION AHCI")
>
> Thanks, I'll queue them up in the next round of releases after the
> current ones are out.
Now queued up.
greg k-h
prev parent reply other threads:[~2021-11-19 14:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-04 18:01 [PATCH 0/2] PCI: MSI: Deal with devices lying about their masking capability Marc Zyngier
2021-11-04 18:01 ` [PATCH 1/2] PCI: MSI: Deal with devices lying about their MSI mask capability Marc Zyngier
2021-11-11 8:57 ` [tip: irq/urgent] PCI/MSI: " tip-bot2 for Marc Zyngier
2021-11-04 18:01 ` [PATCH 2/2] PCI: Add MSI masking quirk for Nvidia ION AHCI Marc Zyngier
2021-11-05 13:14 ` [PATCH 0/2] PCI: MSI: Deal with devices lying about their masking capability Thomas Gleixner
2021-11-16 10:21 ` Rui Salvaterra
2021-11-16 10:39 ` Greg KH
2021-11-16 10:47 ` Rui Salvaterra
2021-11-16 10:56 ` Greg KH
2021-11-19 14:05 ` Greg KH [this message]
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=YZevR+LnK2Fbk4Jh@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=bhelgaas@google.com \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=maz@kernel.org \
--cc=rsalvaterra@gmail.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).