From: Conor Dooley <conor@kernel.org>
To: Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>,
Conor Dooley <conor.dooley@microchip.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 0/6] RISC-V: stop selecting device drivers in Kconfig.socs
Date: Sun, 30 Oct 2022 12:02:09 +0000 [thread overview]
Message-ID: <Y15nwXmn7rToJkH2@spud> (raw)
In-Reply-To: <20221005171348.167476-1-conor@kernel.org>
On Wed, Oct 05, 2022 at 06:13:43PM +0100, Conor Dooley wrote:
> From: Conor Dooley <conor.dooley@microchip.com>
>
> As my RFC [0] series doing the symbol name changes has not yet reached
> consensus, I've split out the removal of device driver selects into a
> new series. I kept the plic as a direct select - although given how Maz
> is treating the SiFive plic driver as the RISC-V plic driver, maybe that
> should just be selected by default at an arch level...
>
> I assume the individual patches can go via their subsystems & I'll
> resubmit the arch/riscv patches a cycle later? I'm not in any rush.
Hey,
What's the story here with the two serial patches, they just waiting for
an Ack? I think these are archived on the riscv patchwork, so if that is
the case I'll unarchive them and mark as needing one.
Thanks,
Conor.
>
> 0 - https://lore.kernel.org/linux-riscv/20220923185605.1900083-1-conor@kernel.org/
>
> Conor Dooley (6):
> clk: sifive: select by default if SOC_SIFIVE
> serial: sifive: select by default if SOC_SIFIVE
> serial: sifive: select by default if SOC_CANAAN
> riscv: stop selecting the PolarFire SoC clock driver
> riscv: stop selecting SiFive clock and serial drivers directly
> riscv: stop directly selecting drivers for SOC_CANAAN
>
> arch/riscv/Kconfig.socs | 8 --------
> drivers/clk/sifive/Kconfig | 4 +++-
> drivers/tty/serial/Kconfig | 2 ++
> 3 files changed, 5 insertions(+), 9 deletions(-)
>
> --
> 2.37.3
>
WARNING: multiple messages have this Message-ID (diff)
From: Conor Dooley <conor@kernel.org>
To: Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>,
Conor Dooley <conor.dooley@microchip.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 0/6] RISC-V: stop selecting device drivers in Kconfig.socs
Date: Sun, 30 Oct 2022 12:02:09 +0000 [thread overview]
Message-ID: <Y15nwXmn7rToJkH2@spud> (raw)
In-Reply-To: <20221005171348.167476-1-conor@kernel.org>
On Wed, Oct 05, 2022 at 06:13:43PM +0100, Conor Dooley wrote:
> From: Conor Dooley <conor.dooley@microchip.com>
>
> As my RFC [0] series doing the symbol name changes has not yet reached
> consensus, I've split out the removal of device driver selects into a
> new series. I kept the plic as a direct select - although given how Maz
> is treating the SiFive plic driver as the RISC-V plic driver, maybe that
> should just be selected by default at an arch level...
>
> I assume the individual patches can go via their subsystems & I'll
> resubmit the arch/riscv patches a cycle later? I'm not in any rush.
Hey,
What's the story here with the two serial patches, they just waiting for
an Ack? I think these are archived on the riscv patchwork, so if that is
the case I'll unarchive them and mark as needing one.
Thanks,
Conor.
>
> 0 - https://lore.kernel.org/linux-riscv/20220923185605.1900083-1-conor@kernel.org/
>
> Conor Dooley (6):
> clk: sifive: select by default if SOC_SIFIVE
> serial: sifive: select by default if SOC_SIFIVE
> serial: sifive: select by default if SOC_CANAAN
> riscv: stop selecting the PolarFire SoC clock driver
> riscv: stop selecting SiFive clock and serial drivers directly
> riscv: stop directly selecting drivers for SOC_CANAAN
>
> arch/riscv/Kconfig.socs | 8 --------
> drivers/clk/sifive/Kconfig | 4 +++-
> drivers/tty/serial/Kconfig | 2 ++
> 3 files changed, 5 insertions(+), 9 deletions(-)
>
> --
> 2.37.3
>
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2022-10-30 12:02 UTC|newest]
Thread overview: 22+ 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 ` Conor Dooley
2022-10-05 17:13 ` [PATCH 1/6] clk: sifive: select by default if SOC_SIFIVE Conor Dooley
2022-10-05 17:13 ` Conor Dooley
2022-10-17 21:07 ` Stephen Boyd
2022-10-17 21:07 ` Stephen Boyd
2022-10-05 17:13 ` [PATCH 2/6] serial: " Conor Dooley
2022-10-05 17:13 ` 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 ` 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 ` 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 ` Conor Dooley
2022-10-05 17:13 ` [PATCH 6/6] riscv: stop directly selecting drivers for SOC_CANAAN Conor Dooley
2022-10-05 17:13 ` Conor Dooley
2022-10-30 12:02 ` Conor Dooley [this message]
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 7:09 ` Greg Kroah-Hartman
2022-11-02 10:34 ` Conor Dooley
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=Y15nwXmn7rToJkH2@spud \
--to=conor@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=conor.dooley@microchip.com \
--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 \
--cc=sboyd@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.