From: Stephen Boyd <sboyd@kernel.org>
To: Albert Ou <aou@eecs.berkeley.edu>,
Conor Dooley <conor.dooley@microchip.com>,
Conor Dooley <conor@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Paul Walmsley <paul.walmsley@sifive.com>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-clk@vger.kernel.org, linux-serial@vger.kernel.org
Subject: Re: [PATCH 1/6] clk: sifive: select by default if SOC_SIFIVE
Date: Mon, 17 Oct 2022 14:07:18 -0700 [thread overview]
Message-ID: <20221017210721.3E280C433C1@smtp.kernel.org> (raw)
In-Reply-To: <20221005171348.167476-2-conor@kernel.org>
Quoting Conor Dooley (2022-10-05 10:13:44)
> From: Conor Dooley <conor.dooley@microchip.com>
>
> With the aim of dropping direct selects of drivers from Kconfig.socs,
> default the SiFive clock drivers to the value of SOC_SIFIVE.
>
> Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
> ---
Applied to clk-fixes
next prev parent reply other threads:[~2022-10-17 21:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-05 17:13 [PATCH 0/6] RISC-V: stop selecting device drivers in Kconfig.socs Conor Dooley
2022-10-05 17:13 ` [PATCH 1/6] clk: sifive: select by default if SOC_SIFIVE Conor Dooley
2022-10-17 21:07 ` Stephen Boyd [this message]
2022-10-05 17:13 ` [PATCH 2/6] serial: " Conor Dooley
2022-10-05 17:13 ` [PATCH 3/6] serial: sifive: select by default if SOC_CANAAN Conor Dooley
2022-10-05 17:13 ` [PATCH 4/6] riscv: stop selecting the PolarFire SoC clock driver Conor Dooley
2022-10-05 17:13 ` [PATCH 5/6] riscv: stop selecting SiFive clock and serial drivers directly Conor Dooley
2022-10-05 17:13 ` [PATCH 6/6] riscv: stop directly selecting drivers for SOC_CANAAN Conor Dooley
2022-10-30 12:02 ` [PATCH 0/6] RISC-V: stop selecting device drivers in Kconfig.socs Conor Dooley
2022-11-02 7:09 ` Greg Kroah-Hartman
2022-11-02 10:34 ` Conor Dooley
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=20221017210721.3E280C433C1@smtp.kernel.org \
--to=sboyd@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=conor.dooley@microchip.com \
--cc=conor@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-serial@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.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;
as well as URLs for NNTP newsgroup(s).