From mboxrd@z Thu Jan  1 00:00:00 1970
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: Re: [PATCH] spi: Remove SPI_BUFSIZ restriction on
 spi_write_then_read()
Date: Fri, 7 Dec 2012 12:41:41 +0900
Message-ID: <20121207034140.GB26070@opensource.wolfsonmicro.com>
References: <1354420465-29315-1-git-send-email-broonie@opensource.wolfsonmicro.com>
 <20121206000026.A620D3E0E22@localhost>
 <20121206053732.GD10867@opensource.wolfsonmicro.com>
 <20121206140427.8E5673E089D@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: spi-devel-general@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
To: Grant Likely <grant.likely@secretlab.ca>
Return-path: <linux-kernel-owner@vger.kernel.org>
Content-Disposition: inline
In-Reply-To: <20121206140427.8E5673E089D@localhost>
Sender: linux-kernel-owner@vger.kernel.org
List-Id: linux-spi.vger.kernel.org

On Thu, Dec 06, 2012 at 02:04:27PM +0000, Grant Likely wrote:

> Alright, applied. I've also merged in your spi-next tree. Let me know if
> that causes problems because it needs to be rebased.

No problem - do you just want to take over the SPI tree again or should
I carry on applying things?