stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Pali Rohár" <pali@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "Marek Behún" <kabel@kernel.org>,
	lorenzo.pieralisi@arm.com, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] PCI: aardvark: Fix PCIe Max Payload Size setting" failed to apply to 5.15-stable tree
Date: Mon, 15 Nov 2021 16:38:41 +0100	[thread overview]
Message-ID: <20211115153841.ftphwo7k5hefayfp@pali> (raw)
In-Reply-To: <YZJ9z4N64bzgl97E@kroah.com>

On Monday 15 November 2021 16:33:35 Greg KH wrote:
> On Sun, Nov 14, 2021 at 03:20:33PM +0100, Pali Rohár wrote:
> > On Sunday 14 November 2021 15:13:31 gregkh@linuxfoundation.org wrote:
> > > The patch below does not apply to the 5.15-stable tree.
> > > If someone wants it applied there, or to any other stable or longterm
> > > tree, then please email the backport, including the original git commit
> > > id to <stable@vger.kernel.org>.
> > > 
> > > thanks,
> > > 
> > > greg k-h
> > 
> > Hello Greg! Following patch is needed for PCI_EXP_DEVCTL_PAYLOAD_512B macro:
> > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=460275f124fb072dca218a6b43b6370eebbab20d
> 
> Thanks, that solved the issue here for 5.10 and newer, but not for
> 4.9.y, 4.14.y, 4.19.y and 5.4.y.  Can you send fixes for them if it
> matters?

Marek told me that would take care of backporting aardvark related
patches to stable trees. He is already in CC list.

      reply	other threads:[~2021-11-15 15:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-14 14:13 FAILED: patch "[PATCH] PCI: aardvark: Fix PCIe Max Payload Size setting" failed to apply to 5.15-stable tree gregkh
2021-11-14 14:20 ` Pali Rohár
2021-11-15 15:33   ` Greg KH
2021-11-15 15:38     ` Pali Rohár [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=20211115153841.ftphwo7k5hefayfp@pali \
    --to=pali@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=kabel@kernel.org \
    --cc=lorenzo.pieralisi@arm.com \
    --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 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).