From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: miquel.raynal@bootlin.com, richard@nod.at, vigneshr@ti.com,
Christophe Kerello <christophe.kerello@foss.st.com>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
linux-stm32@st-md-mailman.stormreply.com,
linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org
Subject: Re: (subset) [PATCH 1/2] memory: stm32-fmc2-ebi: depends on ARCH_STM32 instead of MACH_STM32MP157
Date: Mon, 27 Mar 2023 18:07:06 +0200 [thread overview]
Message-ID: <167993322006.178792.4595537654296937780.b4-ty@linaro.org> (raw)
In-Reply-To: <20230324155105.826063-2-christophe.kerello@foss.st.com>
On Fri, 24 Mar 2023 16:51:04 +0100, Christophe Kerello wrote:
> To be able to compile the driver on all STM32MP SOCs, we move the
> "depends on" on ARCH_STM32.
>
>
Applied, thanks!
[1/2] memory: stm32-fmc2-ebi: depends on ARCH_STM32 instead of MACH_STM32MP157
https://git.kernel.org/krzk/linux-mem-ctrl/c/20c082a2ba25374a13505b78cdad7f6a2cf8d763
Best regards,
--
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
WARNING: multiple messages have this Message-ID (diff)
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: miquel.raynal@bootlin.com, richard@nod.at, vigneshr@ti.com,
Christophe Kerello <christophe.kerello@foss.st.com>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
linux-stm32@st-md-mailman.stormreply.com,
linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org
Subject: Re: (subset) [PATCH 1/2] memory: stm32-fmc2-ebi: depends on ARCH_STM32 instead of MACH_STM32MP157
Date: Mon, 27 Mar 2023 18:07:06 +0200 [thread overview]
Message-ID: <167993322006.178792.4595537654296937780.b4-ty@linaro.org> (raw)
In-Reply-To: <20230324155105.826063-2-christophe.kerello@foss.st.com>
On Fri, 24 Mar 2023 16:51:04 +0100, Christophe Kerello wrote:
> To be able to compile the driver on all STM32MP SOCs, we move the
> "depends on" on ARCH_STM32.
>
>
Applied, thanks!
[1/2] memory: stm32-fmc2-ebi: depends on ARCH_STM32 instead of MACH_STM32MP157
https://git.kernel.org/krzk/linux-mem-ctrl/c/20c082a2ba25374a13505b78cdad7f6a2cf8d763
Best regards,
--
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2023-03-27 16:07 UTC|newest]
Thread overview: 14+ 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 ` Christophe Kerello
2023-03-24 15:51 ` [PATCH 1/2] memory: stm32-fmc2-ebi: " Christophe Kerello
2023-03-24 15:51 ` Christophe Kerello
2023-03-27 16:07 ` Krzysztof Kozlowski [this message]
2023-03-27 16:07 ` (subset) " Krzysztof Kozlowski
2023-03-24 15:51 ` [PATCH 2/2] mtd: rawnand: stm32_fmc2: " Christophe Kerello
2023-03-24 15:51 ` Christophe Kerello
2023-03-28 14:31 ` Miquel Raynal
2023-03-28 14:31 ` Miquel Raynal
2023-03-24 16:03 ` [PATCH 0/2] " Miquel Raynal
2023-03-24 16:03 ` Miquel Raynal
2023-03-27 16:05 ` Krzysztof Kozlowski
2023-03-27 16:05 ` 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=167993322006.178792.4595537654296937780.b4-ty@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 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.