linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Palmer Dabbelt <palmer@dabbelt.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-kernel@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
	Olof Johansson <olof@lixom.net>,
	patches@groups.riscv.org
Subject: Pull Request for linux-next
Date: Tue, 31 Oct 2017 13:43:26 -0700 (PDT)	[thread overview]
Message-ID: <mhng-30337818-ba50-4186-9d35-a868d26ab5ac@palmer-si-x1c4> (raw)

I'd like to request that you add the following tree to linux-next

  git://git.kernel.org/pub/scm/linux/kernel/git/palmer/linux.git for-linux-next

It contains the RISC-V port, which has been through 9 rounds of review on
various public Linux mailing lists.  While the port isn't perfect, I've split
out the commits for which we have general consensus and tagged them with
"for-linux-next" (as opposed to our "riscv-next" tree).  I intend to continue
updating the "for-linux-next" tag as we get more patches in good shape, with
the idea being that the RISC-V arch port patches go in through here.

I know it's a bit late in the cycle, but we've been waiting for you to come
back from vacation before submitting the request so it didn't get lost
somewhere.

Thanks!

             reply	other threads:[~2017-10-31 20:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-31 20:43 Palmer Dabbelt [this message]
2017-10-31 21:21 ` Pull Request for linux-next Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2018-02-25  7:59 Tobin C. Harding
2018-02-25 20:54 ` Stephen Rothwell
2018-02-25 22:13   ` Tobin C. Harding
2018-02-21  8:14 Greentime Hu
2018-02-22  0:29 ` Stephen Rothwell
2018-02-22  3:36   ` Greentime Hu
2018-02-22  4:28     ` Stephen Rothwell
2009-11-15 16:35 PULL request " Tejun Heo
2009-11-15 22:52 ` Stephen Rothwell

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=mhng-30337818-ba50-4186-9d35-a868d26ab5ac@palmer-si-x1c4 \
    --to=palmer@dabbelt.com \
    --cc=arnd@arndb.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olof@lixom.net \
    --cc=patches@groups.riscv.org \
    --cc=sfr@canb.auug.org.au \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).