From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Miquel Raynal <miquel.raynal@bootlin.com>,
Christophe Kerello <christophe.kerello@foss.st.com>
Cc: richard@nod.at, vigneshr@ti.com, linux-mtd@lists.infradead.org,
linux-kernel@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com
Subject: Re: [PATCH 0/2] depends on ARCH_STM32 instead of MACH_STM32MP157
Date: Mon, 27 Mar 2023 18:05:07 +0200 [thread overview]
Message-ID: <efa9a89e-ead7-8604-5d7a-07c728485eee@linaro.org> (raw)
In-Reply-To: <20230324170320.5087c223@xps-13>
On 24/03/2023 17:03, Miquel Raynal wrote:
> Hi Christophe,
>
> christophe.kerello@foss.st.com wrote on Fri, 24 Mar 2023 16:51:03 +0100:
>
>> To be able to compile the driver on all STM32MP SOCs, we move the
>> "depends on" on ARCH_STM32.
>>
>> Christophe Kerello (2):
>> memory: stm32-fmc2-ebi: depends on ARCH_STM32 instead of
>> MACH_STM32MP157
>> mtd: rawnand: stm32_fmc2: depends on ARCH_STM32 instead of
>> MACH_STM32MP157
>
> I don't see issue with taking these two patches in independent trees so
> if nobody disagrees I will take the second one through the mtd tree and
> let Krzysztof take the first one through mem-ctrl.
Sure, np.
Best regards,
Krzysztof
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
prev parent reply other threads:[~2023-03-27 16:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-24 15:51 [PATCH 0/2] depends on ARCH_STM32 instead of MACH_STM32MP157 Christophe Kerello
2023-03-24 15:51 ` [PATCH 1/2] memory: stm32-fmc2-ebi: " Christophe Kerello
2023-03-27 16:07 ` (subset) " Krzysztof Kozlowski
2023-03-24 15:51 ` [PATCH 2/2] mtd: rawnand: stm32_fmc2: " Christophe Kerello
2023-03-28 14:31 ` Miquel Raynal
2023-03-24 16:03 ` [PATCH 0/2] " Miquel Raynal
2023-03-27 16:05 ` Krzysztof Kozlowski [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=efa9a89e-ead7-8604-5d7a-07c728485eee@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=christophe.kerello@foss.st.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=vigneshr@ti.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