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: Mon, 02 Jul 2012 19:53:04 +0000	[thread overview]
Message-ID: <201207022153.04541.rjw@sisk.pl> (raw)
In-Reply-To: <87hatzlm7x.wl%kuninori.morimoto.gx@renesas.com>

On Monday, July 02, 2012, Kuninori Morimoto wrote:
> 
> Hi Rafael
> 
> > I've already merged your entire seres doing some manula adjustments
> > wherever the changes depended on the new PM domain code.  Please
> > check the 'next' branch of the renesas.git tree and let me know if
> > anything is missing or wrong.
> 
> Thank you for accepting my patches.
> Yes. Its are correctly included in my quick check.
> 
> > > ------- for rafael/soc ----------------------------------
> > > Kuninori Morimoto (1):
> > >       [PATCH 1/1] ARM: shmobile: shareing extra gpio setting functions
> > > 
> > >  arch/arm/mach-shmobile/board-ap4evb.c      |   19 +--------------
> > >  arch/arm/mach-shmobile/board-g4evm.c       |   18 ---------------
> > >  arch/arm/mach-shmobile/board-mackerel.c    |   30 +------------------------
> > >  arch/arm/mach-shmobile/include/mach/gpio.h |   32 ++++++++++++++++++++++++++++
> > >  4 files changed, 36 insertions(+), 63 deletions(-)
> > 
> > No, that should be split into 4 patches, such that patch 1 will change
> > arch/arm/mach-shmobile/include/mach/gpio.h only and the other patches will
> > change the respective board files.  You've done the split already, haven't you?
> (snip)
> > [PATCH 1/16] ARM: shmobile: add common DMAEngine definitions
> > [PATCH 2/16] ARM: shmobile: add common extra gpio functions
> > [PATCH 3/16] ARM: shmobile: r8a7740: add DMAEngine support for FSI
> > [PATCH 4/16] ARM: shmobile: r8a7740: add DMAEngine support for SDHI
> > [PATCH 5/16] ARM: shmobile: r8a7740: add DMAEngine support for USB
> > [PATCH 6/16] ARM: shmobile: sh73a0: add DMAEngine support for MPDMAC
> > [PATCH 7/16] ARM: shmobile: sh73a0: add USB clock support
> > [PATCH 8/16] ARM: shmobile: armadillo800eva: enable FSI-WM8978 sound
> > [PATCH 9/16] ARM: shmobile: armadillo800eva: enable FSI-HDMI sound
> > [PATCH 10/16] ARM: shmobile: armadillo800eva: enable DMAEngine on FSI
> > [PATCH 11/16] ARM: shmobile: armadillo800eva: enable DMAEngine on SDHI
> > [PATCH 12/16] ARM: shmobile: armadillo800eva: enable DMAEngine on USB
> > [PATCH 13/16] ARM: shmobile: kzm9g: enable DMAEngine on FSI
> > [PATCH 14/16] ARM: shmobile: kzm9g: enable DMAEngine on MMCIF
> > [PATCH 15/16] ARM: shmobile: kzm9g: enable USB func
> > [PATCH 16/16] ARM: shmobile: kzm9g: enable MicroSD
> > 
> > next time?  That will be _way_ easier for me to handle and generally quite
> > clean, and you can always add a [0/16] message explaining what's going on.
> 
> Sorry it was my English misunderstanding.
> I will do that.
> 
> I think [PATCH 1/16] and [PATCH 2/16] should be separated into 4 patches for each CPU.
> Is this correct ?
> 
> But I still have question about this.
> What it difference between above style and my original patch set
> (= 10 Jun 2012 / [PATCH 0/27] ARM: shmobile: resend patch set)?
> 
> There are patch name issue now, and 1st/2nd were bugfix patches,
> but...

If I remember correctly, there were patches in there that touch
several boards at a time along with a common header.  And there
were patches that required some adjustments, as far as I can say.

Anyway, the format is suitable for me.

Thanks,
Rafael

      parent reply	other threads:[~2012-07-02 19:53 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
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 [this message]

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=201207022153.04541.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).