From: Nikita Shubin <nikita.shubin@maquefel.me>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "Russell King" <linux@armlinux.org.uk>,
"Hartley Sweeten" <hsweeten@visionengravers.com>,
"Alexander Sverdlin" <alexander.sverdlin@gmail.com>,
"Arnd Bergmann" <arnd@arndb.de>,
"Ard Biesheuvel" <ardb@kernel.org>,
"Mike Rapoport" <rppt@kernel.org>,
"Gregory Fong" <gregory.0xf0@gmail.com>,
"Geert Uytterhoeven" <geert+renesas@glider.be>,
"YiFei Zhu" <yifeifz2@illinois.edu>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Linux ARM" <linux-arm-kernel@lists.infradead.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [RFC][PATCH 0/1] ep93xx: clock: convert in-place
Date: Tue, 25 May 2021 14:38:58 +0300 [thread overview]
Message-ID: <20210525143858.235c9318@redslave.neermore.group> (raw)
In-Reply-To: <CACRpkdYkb+-y366esEDZBDMNQ7s6zOfHEPotNaTUi3m95QrBFw@mail.gmail.com>
On Tue, 25 May 2021 12:19:27 +0200
Linus Walleij <linus.walleij@linaro.org> wrote:
> move out as many drivers as possible to be modules and
> not compiled into the static kernel. Do we have candidates
> for that? Are people normally using modules on EP93xx?
AFAIK there is nothing left to convert. Everything is already done as
modules.
next prev parent reply other threads:[~2021-05-25 11:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-25 8:33 [RFC][PATCH 0/1] ep93xx: clock: convert in-place Nikita Shubin
2021-05-25 8:33 ` [PATCH 1/1] ep93xx: clock: convert in-place to COMMON_CLK Nikita Shubin
2021-05-25 19:35 ` Alexander Sverdlin
2021-06-11 22:42 ` Alexander Sverdlin
2021-06-12 9:18 ` Geert Uytterhoeven
2021-06-13 20:11 ` Alexander Sverdlin
2021-06-17 8:26 ` Nikita Shubin
2021-05-25 10:19 ` [RFC][PATCH 0/1] ep93xx: clock: convert in-place Linus Walleij
2021-05-25 11:38 ` Nikita Shubin [this message]
2021-05-25 19:39 ` Alexander Sverdlin
2021-05-26 6:11 ` Nikita Shubin
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=20210525143858.235c9318@redslave.neermore.group \
--to=nikita.shubin@maquefel.me \
--cc=alexander.sverdlin@gmail.com \
--cc=ardb@kernel.org \
--cc=arnd@arndb.de \
--cc=geert+renesas@glider.be \
--cc=gregory.0xf0@gmail.com \
--cc=hsweeten@visionengravers.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=rppt@kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
--cc=yifeifz2@illinois.edu \
/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).