From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Hari Nagalla <hnagalla@ti.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: catalin.marinas@arm.com, will@kernel.org,
quic_bjorande@quicinc.com, arnd@arndb.de, treding@nvidia.com,
dmitry.baryshkov@linaro.org, nfraprado@collabora.com,
broonie@kernel.org, rafal@milecki.pl
Subject: Re: [PATCH 2/2] arm64: defconfig: enable TI K3 R5 and DSP remote proc drivers
Date: Wed, 19 Apr 2023 14:46:45 +0200 [thread overview]
Message-ID: <9a2ed4b6-13b7-9e65-263c-d2b08e11da00@linaro.org> (raw)
In-Reply-To: <ae49267f-4534-e489-4bb7-946944a9a04c@ti.com>
On 19/04/2023 13:52, Hari Nagalla wrote:
> On 4/19/23 06:43, Krzysztof Kozlowski wrote:
>> Why two separate patches for simple defconfig change?
> The intention is to separate commits for enabling mailbox driver from
> remote proc drivers. The mailbox driver is used by the TI K3 system
> controller interface (SCI) driver as well, which is independent of
> remote proc drivers.
Yeah, but why? This is simple defconfig change, just enabling drivers
for same platform. With such arguments are we going to enable all
drivers everywhere one-by-one?
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-04-19 12:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-19 11:39 [PATCH 0/2] arm64: defconfig: enable TI OMAP2 mailbox and R5/DSP " Hari Nagalla
2023-04-19 11:39 ` [PATCH 1/2] arm64: defconfig; enable TI OMAP2 mailbox driver Hari Nagalla
2023-04-19 11:39 ` [PATCH 2/2] arm64: defconfig: enable TI K3 R5 and DSP remote proc drivers Hari Nagalla
2023-04-19 11:43 ` Krzysztof Kozlowski
2023-04-19 11:52 ` Hari Nagalla
2023-04-19 12:46 ` Krzysztof Kozlowski [this message]
2023-04-20 8:47 ` Hari Nagalla
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=9a2ed4b6-13b7-9e65-263c-d2b08e11da00@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=dmitry.baryshkov@linaro.org \
--cc=hnagalla@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nfraprado@collabora.com \
--cc=quic_bjorande@quicinc.com \
--cc=rafal@milecki.pl \
--cc=treding@nvidia.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
all inboxes | Powered by JetHome®