From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Bin Meng <bmeng@tinylab.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Cc: andrew <andrew@lunn.ch>, agross <agross@kernel.org>,
arnd <arnd@arndb.de>, andersson <andersson@kernel.org>,
"chuck.lever" <chuck.lever@oracle.com>,
dinguyen <dinguyen@kernel.org>, festevam <festevam@gmail.com>,
"gregory.clement" <gregory.clement@bootlin.com>,
"jernej.skrabec" <jernej.skrabec@gmail.com>,
"konrad.dybcio" <konrad.dybcio@linaro.org>,
linux-imx <linux-imx@nxp.com>,
"neil.armstrong" <neil.armstrong@linaro.org>,
kernel <kernel@pengutronix.de>, elliott <elliott@hpe.com>,
linux <linux@armlinux.org.uk>, "s.hauer" <s.hauer@pengutronix.de>,
"sebastian.hesselbarth" <sebastian.hesselbarth@gmail.com>,
shawnguo <shawnguo@kernel.org>, newbie13xd <newbie13xd@gmail.com>,
"sudeep.holla" <sudeep.holla@arm.com>, ziy <ziy@nvidia.com>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>
Subject: Re: [PATCH] arm: Drop CONFIG_MTD_M25P80 in various defconfig files
Date: Thu, 23 Feb 2023 11:50:36 +0100 [thread overview]
Message-ID: <e6d97e34-0c63-019d-93b6-c39e722d1d8c@linaro.org> (raw)
In-Reply-To: <em4fed7efe-b8aa-4a34-86d4-655b0a96fec0@1adcb789.com>
On 23/02/2023 11:46, Bin Meng wrote:
> On 2023/2/10 17:32:24, "Bin Meng" <bmeng@tinylab.org> wrote:
>
>> Drop CONFIG_MTD_M25P80 that was removed in
>> commit b35b9a10362d ("mtd: spi-nor: Move m25p80 code in spi-nor.c")
>>
>> Signed-off-by: Bin Meng <bmeng@tinylab.org>
>>
>> ---
>>
>> arch/arm/configs/axm55xx_defconfig | 2 +-
>> arch/arm/configs/davinci_all_defconfig | 1 -
>> arch/arm/configs/dove_defconfig | 1 -
>> arch/arm/configs/keystone_defconfig | 1 -
>> arch/arm/configs/mvebu_v5_defconfig | 1 -
>> arch/arm/configs/mxs_defconfig | 1 -
>> arch/arm/configs/pxa_defconfig | 1 -
>> arch/arm/configs/qcom_defconfig | 1 -
>> arch/arm/configs/socfpga_defconfig | 1 -
>> 9 files changed, 1 insertion(+), 9 deletions(-)
>>
>>
>
> Ping?
No need for pinging, but you need to send to soc folks. Otherwise no one
will pick it up. You will get the address from get_maintainer.pl -f
arch/arm/boot/dts/Makefile (yes, it is quite hidden on purpose).
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-02-23 10:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-10 9:32 Bin Meng
2023-02-23 10:46 ` Bin Meng
2023-02-23 10:50 ` Krzysztof Kozlowski [this message]
2023-02-23 11:00 ` Bin Meng
2023-02-23 11:15 ` Krzysztof Kozlowski
2023-02-23 10:49 ` Konrad Dybcio
-- strict thread matches above, loose matches on Subject: below --
2020-05-02 4:23 Bin Meng
2020-05-02 9:04 ` Russell King - ARM Linux admin
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=e6d97e34-0c63-019d-93b6-c39e722d1d8c@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=andrew@lunn.ch \
--cc=arnd@arndb.de \
--cc=bmeng@tinylab.org \
--cc=chuck.lever@oracle.com \
--cc=dinguyen@kernel.org \
--cc=elliott@hpe.com \
--cc=festevam@gmail.com \
--cc=gregory.clement@bootlin.com \
--cc=jernej.skrabec@gmail.com \
--cc=kernel@pengutronix.de \
--cc=konrad.dybcio@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=neil.armstrong@linaro.org \
--cc=newbie13xd@gmail.com \
--cc=s.hauer@pengutronix.de \
--cc=sebastian.hesselbarth@gmail.com \
--cc=shawnguo@kernel.org \
--cc=sudeep.holla@arm.com \
--cc=ziy@nvidia.com \
/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
all inboxes | Powered by JetHome®