From: Greg KH <gregkh@linuxfoundation.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: linus.walleij@linaro.org, mika.westerberg@linux.intel.com,
stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] gpiolib: acpi: Add ACPI_GPIO_QUIRK_ABSOLUTE_NUMBER quirk" failed to apply to 5.4-stable tree
Date: Fri, 12 Mar 2021 13:10:09 +0100 [thread overview]
Message-ID: <YEtaIRHYvLreTKe2@kroah.com> (raw)
In-Reply-To: <YEtXnzyfm0Tbnu0e@smile.fi.intel.com>
On Fri, Mar 12, 2021 at 01:59:27PM +0200, Andy Shevchenko wrote:
> On Thu, Mar 11, 2021 at 07:12:55PM +0100, gregkh@linuxfoundation.org wrote:
> >
> > The patch below does not apply to the 5.4-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>.
>
> No need for v5.4.
>
> Please, also drop
> gpio-pca953x-set-irq-type-when-handle-intel-galileo-gen-2.patch
> gpiolib-acpi-allow-to-find-gpioint-resource-by-name-and-index.patch
>
> from 5.4-stable queue, thanks!
Why? If you look at the first commit above, it says:
Fixes: ba8c90c61847 ("gpio: pca953x: Override IRQ for one of the expanders on Galileo Gen 2")
which is in the 5.4.52 kernel release. So why shouldn't it go there?
Same goes for the
gpiolib-acpi-allow-to-find-gpioint-resource-by-name-and-index.patch
patch.
Is your marking of the "Fixes:" tags incorrect somehow?
confused,
greg k-h
next prev parent reply other threads:[~2021-03-12 12:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-11 18:12 FAILED: patch "[PATCH] gpiolib: acpi: Add ACPI_GPIO_QUIRK_ABSOLUTE_NUMBER quirk" failed to apply to 5.4-stable tree gregkh
2021-03-12 11:59 ` Andy Shevchenko
2021-03-12 12:10 ` Greg KH [this message]
2021-03-12 12:24 ` Andy Shevchenko
2021-03-12 12:33 ` Andy Shevchenko
2021-03-12 13:24 ` Greg KH
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=YEtaIRHYvLreTKe2@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linus.walleij@linaro.org \
--cc=mika.westerberg@linux.intel.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 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.