[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Y2JHw/y1oWkLpOb2@wendy>
Date: Wed, 2 Nov 2022 10:34:43 +0000
From: Conor Dooley <conor.dooley@...rochip.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
<palmer@...belt.com>
CC: Conor Dooley <conor@...nel.org>,
Paul Walmsley <paul.walmsley@...ive.com>,
Palmer Dabbelt <palmer@...belt.com>,
Albert Ou <aou@...s.berkeley.edu>,
Michael Turquette <mturquette@...libre.com>,
Stephen Boyd <sboyd@...nel.org>,
Jiri Slaby <jirislaby@...nel.org>,
<linux-riscv@...ts.infradead.org>, <linux-kernel@...r.kernel.org>,
<linux-clk@...r.kernel.org>, <linux-serial@...r.kernel.org>
Subject: Re: [PATCH 0/6] RISC-V: stop selecting device drivers in Kconfig.socs
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@...rochip.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.
Powered by blists - more mailing lists