From: Nishanth Menon <nm@ti.com>
To: Andrew Davis <afd@ti.com>
Cc: Arnd Bergmann <arnd@arndb.de>, Arnd Bergmann <arnd@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Martyn Welch <martyn.welch@collabora.com>,
Hari Nagalla <hnagalla@ti.com>,
Jassi Brar <jassisinghbrar@gmail.com>,
<linux-remoteproc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mailbox, remoteproc: k3-m4+: fix compile testing
Date: Tue, 15 Oct 2024 06:47:27 -0500 [thread overview]
Message-ID: <20241015114727.57usuxrhpapiofvg@fretted> (raw)
In-Reply-To: <585e5471-8a49-43cd-afba-055855be8e75@ti.com>
On 12:26-20241014, Andrew Davis wrote:
> Stubs only make sense for optional components, like GPIOLIB, where
> the driver using that component can continue when it is not available.
> For all drivers that depend on TI-SCI it is not optional. The dependent
> driver *will* fail to probe and error out. These stubs do nothing, and
> I'd like to just remove them.
Fair enough. I'd like to see a series where the drivers have
been converted to modules and we remove the "select" from
arch/arm64/Kconfig.platforms - we can then drop the stubs once the
modularization is complete.
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
next prev parent reply other threads:[~2024-10-15 11:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-07 13:23 [PATCH] mailbox, remoteproc: k3-m4+: fix compile testing Arnd Bergmann
2024-10-08 14:12 ` Mathieu Poirier
2024-10-09 17:12 ` Mathieu Poirier
2024-10-14 14:56 ` Andrew Davis
2024-10-14 15:43 ` Arnd Bergmann
2024-10-14 16:52 ` Nishanth Menon
2024-10-14 17:26 ` Andrew Davis
2024-10-15 11:47 ` Nishanth Menon [this message]
2024-10-16 15:26 ` Mathieu Poirier
2024-10-16 15:37 ` Andrew Davis
2024-10-16 16:02 ` Mathieu Poirier
2024-10-16 16:43 ` Andrew Davis
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=20241015114727.57usuxrhpapiofvg@fretted \
--to=nm@ti.com \
--cc=afd@ti.com \
--cc=andersson@kernel.org \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=hnagalla@ti.com \
--cc=jassisinghbrar@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=martyn.welch@collabora.com \
--cc=mathieu.poirier@linaro.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