From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: spi-devel-general@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] spi: Remove SPI_BUFSIZ restriction on spi_write_then_read()
Date: Fri, 7 Dec 2012 12:41:41 +0900 [thread overview]
Message-ID: <20121207034140.GB26070@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20121206140427.8E5673E089D@localhost>
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?
next prev parent reply other threads:[~2012-12-07 3:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-02 3:54 [PATCH] spi: Remove SPI_BUFSIZ restriction on spi_write_then_read() Mark Brown
2012-12-06 0:00 ` Grant Likely
2012-12-06 5:37 ` Mark Brown
[not found] ` <20121206053732.GD10867-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2012-12-06 14:04 ` Grant Likely
2012-12-06 14:04 ` Grant Likely
2012-12-07 3:41 ` Mark Brown [this message]
[not found] ` <20121207034140.GB26070-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2012-12-07 14:04 ` Grant Likely
2012-12-07 14:04 ` Grant Likely
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=20121207034140.GB26070@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=spi-devel-general@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.