From: Krzysztof Kozlowski <krzk@kernel.org>
To: Michael Ellerman <mpe@ellerman.id.au>,
Esben Haabendal <esben@geanix.com>,
Tudor Ambarus <tudor.ambarus@linaro.org>,
Pratyush Yadav <pratyush@kernel.org>,
Michael Walle <mwalle@kernel.org>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
Nicholas Piggin <npiggin@gmail.com>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
"Aneesh Kumar K.V" <aneesh.kumar@kernel.org>,
"Naveen N. Rao" <naveen.n.rao@linux.ibm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>
Cc: linuxppc-dev@lists.ozlabs.org, linux-mtd@lists.infradead.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 2/3] powerpc/configs: Update defconfig with now user-visible CONFIG_FSL_IFC
Date: Tue, 2 Jul 2024 14:33:34 +0200 [thread overview]
Message-ID: <6103ffa6-68df-45a3-ada6-1f8d541d8f02@kernel.org> (raw)
In-Reply-To: <87v81oj93e.fsf@mail.lhotse>
On 02/07/2024 14:01, Michael Ellerman wrote:
> Krzysztof Kozlowski <krzk@kernel.org> writes:
>> On 30/05/2024 16:46, Esben Haabendal wrote:
>>> With CONFIG_FSL_IFC now being user-visible, and thus changed from a select
>>> to depends in CONFIG_MTD_NAND_FSL_IFC, the dependencies needs to be
>>> selected in defconfigs.
>>>
>>> Signed-off-by: Esben Haabendal <esben@geanix.com>
>>
>> Anyone is going to pick this up?
>
> Doesn't it need to be merged along with patch 1?
Well, it's late to talk about this... I replied 3 weeks ago, when taking
the first patch, that I don't consider defconfig as a guaranteed feature
thus no hard-bisectability requirement. Three weeks and no comments on
that, so no, this does not have to be merged with patch 1.
The best if it goes the same cycle, though. So for v6.11.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-07-02 12:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-30 14:46 [PATCH v3 0/3] memory: fsl_ifc: Make FSL_IFC config visible and selectable Esben Haabendal
2024-05-30 14:46 ` [PATCH v3 1/3] " Esben Haabendal
2024-06-12 8:26 ` (subset) " Krzysztof Kozlowski
2024-05-30 14:46 ` [PATCH v3 2/3] powerpc/configs: Update defconfig with now user-visible CONFIG_FSL_IFC Esben Haabendal
2024-07-02 7:00 ` Krzysztof Kozlowski
2024-07-02 12:01 ` Michael Ellerman
2024-07-02 12:33 ` Krzysztof Kozlowski [this message]
2024-05-30 14:46 ` [PATCH v3 3/3] arm64/configs: " Esben Haabendal
2024-07-02 7:00 ` Krzysztof Kozlowski
2024-07-06 23:10 ` [PATCH v3 0/3] memory: fsl_ifc: Make FSL_IFC config visible and selectable 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=6103ffa6-68df-45a3-ada6-1f8d541d8f02@kernel.org \
--to=krzk@kernel.org \
--cc=aneesh.kumar@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=christophe.leroy@csgroup.eu \
--cc=esben@geanix.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=miquel.raynal@bootlin.com \
--cc=mpe@ellerman.id.au \
--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 \
--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;
as well as URLs for NNTP newsgroup(s).