From: Arnd Bergmann <arnd@arndb.de>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: Ulf Hansson <ulf.hansson@linaro.org>, Chris Ball <cjb@laptop.org>,
Simon <horms@verge.net.au>, Linux-SH <linux-sh@vger.kernel.org>,
linux-mmc <linux-mmc@vger.kernel.org>
Subject: Re: [PATCH 2/9] mmc: tmio: tmio_mmc_host has .dma
Date: Thu, 08 Jan 2015 14:09:17 +0100 [thread overview]
Message-ID: <9752854.8NpfY0BrAf@wuerfel> (raw)
In-Reply-To: <87387lu3sv.wl%kuninori.morimoto.gx@renesas.com>
On Thursday 08 January 2015 07:30:36 Kuninori Morimoto wrote:
>
> Hmm... indeed Arnd's patch and my patch-set conflicts.
> I have these patch / patch-set
> 1) header cleanup for tmio
> 2) slave_id cleanup for shdma
> 3) add DMA feature for sh_mobile_sdhi
>
> 1 ) and 2) conflicts here. one idea is like this
> 1) header cleanup for tmio
> 2) add DMA feature for sh_mobile_sdhi
> 3) slave_id cleanup for shdma
>
> 1) and 2) can be controled by Ulf with no-conflict.
> if these are merged correctly, I can send 3) to DMAEngine ML.
> Then, I can point the Ulf's branch as base branch.
>
> Arnd, Ulf what do you think ?
>
Sounds good. You could also leave out the sh_mobile_sdhi part from
3) patch to avoid the conflict, and add a comment in that place
as part of 2), to say that the slave_id assignment can be removed
once the other parts are done. That way, we know where we're at
if we want to remove slave_id from dma_slave_config and it's still
part of the sdhi driver.
Arnd
next prev parent reply other threads:[~2015-01-08 13:09 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-05 7:01 [PATCH 0/9]: mmc: tmio header cleanup Kuninori Morimoto
2015-01-05 7:02 ` [PATCH 1/9] mmc: tmio: add tmio_mmc_host_alloc/free() Kuninori Morimoto
2015-01-05 8:35 ` Geert Uytterhoeven
2015-01-05 8:39 ` Kuninori Morimoto
2015-01-05 7:02 ` [PATCH 2/9] mmc: tmio: tmio_mmc_host has .dma Kuninori Morimoto
2015-01-05 8:43 ` Arnd Bergmann
2015-01-05 9:35 ` Kuninori Morimoto
2015-01-05 21:33 ` Arnd Bergmann
2015-01-06 0:20 ` Kuninori Morimoto
2015-01-06 13:24 ` Arnd Bergmann
2015-01-07 1:45 ` Kuninori Morimoto
2015-01-06 2:38 ` Kuninori Morimoto
2015-01-06 13:19 ` Arnd Bergmann
2015-01-07 2:56 ` Kuninori Morimoto
2015-01-07 2:28 ` Kuninori Morimoto
2015-01-07 9:23 ` Arnd Bergmann
2015-01-07 3:01 ` Kuninori Morimoto
2015-01-07 9:15 ` Arnd Bergmann
2015-01-08 1:57 ` Kuninori Morimoto
2015-01-08 7:30 ` Kuninori Morimoto
2015-01-08 13:09 ` Arnd Bergmann [this message]
2015-01-09 9:44 ` Kuninori Morimoto
2015-01-12 9:05 ` Ulf Hansson
2015-01-05 7:02 ` [PATCH 3/9] mmc: tmio: tmio_mmc_host has .write16_hook Kuninori Morimoto
2015-01-05 7:03 ` [PATCH 4/9] mmc: tmio: tmio_mmc_host has .clk_enable Kuninori Morimoto
2015-01-05 7:03 ` [PATCH 5/9] mmc: tmio: tmio_mmc_host has .clk_disable Kuninori Morimoto
2015-01-05 7:03 ` [PATCH 6/9] mmc: tmio: tmio_mmc_host has .multi_io_quirk Kuninori Morimoto
2015-01-05 7:03 ` [PATCH 7/9] mmc: tmio: tmio_mmc_host has .bus_shift Kuninori Morimoto
2015-01-05 7:03 ` [PATCH 8/9] mmc: sh_mobile_sdhi: remove .init/.cleanup Kuninori Morimoto
2015-01-05 9:02 ` Geert Uytterhoeven
2015-01-05 9:15 ` Kuninori Morimoto
2015-01-05 7:04 ` [PATCH 9/9] mmc: sh_mobile_sdhi: remove sh_mobile_sdhi_info Kuninori Morimoto
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=9752854.8NpfY0BrAf@wuerfel \
--to=arnd@arndb.de \
--cc=cjb@laptop.org \
--cc=horms@verge.net.au \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=ulf.hansson@linaro.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