All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: balbi@ti.com
Cc: Venu Byravarasu <vbyravarasu@nvidia.com>,
	ccross@android.com, olof@lixom.net, linux@arm.linux.org.uk,
	stern@rowland.harvard.edu, gregkh@linuxfoundation.org,
	linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH v2] usb: move phy driver from mach-tegra to drivers/usb
Date: Tue, 04 Sep 2012 15:48:31 -0600	[thread overview]
Message-ID: <5046772F.6060908@wwwdotorg.org> (raw)
In-Reply-To: <1346395526-18219-1-git-send-email-vbyravarasu@nvidia.com>

On 08/31/2012 12:45 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>

Tested-by: Stephen Warren <swarren@nvidia.com>

Felipe, Would it be possible to apply this patch to a topic branch, so
that I can merge it into the Tegra tree? The reason is that I'd like to
remove Tegra's devices.[ch] in kernel 3.7, but to do that, I need to
move a tiny chunk of code out of that file somewhere else, and doing
that relies on adding a #include to usb_phy.h/tegra_usb_phy.h, which is
renamed in this patch.

Alternatively, if you don't think it'll cause any merge conflicts with
the USB PHY tree, I can just take this patch through the Tegra tree if
you want. Venu, do you plan any other patches within the next couple
weeks or so (i.e. before 3.6-rc6) that will depend on this patch? If so,
taking it only through the Tegra tree might not work so well.

Thanks.

WARNING: multiple messages have this Message-ID (diff)
From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] usb: move phy driver from mach-tegra to drivers/usb
Date: Tue, 04 Sep 2012 15:48:31 -0600	[thread overview]
Message-ID: <5046772F.6060908@wwwdotorg.org> (raw)
In-Reply-To: <1346395526-18219-1-git-send-email-vbyravarasu@nvidia.com>

On 08/31/2012 12:45 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>

Tested-by: Stephen Warren <swarren@nvidia.com>

Felipe, Would it be possible to apply this patch to a topic branch, so
that I can merge it into the Tegra tree? The reason is that I'd like to
remove Tegra's devices.[ch] in kernel 3.7, but to do that, I need to
move a tiny chunk of code out of that file somewhere else, and doing
that relies on adding a #include to usb_phy.h/tegra_usb_phy.h, which is
renamed in this patch.

Alternatively, if you don't think it'll cause any merge conflicts with
the USB PHY tree, I can just take this patch through the Tegra tree if
you want. Venu, do you plan any other patches within the next couple
weeks or so (i.e. before 3.6-rc6) that will depend on this patch? If so,
taking it only through the Tegra tree might not work so well.

Thanks.

  reply	other threads:[~2012-09-04 21:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-31  6:45 [PATCH v2] usb: move phy driver from mach-tegra to drivers/usb Venu Byravarasu
2012-08-31  6:45 ` Venu Byravarasu
2012-08-31  6:45 ` Venu Byravarasu
2012-09-04 21:48 ` Stephen Warren [this message]
2012-09-04 21:48   ` Stephen Warren
     [not found]   ` <5046772F.6060908-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-09-05 12:54     ` Venu Byravarasu
2012-09-05 12:54       ` Venu Byravarasu
2012-09-05 12:54       ` Venu Byravarasu
     [not found]       ` <D958900912E20642BCBC71664EFECE3E6DDE77533D-QZ+emBqkIFBDw2glCA4ptUEOCMrvLtNR@public.gmane.org>
2012-09-05 12:52         ` Felipe Balbi
2012-09-05 12:52           ` Felipe Balbi
2012-09-05 12:52           ` Felipe Balbi
2012-09-05 13:35           ` Venu Byravarasu
2012-09-05 13:35             ` Venu Byravarasu

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=5046772F.6060908@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --cc=balbi@ti.com \
    --cc=ccross@android.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=olof@lixom.net \
    --cc=stern@rowland.harvard.edu \
    --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 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.