From: Simon Horman <horms@verge.net.au>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v8 0/9] Reorganize R8A7779/Marzen USB code
Date: Tue, 11 Jun 2013 07:56:19 +0000 [thread overview]
Message-ID: <20130611075619.GA5300@verge.net.au> (raw)
In-Reply-To: <20130611074943.GF10440@verge.net.au>
On Tue, Jun 11, 2013 at 04:49:43PM +0900, Simon Horman wrote:
> On Fri, Jun 07, 2013 at 02:45:45PM +0400, Sergei Shtylyov wrote:
> > Hello.
> >
> > On 07-06-2013 12:06, Simon Horman wrote:
> >
> > >> Here's the set of 9 patches against the Simon Horman's 'renesas.git' repo,
> > >>'renesas-next-20130528' 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] phy-rcar-usb: remove EHCI internal buffer setup
> > >>[5/9] ARM: shmobile: r8a7779: remove USB PHY 2nd memory resource
> > >>[6/9] phy-rcar-usb: correct base address
> > >>[7/9] phy-rcar-usb: add platform data
> > >>[8/9] ARM: shmobile: Marzen: pass platform data to USB PHY device
> > >>[9/9] phy-rcar-usb: handle platform data
> >
> > >> The patchset is completely ready to be merged now.
> >
> > >Can I confirm that the plan is for me to merge this code?
> >
> > Yes, that was the plan.
> >
> > >If so, I should be able to do so next week.
>
> Thanks, I have queued this up in the soc2 phy-rcar-usb.
s/soc2 phy-rcar-usb/phy-rcar-usb branch/
> My current plan is to let that branch sit in next for a few
> days and then send a pull-request for it to be included in v3.11.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-sh" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2013-06-11 7:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-01 21:28 [PATCH v8 0/9] Reorganize R8A7779/Marzen USB code Sergei Shtylyov
2013-06-01 21:30 ` [PATCH v8 1/9] ARM: shmobile: Marzen: move USB EHCI, OHCI, and PHY devices to R8A7779 code Sergei Shtylyov
2013-06-01 21:37 ` [PATCH v8 3/9] ARM: shmobile: r8a7779: setup EHCI internal buffer Sergei Shtylyov
2013-06-01 21:48 ` [PATCH v8 5/9] ARM: shmobile: r8a7779: remove USB PHY 2nd memory resource Sergei Shtylyov
2013-06-01 21:55 ` [PATCH v8 8/9] ARM: shmobile: Marzen: pass platform data to USB PHY device Sergei Shtylyov
2013-06-07 8:06 ` [PATCH v8 0/9] Reorganize R8A7779/Marzen USB code Simon Horman
2013-06-07 10:45 ` Sergei Shtylyov
2013-06-11 7:49 ` Simon Horman
2013-06-11 7:56 ` 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=20130611075619.GA5300@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