Message-Id: <20170712013130.14792-1-palmer@dabbelt.com>
Date:   Tue, 11 Jul 2017 18:31:13 -0700
From:   Palmer Dabbelt <palmer@...belt.com>
To:     Olof Johansson <olof@...om.net>, Arnd Bergmann <arnd@...db.de>,
        akpm@...ux-foundation.org
Cc:     albert@...ive.com, yamada.masahiro@...ionext.com, mmarek@...e.com,
        will.deacon@....com, peterz@...radead.org, boqun.feng@...il.com,
        mingo@...hat.com, daniel.lezcano@...aro.org, tglx@...utronix.de,
        jason@...edaemon.net, marc.zyngier@....com,
        gregkh@...uxfoundation.org, jslaby@...e.com, davem@...emloft.net,
        mchehab@...nel.org, sfr@...b.auug.org.au, fweisbec@...il.com,
        viro@...iv.linux.org.uk, mcgrof@...nel.org, dledford@...hat.com,
        bart.vanassche@...disk.com, sstabellini@...nel.org,
        daniel.vetter@...ll.ch, mpe@...erman.id.au, msalter@...hat.com,
        nicolas.dichtel@...nd.com, james.hogan@...tec.com,
        paul.gortmaker@...driver.com, linux@...ck-us.net,
        heiko.carstens@...ibm.com, schwidefsky@...ibm.com,
        linux-kernel@...r.kernel.org, patches@...ups.riscv.org
Subject: RISC-V Linux Port v6

While it's only been a day since the last patch set (which might be a bit
fast), I've generally been spinning new patch sets whenever I get through my
inbox.  For my other patch sets I've managed to get buried in a week's worth of
email in a few hours, but for this one it appears there's been significantly
less feedback so I've managed to get through everything.  I'm hoping that's a
good sign: either I've started to figure out what I'm doing or the code has
gotten better -- hopefully it doesn't mean everyone else has given up :).

As it's been only a day, the changes are pretty minimal:

 * The patch set is now based on linux-next/master, which I believe is a better
   base now that we're getting closer to upstream.
 * EARLY_PRINTK is no longer an option.  Since the SBI console is reasonable,
   there's no penalty to enabling it (and thus no benefit to disabling it).
 * The mmap syscalls were refactored a bit.

At this point I'm not really sure how to proceed: reviews have calmed down
quite a bit over the last two weeks, but I'm not familiar with the Linux
development process enough to know how to get closer to upstream.  Is this
ready for inclusion into another tree?  If so, is linux-next the right tree to
work off of?

Of course, if anyone has outstanding code reviews then feel free to submit them
either to this patch set or a previous one (v5 is essentially the same, and v4
is mostly some small SMP fixes).  I don't want to rush anyone by re-submitting
so quickly, it's just that my usual protocol has been sped up.

As usual, the patch set has been posted to our Git Hub page

  https://github.com/riscv/riscv-linux/tree/riscv-for-submission-v6

Thanks to everyone for all your help!

[PATCH 01/17] lib: Add shared copies of some GCC library routines
[PATCH 02/17] pci: Add a generic, weakly-linked
[PATCH 03/17] pci: Add a generic, weakly-linked pcibios_fixup_bus
[PATCH 04/17] MAINTAINERS: Add RISC-V
[PATCH 05/17] clocksource: New RISC-V SBI timer driver
[PATCH 06/17] irqchip: RISC-V Local Interrupt Controller Driver
[PATCH 07/17] irqchip: New RISC-V PLIC Driver
[PATCH 08/17] tty: New RISC-V SBI console driver
[PATCH 09/17] RISC-V: Init and Halt Code
[PATCH 10/17] RISC-V: Atomic and Locking Code
[PATCH 11/17] RISC-V: Generic library routines and assembly
[PATCH 12/17] RISC-V: ELF and module implementation
[PATCH 13/17] RISC-V: Task implementation
[PATCH 14/17] RISC-V: Device, timer, IRQs, and the SBI
[PATCH 15/17] RISC-V: Paging and MMU
[PATCH 16/17] RISC-V: User-facing API
[PATCH 17/17] RISC-V: Build Infastructure

Powered by blists - more mailing lists