From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Esben Haabendal <esben@geanix.com>
Cc: Michael Walle <mwalle@kernel.org>,
Vignesh Raghavendra <vigneshr@ti.com>,
Richard Weinberger <richard@nod.at>,
linux-kernel@vger.kernel.org,
Krzysztof Kozlowski <krzk@kernel.org>,
"Aneesh Kumar K.V" <aneesh.kumar@kernel.org>,
Tudor Ambarus <tudor.ambarus@linaro.org>,
linux-mtd@lists.infradead.org,
Nicholas Piggin <npiggin@gmail.com>,
"Naveen N. Rao" <naveen.n.rao@linux.ibm.com>,
linuxppc-dev@lists.ozlabs.org,
Pratyush Yadav <pratyush@kernel.org>
Subject: Re: [PATCH v2 1/2] memory: fsl_ifc: Make FSL_IFC config visible and selectable
Date: Tue, 28 May 2024 14:48:23 +0200 [thread overview]
Message-ID: <20240528144823.2ec929f6@xps-13> (raw)
In-Reply-To: <20240528-fsl-ifc-config-v2-1-5fd7be76650d@geanix.com>
Hi Esben,
esben@geanix.com wrote on Tue, 28 May 2024 14:28:52 +0200:
> While use of fsl_ifc driver with NAND flash is fine, as the fsl_ifc_nand
> driver selects FSL_IFC automatically, we need the CONFIG_FSL_IFC option to
> be selectable for platforms using fsl_ifc with NOR flash.
>
> Fixes: ea0c0ad6b6eb ("memory: Enable compile testing for most of the drivers")
> Signed-off-by: Esben Haabendal <esben@geanix.com>
Looks good to me.
Reviewed-by: Miquel Raynal <miquel.raynal@bootlin.com>
Thanks,
Miquèl
next prev parent reply other threads:[~2024-05-28 13:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-28 12:28 [PATCH v2 0/2] memory: fsl_ifc: Make FSL_IFC config visible and selectable Esben Haabendal
2024-05-28 12:28 ` [PATCH v2 1/2] " Esben Haabendal
2024-05-28 12:48 ` Miquel Raynal [this message]
2024-05-28 13:15 ` Christophe Leroy
2024-05-28 13:32 ` Krzysztof Kozlowski
2024-05-28 13:43 ` Esben Haabendal
2024-05-28 12:28 ` [PATCH v2 2/2] powerpc/configs: Update defconfig with now user-visible CONFIG_FSL_IFC Esben Haabendal
2024-05-28 13:00 ` Krzysztof Kozlowski
2024-05-28 13:33 ` Esben Haabendal
2024-05-28 13:47 ` Krzysztof Kozlowski
2024-05-29 8:14 ` Michael Ellerman
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=20240528144823.2ec929f6@xps-13 \
--to=miquel.raynal@bootlin.com \
--cc=aneesh.kumar@kernel.org \
--cc=esben@geanix.com \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mwalle@kernel.org \
--cc=naveen.n.rao@linux.ibm.com \
--cc=npiggin@gmail.com \
--cc=pratyush@kernel.org \
--cc=richard@nod.at \
--cc=tudor.ambarus@linaro.org \
--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;
as well as URLs for NNTP newsgroup(s).