On Wed, Jul 12, 2017 at 01:31:17PM +0200, Arnd Bergmann wrote:
> On Wed, Jul 12, 2017 at 1:16 PM, James Hogan <james.hogan@imgtec.com> wrote:
> > On Tue, Jul 11, 2017 at 06:31:17PM -0700, Palmer Dabbelt wrote:
[...]
> >> +RISC-V ARCHITECTURE
> >> +M:   Palmer Dabbelt <palmer@sifive.com>
> >> +M:   Albert Ou <albert@sifive.com>
> >> +L:   patches@groups.riscv.org
> >> +T:   git https://github.com/riscv/riscv-linux
> >> +S:   Supported
> >> +F:   arch/riscv/
> >
> > Should this include other tightly riscv specific drivers outside of
> > arch/riscv/ (or maybe they should have their own MAINTAINERS entries if
> > they aren't so tightly bound to the architecture or are maintained
> > separately)?
> >
> > drivers/clocksource/riscv_timer.c
> > drivers/irqchip/irq-riscv-intc.c
> > drivers/irqchip/irq-riscv-plic.c
> > drivers/tty/hvc/hvc_sbi.c
> > include/linux/timer_riscv.h
> >
> 
> I would suggest including a
> 
> K: riscv
> 
> keyword line that should catch the closely related drivers, and have
> separate entries for the rest. Maybe rename the hvc_sbi file
> to fall within that keyword match.
> 
>         Arnd

All good suggestions. Palmer, would you mind to take this patch from
here, to reduce the communication overhead? (Besides, you know better
than I what to include, anyway)


Jonathan