linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH][rework] ARM: shmobile: patch set rework
Date: Thu, 28 Jun 2012 20:56:31 +0000	[thread overview]
Message-ID: <201206282256.31743.rjw@sisk.pl> (raw)
In-Reply-To: <87hatzlm7x.wl%kuninori.morimoto.gx@renesas.com>

On Monday, June 25, 2012, Magnus Damm wrote:
> Hi Morimoto-san,
> 
> On Mon, Jun 25, 2012 at 7:28 PM, Kuninori Morimoto
> <kuninori.morimoto.gx@renesas.com> wrote:
> >
> > Hi Rafael, Magnus
> > Cc Simon
> >
> > These are rework patch set which are not included on latest rafael's tree.
> > (and additional patch)
> > I separated each patches to become independent as much as possible.
> 
> Thanks for splitting out your patches!
> 
> > My previous patch set tried to sharing "gpio" and "DMAEngine" definitions on top.
> > This patch set still try to sharing it, but it was on last patches.
> 
> Good plan. I like when you prioritize adding hardware support over
> moving around code. =)
> 
> > gpio/DMAEngine sharing patch were separated as "add common xxx",
> > and "use common xxx".
> > I hope it is good fit for rafael's branch control
> 
> Looks fine to me, but I will let Rafael decide about that.
> 
> > 1st "PM domain" patch is new one.
> > It adds very basic PM domain support for Armadillo
> >
> > Kuninori Morimoto (1):
> >      ARM: shmobile: r8a7740: basic PM domain support
> 
> I believe this one needs more work. So I prefer holding off on this
> for a while, alternatively including it in some topic branch for
> incremental fixing and possible rebase,
> 
> > Kuninori Morimoto (2):
> >      ARM: shmobile: armadillo800eva: enable FSI-WM8978 sound
> >      ARM: shmobile: armadillo800eva: enable FSI-HDMI sound
> >
> > Kuninori Morimoto (3):
> >      ARM: shmobile: sh73a0: add USB clock support
> >      ARM: shmobile: kzm9g: enable USB func
> >      ARM: shmobile: kzm9g: enable MicroSD
> >
> > Kuninori Morimoto (6):
> >      ARM: shmobile: r8a7740: add DMAEngine support for FSI
> >      ARM: shmobile: r8a7740: add DMAEngine support for SDHI
> >      ARM: shmobile: r8a7740: add DMAEngine support for USB
> >      ARM: shmobile: armadillo800eva: enable DMAEngine on FSI
> >      ARM: shmobile: armadillo800eva: enable DMAEngine on SDHI
> >      ARM: shmobile: armadillo800eva: enable DMAEngine on USB
> >
> > Kuninori Morimoto (3):
> >      ARM: shmobile: sh73a0: add DMAEngine support for MPDMAC
> >      ARM: shmobile: kzm9g: enable DMAEngine on FSI
> >      ARM: shmobile: kzm9g: enable DMAEngine on MMCIF
> >
> > Kuninori Morimoto (5):
> >      ARM: shmobile: add common extra gpio functions
> >      ARM: shmobile: use common extra gpio functions on ap4evb
> >      ARM: shmobile: use common extra gpio functions on g4evm
> >      ARM: shmobile: use common extra gpio functions on mackrel
> >      ARM: shmobile: use common extra gpio functions on armadillo800eva
> >
> > Kuninori Morimoto (4):
> >      ARM: shmobile: add common DMAEngine definitions
> >      ARM: shmobile: use common DMAEngine definitions on r8a7740
> >      ARM: shmobile: use common DMAEngine definitions on sh7372
> >      ARM: shmobile: use common DMAEngine definitions on sh73a0
> 
> These all look fine to me. Thanks for reposting your patches.
> 
> Rafael, please feel free to include my acked-by and pick up unless you
> or someone else thinks differently.
> 
> Morimoto-san, in general I'm happy with you resending your patches
> like this time,

Sorry to say that, but it totally doesn't work for me.

I'd prefer it to be a single patch series organized so that:
(1) Patches that multiple SoCs depend on go first
    (e.g. "ARM: shmobile: add common extra gpio functions" above).
(2) Patches that only one SoC depends on, but that touch files common to
    multiple boards go next
    (e.g. "ARM: shmobile: use common DMAEngine definitions on r8a7740" above).
(3) Patches that touch only one individual board go last
    (e.g. "ARM: shmobile: use common extra gpio functions on mackrel" above).

Pretty much any other ordering adds work for me and causes a lot of pain if
things don't apply cleanly to the branches I'm using (which is the case this
time).

Thanks,
Rafael



  parent reply	other threads:[~2012-06-28 20:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-25 10:28 [PATCH][rework] ARM: shmobile: patch set rework Kuninori Morimoto
2012-06-25 16:13 ` Magnus Damm
2012-06-28 20:56 ` Rafael J. Wysocki [this message]
2012-06-29  2:18 ` Kuninori Morimoto
2012-06-30 14:09 ` Rafael J. Wysocki
2012-07-02  0:47 ` Kuninori Morimoto
2012-07-02 19:53 ` Rafael J. Wysocki

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=201206282256.31743.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --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 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).