All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/8] Reorganize R8A7779/Marzen USB code
Date: Fri, 05 Apr 2013 16:40:13 +0000	[thread overview]
Message-ID: <515EFE6D.4020006@cogentembedded.com> (raw)
In-Reply-To: <87vc81ka6k.wl%kuninori.morimoto.gx@renesas.com>

Hello.

On 05-04-2013 6:01, Kuninori Morimoto wrote:

>>     Here's the set of 4 patches against the Simon Horman's 'renesas.git' repo,
>> 'renesas-next-20130404v2' tag and the 2 Ether patches I've reposted yesterday.
>> It was created to fix the shortcomings in the R8A7779/Marzen USB platform code
>> and R8A7779 USB common PHY driver, and so spans both arch/arm/mach-shmobile/
>> and drivers/usb/ subtrees (some patches have to touch both subtrees).
>> The patches were conceived with the complete bisectability goal in mind.

>> [1/8] ARM: shmobile:Marzen: move USB EHCI, OHCI, and PHY devices to R8A7779 code
>> [2/8] ehci-platform: add init() method to platform data
>> [3/8] ARM: shmobile: R8A7779: setup EHCI internal buffer
>> [4/8] rcar-phy: remove EHCI internal buffer setup
>> [5/8] rcar-phy: correct base address
>> [6/8] rcar-phy: add platform data
>> [7/8] ARM: shmobile: Marzen: pass platform data to USB PHY device
>> [8/8] rcar-phy: handle platform data

>>     I'm not sure thru which tree this patchset should be merged, however it turns
>> out that it's too late now to push it thru Felipe Balbi's USB tree for 3.10, so
>> maybe the patchset can be merged thru Simon's tree with Felipe's and Alan
>> Stern's ACKs.

> I guess you already got request about patch style from Simon.

    It's not about style. I tried to keep the series copmpletely bisectable, 
and granting almost all requests about splitting the patches would have broken 
the bisection.

> When you send v2 patch, could you please add "this patch is tested on xxxx bard"
> on each patch's comment area ?

    I'm not sure it's worth doing v2, although in one place I can indeed 
readily split the patch. All patches were tested on the Marzen board, I forgot 
to mention that in the cover letter.

> Then,
> for all patches

> Acked-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>

    Thanks.

WBR, Sergei


WARNING: multiple messages have this Message-ID (diff)
From: sergei.shtylyov@cogentembedded.com (Sergei Shtylyov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/8] Reorganize R8A7779/Marzen USB code
Date: Fri, 05 Apr 2013 20:40:13 +0400	[thread overview]
Message-ID: <515EFE6D.4020006@cogentembedded.com> (raw)
In-Reply-To: <87vc81ka6k.wl%kuninori.morimoto.gx@renesas.com>

Hello.

On 05-04-2013 6:01, Kuninori Morimoto wrote:

>>     Here's the set of 4 patches against the Simon Horman's 'renesas.git' repo,
>> 'renesas-next-20130404v2' tag and the 2 Ether patches I've reposted yesterday.
>> It was created to fix the shortcomings in the R8A7779/Marzen USB platform code
>> and R8A7779 USB common PHY driver, and so spans both arch/arm/mach-shmobile/
>> and drivers/usb/ subtrees (some patches have to touch both subtrees).
>> The patches were conceived with the complete bisectability goal in mind.

>> [1/8] ARM: shmobile:Marzen: move USB EHCI, OHCI, and PHY devices to R8A7779 code
>> [2/8] ehci-platform: add init() method to platform data
>> [3/8] ARM: shmobile: R8A7779: setup EHCI internal buffer
>> [4/8] rcar-phy: remove EHCI internal buffer setup
>> [5/8] rcar-phy: correct base address
>> [6/8] rcar-phy: add platform data
>> [7/8] ARM: shmobile: Marzen: pass platform data to USB PHY device
>> [8/8] rcar-phy: handle platform data

>>     I'm not sure thru which tree this patchset should be merged, however it turns
>> out that it's too late now to push it thru Felipe Balbi's USB tree for 3.10, so
>> maybe the patchset can be merged thru Simon's tree with Felipe's and Alan
>> Stern's ACKs.

> I guess you already got request about patch style from Simon.

    It's not about style. I tried to keep the series copmpletely bisectable, 
and granting almost all requests about splitting the patches would have broken 
the bisection.

> When you send v2 patch, could you please add "this patch is tested on xxxx bard"
> on each patch's comment area ?

    I'm not sure it's worth doing v2, although in one place I can indeed 
readily split the patch. All patches were tested on the Marzen board, I forgot 
to mention that in the cover letter.

> Then,
> for all patches

> Acked-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>

    Thanks.

WBR, Sergei

  reply	other threads:[~2013-04-05 16:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-04 22:51 [PATCH 0/8] Reorganize R8A7779/Marzen USB code Sergei Shtylyov
2013-04-04 22:51 ` Sergei Shtylyov
2013-04-05  2:01 ` Kuninori Morimoto
2013-04-05  2:01   ` Kuninori Morimoto
2013-04-05 16:40   ` Sergei Shtylyov [this message]
2013-04-05 16:40     ` Sergei Shtylyov
2013-04-05 22:35     ` Sergei Shtylyov
2013-04-05 22:35       ` Sergei Shtylyov
2013-04-08  2:33       ` Simon Horman
2013-04-08  2:33         ` Simon Horman
2013-04-08 12:35         ` Sergei Shtylyov
2013-04-08 12:35           ` Sergei Shtylyov
2013-04-09 12:00   ` Sergei Shtylyov
2013-04-09 12:00     ` Sergei Shtylyov
2013-04-09 15:11     ` Simon Horman
2013-04-09 15:11       ` Simon Horman

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=515EFE6D.4020006@cogentembedded.com \
    --to=sergei.shtylyov@cogentembedded.com \
    --cc=linux-arm-kernel@lists.infradead.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.