From: Simon Horman <horms@verge.net.au>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Khiem Nguyen <khiem.nguyen.xt@renesas.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Magnus Damm <magnus.damm@gmail.com>,
Ben Dooks <ben.dooks@codethink.co.uk>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Linux-sh list <linux-sh@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
dmaengine@vger.kernel.org
Subject: Re: [PATCH v2 0/7] ARM: shmobile: koelsch reference: Enable DMA for QSPI
Date: Wed, 4 Jun 2014 08:29:06 +0900 [thread overview]
Message-ID: <20140603232906.GC19407@verge.net.au> (raw)
In-Reply-To: <CAMuHMdVnmsjf29X4KF0co+WwUh9i0DQe6hE0hNFMCv-+GeHP_w@mail.gmail.com>
On Tue, Jun 03, 2014 at 09:05:42AM +0200, Geert Uytterhoeven wrote:
> On Tue, Jun 3, 2014 at 6:36 AM, Khiem Nguyen
> <khiem.nguyen.xt@renesas.com> wrote:
> > I think this patch series should be divided into 2 parts,
> > one for DMA in general and one for DMA supporting QSPI.
> >
> > How do you think about it ?
>
> I don't think it's worth splitting off just the last patch into a separate
> series.
>
> This is a series, not a single patch. The applyer can always drop some
> patches.
FWIW, that seems reasonable to me.
next prev parent reply other threads:[~2014-06-03 23:29 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-02 13:42 [PATCH v2 0/7] ARM: shmobile: koelsch reference: Enable DMA for QSPI Geert Uytterhoeven
2014-06-02 13:42 ` [PATCH v2 1/7] DMA: shdma: Add r8a7791 support Geert Uytterhoeven
2014-06-04 11:29 ` Laurent Pinchart
2014-06-04 11:39 ` Geert Uytterhoeven
2014-06-02 13:42 ` [PATCH v2 2/7] DMA: shdma: Spelling s/controll/control/ Geert Uytterhoeven
2014-06-02 13:50 ` Ben Dooks
2014-06-04 11:25 ` Laurent Pinchart
2014-06-02 13:42 ` [PATCH v2 3/7] ARM: shmobile: r8a7791 dtsi: add SYS-DMAC clocks Geert Uytterhoeven
2014-06-04 11:24 ` Laurent Pinchart
2014-06-04 23:29 ` Simon Horman
2014-06-02 13:42 ` [PATCH v2 4/7] ARM: shmobile: r8a7791: Add SYS-DMAC channel definitions for bindings Geert Uytterhoeven
2014-06-02 13:52 ` Ben Dooks
2014-06-03 7:53 ` Geert Uytterhoeven
2014-06-04 11:30 ` Laurent Pinchart
2014-06-04 11:45 ` Ben Dooks
2014-06-04 11:53 ` Laurent Pinchart
2014-06-02 13:42 ` [PATCH v2 5/7] ARM: shmobile: r8a7791 dtsi: Add SYS-DMAC0 and SYS-DMAC1 nodes Geert Uytterhoeven
2014-06-04 12:25 ` Laurent Pinchart
2014-06-05 0:17 ` Kuninori Morimoto
2014-06-05 12:37 ` Laurent Pinchart
2014-06-06 11:22 ` Ben Dooks
2014-06-02 13:42 ` [PATCH v2 6/7] ARM: shmobile: koelsch dts: Enable sysdma0 and sysdma1 Geert Uytterhoeven
2014-06-02 13:42 ` [PATCH v2 7/7] ARM: shmobile: r8a7791 dtsi: Enable DMA for QSPI Geert Uytterhoeven
2014-06-02 13:53 ` Ben Dooks
2014-06-02 13:58 ` [PATCH v2 0/7] ARM: shmobile: koelsch reference: " Ben Dooks
2014-06-03 4:36 ` Khiem Nguyen
2014-06-03 7:05 ` Geert Uytterhoeven
2014-06-03 23:29 ` Simon Horman [this message]
2014-06-04 0:18 ` Khiem Nguyen
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=20140603232906.GC19407@verge.net.au \
--to=horms@verge.net.au \
--cc=ben.dooks@codethink.co.uk \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=khiem.nguyen.xt@renesas.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).