From mboxrd@z Thu Jan  1 00:00:00 1970
From: Philipp Zabel <p.zabel@pengutronix.de>
Subject: Please add reset/next and reset/fixes to linux-next
Date: Mon, 29 May 2017 15:23:17 +0200
Message-ID: <1496064197.17695.72.camel@pengutronix.de>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Return-path: <linux-next-owner@vger.kernel.org>
Received: from metis.ext.4.pengutronix.de ([92.198.50.35]:37163 "EHLO
        metis.ext.4.pengutronix.de" rhost-flags-OK-OK-OK-OK)
        by vger.kernel.org with ESMTP id S1750913AbdE2NXU (ORCPT
        <rfc822;linux-next@vger.kernel.org>);
        Mon, 29 May 2017 09:23:20 -0400
Sender: linux-next-owner@vger.kernel.org
List-ID: <linux-next.vger.kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, kernel@pengutronix.de

Hi Stephen,

could you add the reset/next and reset/fixes branches to the linux-next
tree? I use those to stage reset framework and driver patches before
sending them off to be merged via arm-soc.

https://git.pengutronix.de/git/pza/linux reset/fixes
https://git.pengutronix.de/git/pza/linux reset/next

regards
Philipp