linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vinod Koul <vinod.koul@intel.com>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
	Simon <horms@verge.net.au>, Arnd Bergmann <arnd@arndb.de>,
	Chris Ball <cjb@laptop.org>, Linux-SH <linux-sh@vger.kernel.org>,
	linux-mmc <linux-mmc@vger.kernel.org>
Subject: Re: [PATCH 0/2] tmio: mmc: replace sh_mobile_sdhi_info to tmio_mmc_data
Date: Thu, 05 Mar 2015 08:48:30 +0000	[thread overview]
Message-ID: <20150305083630.GZ2613@intel.com> (raw)
In-Reply-To: <CAPDyKFqJ7bbfaQgYnhHerFbre9mPzj7i6QGPQZo54ukuHaD32g@mail.gmail.com>

On Thu, Mar 05, 2015 at 09:33:10AM +0100, Ulf Hansson wrote:
> On 5 March 2015 at 08:11, Kuninori Morimoto
> <kuninori.morimoto.gx@renesas.com> wrote:
> >
> > Hi Ulf
> >
> >> > Hi Ulf, Vinod, Simon
> >> >
> >> > DMAEngine cleanup patches are accepted in v4.0-rc1
> >> >
> >> > As I mentioned in
> >> > http://thread.gmane.org/gmane.linux.ports.sh.devel/42669
> >> > these are last of sh_mobile_sdhi DMA patches.
> >> >
> >> > These patches uses tmio_mmc_data on platform,
> >> > and remove sh_mobile_sdhi
> >> >
> >> > These are based on
> >> >  - linus's v4.0-rc1
> >> >  - Vinod's dma/next (git://git.infradead.org/users/vkoul/slave-dma.git :: next)
> >> >
> >> > Vinod
> >> >
> >> > please let us know if it has stable tag or branch
No my next is not stable, I will rebase that.
I think you want to pick topic/sh, that is an immutable branch
Can you check that has all the patches you need for this?

> >> Please use topic/sh. I will not rebase that, my next would be rebased
> >> frequently...
> >
> > Please let me know if you want me to re-send these patches
> 
> I have no issues with the patches as such. Though, I wonder about the
> dependency here.
> 
> Does these patches depend on an immutable branch hosted from Vinod's tree?
>
> 
> Do you want me to take the patches through my mmc tree or just request
> an ack so Vinod can carry this?
Either ways is okay with me..

-- 
~Vinod


  reply	other threads:[~2015-03-05  8:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-24  2:07 [PATCH 0/2] tmio: mmc: replace sh_mobile_sdhi_info to tmio_mmc_data Kuninori Morimoto
2015-02-24  2:06 ` [PATCH 1/2] mmc: tmio: mmc: tmio: tmio_mmc_data has .chan_priv_?x Kuninori Morimoto
2015-03-05 10:02   ` Ulf Hansson
2015-03-05 10:56     ` Lee Jones
2015-02-24  2:07 ` [PATCH 2/2] mmc: sh_mobile_sdhi: remove sh_mobile_sdhi_info Kuninori Morimoto
2015-03-05  9:59   ` Ulf Hansson
2015-02-24  8:17 ` [PATCH 0/2] tmio: mmc: replace sh_mobile_sdhi_info to tmio_mmc_data Arnd Bergmann
2015-02-24 16:35 ` Vinod Koul
2015-03-05  7:11   ` Kuninori Morimoto
2015-03-05  8:33     ` Ulf Hansson
2015-03-05  8:48       ` Vinod Koul [this message]
2015-03-05  8:59         ` Kuninori Morimoto
2015-03-05 10:03         ` Ulf Hansson
2015-03-05 16:37 ` Vinod Koul

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=20150305083630.GZ2613@intel.com \
    --to=vinod.koul@intel.com \
    --cc=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;
as well as URLs for NNTP newsgroup(s).