From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753814AbdJaUn3 (ORCPT ); Tue, 31 Oct 2017 16:43:29 -0400 Received: from mail-pg0-f46.google.com ([74.125.83.46]:49328 "EHLO mail-pg0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753593AbdJaUn1 (ORCPT ); Tue, 31 Oct 2017 16:43:27 -0400 X-Google-Smtp-Source: ABhQp+Tl4R/0LYjaHR4iFRGHH3i1nuwu2GXdjk2NRcfCT5YGfIM11JE6k2sB6/1WAKSXBb4UiWqOcA== Date: Tue, 31 Oct 2017 13:43:26 -0700 (PDT) X-Google-Original-Date: Tue, 31 Oct 2017 13:43:12 PDT (-0700) Subject: Pull Request for linux-next CC: linux-kernel@vger.kernel.org, Arnd Bergmann , Olof Johansson , patches@groups.riscv.org From: Palmer Dabbelt To: Stephen Rothwell Message-ID: Mime-Version: 1.0 (MHng) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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!