SUPERH platform development
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 0/9] Reorganize R8A7779/Marzen USB code
Date: Tue, 09 Apr 2013 08:32:43 +0000	[thread overview]
Message-ID: <20130409083243.GF18478@verge.net.au> (raw)
In-Reply-To: <201304090110.50154.sergei.shtylyov@cogentembedded.com>

On Tue, Apr 09, 2013 at 01:10:49AM +0400, Sergei Shtylyov wrote:
> Hello.
> 
>    Here's the set of 9 patches against the Simon Horman's 'renesas.git' repo,
> 'renesas-next-20130405v2' tag.  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. The patches have been tested on the Marzen board.
> 
> [1/9] ARM: shmobile: Marzen: move USB EHCI, OHCI, and PHY devices to R8A7779 code
> [2/9] ehci-platform: add pre_setup() method to platform data
> [3/9] ARM: shmobile: R8A7779: setup EHCI internal buffer
> [4/9] rcar-phy: remove EHCI internal buffer setup
> [5/9] ARM: shmobile: R8A7779: remove USB PHY 2nd memory resource
> [6/9] rcar-phy: correct base address
> [7/9] rcar-phy: add platform data
> [8/9] ARM: shmobile: Marzen: pass platform data to USB PHY device
> [9/9] 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 which
> would have been most convenient probably, so maybe the patchset can be merged
> thru Simon's tree with Felipe's and Alan Stern's ACKs. Or perhaps it now should
> be postponed for 3.11...

I feel that it is also too late for v3.10 for my tree.

I am happy to take them through my tree with appropriate acks.
Or, follow acks from Morimoto-san to allow the shmobile portions
to go through a different tree.


      parent reply	other threads:[~2013-04-09  8:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-08 21:10 [PATCH v2 0/9] Reorganize R8A7779/Marzen USB code Sergei Shtylyov
2013-04-09  5:58 ` Kuninori Morimoto
2013-04-09 12:44   ` Sergei Shtylyov
2013-04-10  1:31     ` Kuninori Morimoto
2013-04-12 23:07       ` Sergei Shtylyov
2013-04-12 23:11         ` Sergei Shtylyov
2013-04-17  1:14           ` Kuninori Morimoto
2013-04-19  0:27             ` Kuninori Morimoto
2013-04-19 17:54               ` Sergei Shtylyov
2013-04-09  8:32 ` Simon Horman [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=20130409083243.GF18478@verge.net.au \
    --to=horms@verge.net.au \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox