From: Mark Brown <broonie@kernel.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
linux-spi <linux-spi@vger.kernel.org>,
Linux-sh list <linux-sh@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Geert Uytterhoeven <geert+renesas@linux-m68k.org>
Subject: Re: [PATCH v5] spi: rspi: Add DT support
Date: Thu, 30 Jan 2014 11:25:58 +0000 [thread overview]
Message-ID: <20140130112558.GJ22609@sirena.org.uk> (raw)
In-Reply-To: <CAMuHMdX+EUUHxOgc8RF=C=qdYiOc8h+su4r-=HAhWXUqEivSvw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 642 bytes --]
On Wed, Jan 29, 2014 at 08:10:34PM +0100, Geert Uytterhoeven wrote:
> On Wed, Jan 29, 2014 at 7:00 PM, Mark Brown <broonie@kernel.org> wrote:
> > well?
> As there were no code changes in v5 of "spi: rspi: Add DT support",
> Patch "[14/14] spi: rspi: Add support for Quad and Dual SPI Transfers on QSPI"
> should still apply fine.
> Do you want me to resubmit?
I see you did actually resend before I saw this but yes, in general it's
better to resend stuff. If you start applying version X of one patch
with version Y of another it's more work and there's a lot of things
that can go wrong between user error and unexpected dependencies.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2014-01-30 11:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-28 9:21 Geert Uytterhoeven
2014-01-29 18:00 ` Mark Brown
2014-01-29 19:10 ` Geert Uytterhoeven
2014-01-30 11:25 ` Mark Brown [this message]
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=20140130112558.GJ22609@sirena.org.uk \
--to=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@linux-m68k.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®