Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1757246AbcK3NXF (ORCPT <rfc822;w@1wt.eu>);
        Wed, 30 Nov 2016 08:23:05 -0500
Received: from mail-pg0-f68.google.com ([74.125.83.68]:33109 "EHLO
        mail-pg0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1753112AbcK3NW4 (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Wed, 30 Nov 2016 08:22:56 -0500
From: Stafford Horne <shorne@gmail.com>
X-Google-Original-From: Stafford Horne <shorne@lianli.shorne-pla.net>
Date: Wed, 30 Nov 2016 22:22:41 +0900 (JST)
To: sfr@canb.auug.org.au
cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
        openrisc@lists.librecores.org
Subject: Add openrisc for-next branch to linux-next
Message-ID: <alpine.LFD.2.20.1611302214520.29569@lianli.shorne-pla.net>
User-Agent: Alpine 2.20 (LFD 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 300
Lines: 11

Hi Stephen,

I have been working on getting the OpenRISC backlog of fixes sorted out 
for upstream.  Can this branch be added to linux-next?

   git://github.com/openrisc/linux.git for-next

These have been through a few reviews and we plan to ask Linus to pull in 
the next merge window.

-Stafford