All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 11/12 v2] ARM: shmobile: multiplatform: add Audo DMAC peri peri support on defconfig
Date: Thu, 11 Dec 2014 03:23:15 +0000	[thread overview]
Message-ID: <20141211032312.GG513@verge.net.au> (raw)
In-Reply-To: <87h9yl2ie3.wl%kuninori.morimoto.gx@gmail.com>

On Wed, Dec 10, 2014 at 03:51:59AM +0000, Kuninori Morimoto wrote:
> 
> Hi Simon
> 
> > > Thank you for your help
> > > It depends on RCAR-DMAC enable/disable and driver (which want to use DMAEngine).
> > > But, unfortunately, reverting it from v3.19 is very safety. 
> > 
> > Thanks, I think I understand.
> > 
> > I plan to queue-up the following:
> > 
> > From: Simon Horman <horms+renesas@verge.net.au>
> > 
> > [PATCH] Revert "ARM: shmobile: multiplatform: add Audo DMAC peri peri support on defconfig"
> > 
> > This reverts commit 2315f9fce4da7df9362e4baeb5250d14ea48bf63.
> > 
> > Unfortunately enabling RCAR_AUDMAC_PP support this patch breaks dmaengine
> > support on R-Car Gen2 boards. This should be resolved by driver updates
> > in v3.20. But v3.19 was too early for this defconfig change.
> > 
> > Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
> > ---
> 
> Thank you.
> I will re-send this patch if all are OK

Thanks, please do.

I have sent a pull-request for the reversion above.

  parent reply	other threads:[~2014-12-11  3:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-31  0:27 [PATCH 11/12 v2] ARM: shmobile: multiplatform: add Audo DMAC peri peri support on defconfig Kuninori Morimoto
2014-12-08  4:37 ` Kuninori Morimoto
2014-12-09  0:20 ` Simon Horman
2014-12-10  0:58 ` Kuninori Morimoto
2014-12-10  2:41 ` Simon Horman
2014-12-10  3:51 ` Kuninori Morimoto
2014-12-11  3:23 ` Simon Horman [this message]
2014-12-11  3:40 ` 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=20141211032312.GG513@verge.net.au \
    --to=horms@verge.net.au \
    --cc=linux-sh@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 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.