From: Stephen Warren <swarren@wwwdotorg.org>
To: balbi@ti.com
Cc: Venu Byravarasu <vbyravarasu@nvidia.com>,
linux-kernel@vger.kernel.org,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Subject: Re: [PATCH] usb: move phy driver from mach-tegra to drivers/usb
Date: Wed, 12 Sep 2012 09:29:56 -0600 [thread overview]
Message-ID: <5050AA74.6050408@wwwdotorg.org> (raw)
In-Reply-To: <20120912134919.GR5732@arwen.pp.htv.fi>
On 09/12/2012 07:49 AM, Felipe Balbi wrote:
> On Tue, Sep 11, 2012 at 10:34:38AM -0600, Stephen Warren wrote:
>> On 09/05/2012 07:20 AM, Venu Byravarasu wrote:
>>> As part of this patch: 1. Moved existing tegra phy driver to
>>> drivers/USB directory. 2. Added standard USB phy driver APIs to
>>> tegra phy driver.
>>>
>>> Signed-off-by: Venu Byravarasu <vbyravarasu@nvidia.com>
>>
>> Felipe,
>>
>> I see this patch hasn't been applied yet. Can I ask that it be
>> deferred to 3.8 rather than being applied for 3.7. The reason is
>> that in 3.7, I want to add a new include of the header that this
>> patch moves, and without merging the Tegra and USB PHY trees
>> together, the two patches together would cause a build break.
>> Now, it's a little late to merge the branches, since I need to
>> send my pull requests in about 3 days, so they hit arm-soc by
>> 3.6-rc6.
>
> According to git I've applied this on September 5th:
>
> http://git.kernel.org/?p=linux/kernel/git/balbi/usb.git;a=commit;h=1ba8216f0bc02af6ba70d1108d60eb1b064395e4
Sorry,
>
I had not noticed that; that branch isn't in linux-next, and I
didn't see any email notification that the patch was applied.
As discussed off-list, I'll resolve this by rebasing the relevant
Tegra branch on top of your xceiv branch's pull request tag. Sorry for
the confusion.
prev parent reply other threads:[~2012-09-12 15:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-05 13:20 [PATCH] usb: move phy driver from mach-tegra to drivers/usb Venu Byravarasu
2012-09-11 16:34 ` Stephen Warren
2012-09-12 13:49 ` Felipe Balbi
2012-09-12 15:29 ` Stephen Warren [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=5050AA74.6050408@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=balbi@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=vbyravarasu@nvidia.com \
/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