All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Pali Rohár" <pali@kernel.org>
Cc: "Marek Behún" <kabel@kernel.org>,
	"Sasha Levin" <sashal@kernel.org>,
	stable@vger.kernel.org,
	"Josef Schlehofer" <josef.schlehofer@nic.cz>,
	"Lorenzo Pieralisi" <lorenzo.pieralisi@arm.com>
Subject: Re: [PATCH 4.14 1/2] PCI: aardvark: Clear all MSIs at setup
Date: Tue, 10 May 2022 14:20:32 +0200	[thread overview]
Message-ID: <YnpYkEYMYEP9yo3T@kroah.com> (raw)
In-Reply-To: <20220510120118.r4nmzqrxw3mmyryd@pali>

On Tue, May 10, 2022 at 02:01:18PM +0200, Pali Rohár wrote:
> On Tuesday 10 May 2022 13:58:06 Greg Kroah-Hartman wrote:
> > On Tue, May 03, 2022 at 10:54:33PM +0200, Marek Behún wrote:
> > > From: Pali Rohár <pali@kernel.org>
> > > 
> > > [ Upstream commit 7d8dc1f7cd007a7ce94c5b4c20d63a8b8d6d7751 ]
> > > 
> > > We already clear all the other interrupts (ISR0, ISR1, HOST_CTRL_INT).
> > > 
> > > Define a new macro PCIE_MSI_ALL_MASK and do the same clearing for MSIs,
> > > to ensure that we don't start receiving spurious interrupts.
> > > 
> > > Use this new mask in advk_pcie_handle_msi();
> > > 
> > > Link: https://lore.kernel.org/r/20211130172913.9727-5-kabel@kernel.org
> > > Signed-off-by: Pali Rohár <pali@kernel.org>
> > > Signed-off-by: Marek Behún <kabel@kernel.org>
> > > Signed-off-by: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
> > > Signed-off-by: Marek Behún <kabel@kernel.org>
> > > ---
> > >  drivers/pci/host/pci-aardvark.c | 6 ++++--
> > >  1 file changed, 4 insertions(+), 2 deletions(-)
> > 
> > What about 4.19 and 5.4 for this and patch 2/2?  I can't apply this to
> > 4.14 without the newer kernels also having it, right?
> 
> Do you mean these patches which Marek prepared? Or something else?
> https://lore.kernel.org/stable/20220504140719.11066-1-kabel@kernel.org/
> https://lore.kernel.org/stable/20220504140826.11094-1-kabel@kernel.org/

Odd, I missed those somehow.  Thanks for pointing them out, I'll go
apply them now.

greg k-h

      reply	other threads:[~2022-05-10 12:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-03 20:54 [PATCH 4.14 1/2] PCI: aardvark: Clear all MSIs at setup Marek Behún
2022-05-03 20:54 ` [PATCH 4.14 2/2] PCI: aardvark: Fix reading MSI interrupt number Marek Behún
2022-05-10 11:58 ` [PATCH 4.14 1/2] PCI: aardvark: Clear all MSIs at setup Greg Kroah-Hartman
2022-05-10 12:01   ` Pali Rohár
2022-05-10 12:20     ` Greg Kroah-Hartman [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=YnpYkEYMYEP9yo3T@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=josef.schlehofer@nic.cz \
    --cc=kabel@kernel.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=pali@kernel.org \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    /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.