| Message ID | 20221005171348.167476-1-conor@kernel.org (mailing list archive) |
|---|---|
| Headers | show |
| Series | RISC-V: stop selecting device drivers in Kconfig.socs | expand |
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 >
On Sun, Oct 30, 2022 at 12:02:09PM +0000, Conor Dooley wrote: > 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. Sorry for the delay, I'll take both of them through the tty/serial tree. thanks, greg k-h
On Wed, Nov 02, 2022 at 08:09:32AM +0100, Greg Kroah-Hartman wrote: > On Sun, Oct 30, 2022 at 12:02:09PM +0000, Conor Dooley wrote: > > 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. > > Sorry for the delay, I'll take both of them through the tty/serial tree. nw Greg, thanks. @Palmer, I'll re-submit the Kconfig.socs bits of this after v6.2-rc1. Thanks, Conor.
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. 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(-)