public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Wadim Egorov <w.egorov@phytec.de>
To: <catalin.marinas@arm.com>, <will@kernel.org>,
	<quic_bjorande@quicinc.com>, <krzysztof.kozlowski@linaro.org>,
	<geert+renesas@glider.be>, <dmitry.baryshkov@linaro.org>,
	<shawnguo@kernel.org>, <neil.armstrong@linaro.org>,
	<arnd@arndb.de>, <m.szyprowski@samsung.com>,
	<nfraprado@collabora.com>, <u-kumar1@ti.com>
Cc: <upstream@lists.phytec.de>, <linux-kernel@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [Upstream] [PATCH] arm64: defconfig: Enable PCF857X GPIO expander
Date: Wed, 2 Oct 2024 12:32:42 +0200	[thread overview]
Message-ID: <4238b46e-58eb-41b8-863c-2c66e823f594@phytec.de> (raw)
In-Reply-To: <20240718095239.922641-1-w.egorov@phytec.de>



Am 18.07.24 um 11:52 schrieb Wadim Egorov:
> Enable the PCF857X GPIO expander which is equipped on
> the PHYTEC phyBOARD-Lyra AM625.
> 
> Signed-off-by: Wadim Egorov <w.egorov@phytec.de>

Is there something wrong with this change?

> ---
>   arch/arm64/configs/defconfig | 1 +
>   1 file changed, 1 insertion(+)
> 
> diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
> index ef2235838c44..0c7d3f7717ff 100644
> --- a/arch/arm64/configs/defconfig
> +++ b/arch/arm64/configs/defconfig
> @@ -655,6 +655,7 @@ CONFIG_GPIO_XGENE_SB=y
>   CONFIG_GPIO_MAX732X=y
>   CONFIG_GPIO_PCA953X=y
>   CONFIG_GPIO_PCA953X_IRQ=y
> +CONFIG_GPIO_PCF857X=m
>   CONFIG_GPIO_BD9571MWV=m
>   CONFIG_GPIO_MAX77620=y
>   CONFIG_GPIO_SL28CPLD=m



  reply	other threads:[~2024-10-02 10:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-18  9:52 [PATCH] arm64: defconfig: Enable PCF857X GPIO expander Wadim Egorov
2024-10-02 10:32 ` Wadim Egorov [this message]
2024-10-02 10:45   ` [Upstream] " Krzysztof Kozlowski

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=4238b46e-58eb-41b8-863c-2c66e823f594@phytec.de \
    --to=w.egorov@phytec.de \
    --cc=arnd@arndb.de \
    --cc=catalin.marinas@arm.com \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=geert+renesas@glider.be \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.szyprowski@samsung.com \
    --cc=neil.armstrong@linaro.org \
    --cc=nfraprado@collabora.com \
    --cc=quic_bjorande@quicinc.com \
    --cc=shawnguo@kernel.org \
    --cc=u-kumar1@ti.com \
    --cc=upstream@lists.phytec.de \
    --cc=will@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