All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 0/9] Reorganize R8A7779/Marzen USB code
Date: Thu, 11 Apr 2013 00:51:56 +0000	[thread overview]
Message-ID: <20130411005155.GA18530@verge.net.au> (raw)
In-Reply-To: <20130410090543.GB25890@verge.net.au>

On Wed, Apr 10, 2013 at 06:05:43PM +0900, Simon Horman wrote:
> On Wed, Apr 10, 2013 at 11:50:33AM +0300, Felipe Balbi wrote:
> > Hi,
> > 
> > On Wed, Apr 10, 2013 at 01:49:23PM +0900, Simon Horman wrote:
> > > On Wed, Apr 10, 2013 at 02:26:08AM +0400, Sergei Shtylyov wrote:
> > > > Hello.
> > > > 
> > > >    Here's the set of 9 patches against the Simon Horman's 'renesas.git' repo,
> > > > 'renesas-next-20130410' 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.
> > > > 
> > > > [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), and it's probably too late to
> > > > merge thru Simon's tree for 3.10 too. So it now have to be postponed to 3.11,
> > > > unfortunately...
> > > 
> > > Felipe, how would you prefer to handle this?
> > > I'm happy for you to take it or to take it myself.
> > 
> > please take it yourself, just keep in mind there will be conflicts, I
> > will go over the patches now and give my Acked-by so you can queue them
> > up.
> 
> Thanks

Sergei, it looks like patches 1-7 are clear.
Do you want me to start queueing them up.
Or would you rather wait for the issue with patch 6 to be resolved?

WARNING: multiple messages have this Message-ID (diff)
From: horms@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/9] Reorganize R8A7779/Marzen USB code
Date: Thu, 11 Apr 2013 09:51:56 +0900	[thread overview]
Message-ID: <20130411005155.GA18530@verge.net.au> (raw)
In-Reply-To: <20130410090543.GB25890@verge.net.au>

On Wed, Apr 10, 2013 at 06:05:43PM +0900, Simon Horman wrote:
> On Wed, Apr 10, 2013 at 11:50:33AM +0300, Felipe Balbi wrote:
> > Hi,
> > 
> > On Wed, Apr 10, 2013 at 01:49:23PM +0900, Simon Horman wrote:
> > > On Wed, Apr 10, 2013 at 02:26:08AM +0400, Sergei Shtylyov wrote:
> > > > Hello.
> > > > 
> > > >    Here's the set of 9 patches against the Simon Horman's 'renesas.git' repo,
> > > > 'renesas-next-20130410' 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.
> > > > 
> > > > [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), and it's probably too late to
> > > > merge thru Simon's tree for 3.10 too. So it now have to be postponed to 3.11,
> > > > unfortunately...
> > > 
> > > Felipe, how would you prefer to handle this?
> > > I'm happy for you to take it or to take it myself.
> > 
> > please take it yourself, just keep in mind there will be conflicts, I
> > will go over the patches now and give my Acked-by so you can queue them
> > up.
> 
> Thanks

Sergei, it looks like patches 1-7 are clear.
Do you want me to start queueing them up.
Or would you rather wait for the issue with patch 6 to be resolved?

  reply	other threads:[~2013-04-11  0:51 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-09 22:26 [PATCH v3 0/9] Reorganize R8A7779/Marzen USB code Sergei Shtylyov
2013-04-09 22:26 ` Sergei Shtylyov
2013-04-10  4:49 ` Simon Horman
2013-04-10  4:49   ` Simon Horman
2013-04-10  8:50   ` Felipe Balbi
2013-04-10  8:50     ` Felipe Balbi
2013-04-10  9:05     ` Simon Horman
2013-04-10  9:05       ` Simon Horman
2013-04-11  0:51       ` Simon Horman [this message]
2013-04-11  0:51         ` Simon Horman
2013-04-11 12:02         ` Sergei Shtylyov
2013-04-11 12:02           ` Sergei Shtylyov
2013-04-11 12:06           ` Felipe Balbi
2013-04-11 12:06             ` Felipe Balbi
2013-04-11 12:20             ` Sergei Shtylyov
2013-04-11 12:20               ` Sergei Shtylyov
2013-04-12  0:34           ` Simon Horman
2013-04-12  0:34             ` Simon Horman
2013-04-12 18:11             ` Sergei Shtylyov
2013-04-12 18:11               ` Sergei Shtylyov

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=20130411005155.GA18530@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 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.