From: Greg KH <gregkh@linuxfoundation.org>
To: "Pali Rohár" <pali@kernel.org>
Cc: lorenzo.pieralisi@arm.com, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] PCI: aardvark: Fix reporting CRS value" failed to apply to 5.14-stable tree
Date: Wed, 22 Sep 2021 17:54:33 +0200 [thread overview]
Message-ID: <YUtRuTF+pglF9R84@kroah.com> (raw)
In-Reply-To: <20210922150333.3p7jjaz7fqt6ovwh@pali>
On Wed, Sep 22, 2021 at 05:03:33PM +0200, Pali Rohár wrote:
> On Wednesday 22 September 2021 16:41:30 Greg KH wrote:
> > On Wed, Sep 15, 2021 at 06:46:43PM +0200, Pali Rohár wrote:
> > > On Wednesday 15 September 2021 16:30:03 gregkh@linuxfoundation.org wrote:
> > > > The patch below does not apply to the 5.14-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>.
> > >
> > > Hello that patch depends on commit which fixes name of rootcap member:
> > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e902bb7c24a7099d0eb0eb4cba06f2d91e9299f3
> >
> > Thanks, that worked for 5.10 and 5.14, but not for 5.4.y. If this needs
> > to go there too, can you send a working set of backported patches?
>
> Hello Greg!
>
> Applying patches in this order passes:
>
> git cherry-pick e0d9d30b73548fbfe5c024ed630169bdc9a08aee
> git cherry-pick b1bd5714472cc72e14409f5659b154c765a76c65
> git cherry-pick e902bb7c24a7099d0eb0eb4cba06f2d91e9299f3
> git cherry-pick 43f5c77bcbd27cce70bf33c2b86d6726ce95dd66
>
> First patch fixes big endian support in driver code and second patch
> fixes filling return value of function call on error (return value is
> passed via pointer argument). I do not know why they do not have
> appropriate Fixes tag, but for me it looks like that both patches are
> suitable for stable backporting.
>
> What do you think, are first two patches suitable for backport? Or do
> you need some other solution?
Looks good to me, thanks for these, all now queued up!
greg k-h
prev parent reply other threads:[~2021-09-22 15:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-15 14:30 FAILED: patch "[PATCH] PCI: aardvark: Fix reporting CRS value" failed to apply to 5.14-stable tree gregkh
2021-09-15 16:46 ` Pali Rohár
2021-09-22 14:41 ` Greg KH
2021-09-22 15:03 ` Pali Rohár
2021-09-22 15:54 ` 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=YUtRuTF+pglF9R84@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=pali@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.