From: Guillaume La Roque <glaroque@baylibre.com>
To: Arnd Bergmann <arnd@arndb.de>, Nishanth Menon <nm@ti.com>,
Tero Kristo <kristo@kernel.org>
Cc: Andrew Davis <afd@ti.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] firmware: config: ti-sci: Default set to ARCH_K3 for the ti sci driver
Date: Thu, 20 Mar 2025 14:41:45 +0100 [thread overview]
Message-ID: <818de9a7-b308-4e00-9eba-3f58e1d89bbd@baylibre.com> (raw)
In-Reply-To: <c506a805-9221-4afe-8d98-af0ca97a1fd2@app.fastmail.com>
Le 19/03/2025 à 22:45, Arnd Bergmann a écrit :
> On Thu, Feb 20, 2025, at 14:31, Guillaume La Roque wrote:
>> With ARCH_K3=y we cannot enable TI_SCI_PROTOCOL=m because
>> ARCH_K3 selects TI_SCI_PROTOCOL.
>>
>> Modify the logic to enable TI_SCI_PROTOCOL by default when ARCH_K3=y
>> allowing us to submit a future patch to remove select on ARCH_K3 without
>> breaking existing users.
>>
>> Signed-off-by: Guillaume La Roque <glaroque@baylibre.com>
>> ---
>> Link to comment done on last serie [1] we come back on first version of
>> series[2] to not use imply but set deps on ARCH_K3 in driver directly.
>> An other patch will be sent to update Kconfig.platform when this patch
>> is merged.
> I just merged the patch and hadn't seen the earlier discussion,
> just two small notes from me:
>
> - thanks for doing it this way instead of the backwards 'imply'
> - there is really no need to split it into two steps, since the
> change to the Kconfig.platforms file logically goes with this
> one and I would merge both through the SoC tree, having it
> as a single patch would make sense.
>
> Arnd
Hi,
thanks for merged.
i do what we ask me in review in fact or perhaps i misunderstand sorry
for that.
Guillaume
prev parent reply other threads:[~2025-03-20 13:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-20 13:31 Guillaume La Roque
2025-02-26 18:49 ` Nishanth Menon
2025-03-19 21:45 ` Arnd Bergmann
2025-03-20 13:41 ` Guillaume La Roque [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=818de9a7-b308-4e00-9eba-3f58e1d89bbd@baylibre.com \
--to=glaroque@baylibre.com \
--cc=afd@ti.com \
--cc=arnd@arndb.de \
--cc=kristo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@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
all inboxes | Powered by JetHome®