From: Sasha Levin <sashal@kernel.org>
To: gregkh@linuxfoundation.org
Cc: krzk@kernel.org, olof@lixom.net, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] ARM: npcm: Bring back GPIOLIB support" failed to apply to 4.14-stable tree
Date: Tue, 18 Feb 2020 11:53:43 -0500 [thread overview]
Message-ID: <20200218165343.GR1734@sasha-vm> (raw)
In-Reply-To: <158196661868212@kroah.com>
On Mon, Feb 17, 2020 at 08:10:18PM +0100, gregkh@linuxfoundation.org wrote:
>
>The patch below does not apply to the 4.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>.
>
>thanks,
>
>greg k-h
>
>------------------ original commit in Linus's tree ------------------
>
>From e383e871ab54f073c2a798a9e0bde7f1d0528de8 Mon Sep 17 00:00:00 2001
>From: Krzysztof Kozlowski <krzk@kernel.org>
>Date: Thu, 30 Jan 2020 20:55:24 +0100
>Subject: [PATCH] ARM: npcm: Bring back GPIOLIB support
>
>The CONFIG_ARCH_REQUIRE_GPIOLIB is gone since commit 65053e1a7743
>("gpio: delete ARCH_[WANTS_OPTIONAL|REQUIRE]_GPIOLIB") and all platforms
>should explicitly select GPIOLIB to have it.
>
>Link: https://lore.kernel.org/r/20200130195525.4525-1-krzk@kernel.org
>Cc: <stable@vger.kernel.org>
>Fixes: 65053e1a7743 ("gpio: delete ARCH_[WANTS_OPTIONAL|REQUIRE]_GPIOLIB")
>Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>
>Signed-off-by: Olof Johansson <olof@lixom.net>
This isn't needed on 4.14 and older since 7bffa14c9aed ("arm: npcm: add
basic support for Nuvoton BMCs") was added after 4.14.
--
Thanks,
Sasha
prev parent reply other threads:[~2020-02-18 16:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-17 19:10 FAILED: patch "[PATCH] ARM: npcm: Bring back GPIOLIB support" failed to apply to 4.14-stable tree gregkh
2020-02-18 16:53 ` Sasha Levin [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=20200218165343.GR1734@sasha-vm \
--to=sashal@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=krzk@kernel.org \
--cc=olof@lixom.net \
--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.