All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roger Quadros <rogerq@ti.com>
To: Venu Byravarasu <vbyravarasu@nvidia.com>
Cc: "balbi@ti.com" <balbi@ti.com>,
	"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] usb: phy: moving all PHY API definitions to usb/phy directory
Date: Wed, 23 Jan 2013 11:32:24 +0200	[thread overview]
Message-ID: <50FFAE28.3070003@ti.com> (raw)
In-Reply-To: <D958900912E20642BCBC71664EFECE3E6E1B13B787@BGMAIL02.nvidia.com>

On 01/23/2013 01:56 AM, Venu Byravarasu wrote:
>> -----Original Message-----
>> From: Roger Quadros [mailto:rogerq@ti.com]
>> Sent: Tuesday, January 22, 2013 7:51 PM
>> To: Venu Byravarasu
>> Cc: balbi@ti.com; gregkh@linuxfoundation.org; linux-usb@vger.kernel.org;
>> linux-kernel@vger.kernel.org
>> Subject: Re: [PATCH v2] usb: phy: moving all PHY API definitions to usb/phy
>> directory
>>
>> On 01/22/2013 01:01 PM, Venu Byravarasu wrote:
>>> As drivers/usb/otg/otg.c contains most of the PHY related APIs
>>> which are not OTG specific, moving them to more logical place
>>> under driver/usb/phy.
>>>
>>> Signed-off-by: Venu Byravarasu <vbyravarasu@nvidia.com>
>>> ---
>>> delta from v1:
>>> Missed adding newly created file usb_phy.c with previous patch.
>>> hence sending v2, after adding that.
>>>
>>>  drivers/usb/otg/otg.c                    |  184 ------------------------------
>>>  drivers/usb/phy/Makefile                 |    1 +
>>>  drivers/usb/{otg/otg.c => phy/usb_phy.c} |   45 +-------
>>>  3 files changed, 6 insertions(+), 224 deletions(-)
>>>  copy drivers/usb/{otg/otg.c => phy/usb_phy.c} (82%)
>>
>> what about updating
>> drivers/usb/otg/Makefile and Kconfig?
>>
>> i.e. remove CONFIG_USB_OTG_UTILS and otg.o there?
> 
> Thanks for your comments.
> Those files may still be needed, as we're not removing otg.c,
> due to remaining only otg function i.e. otg_state_string().
> 

Oh yes, in that case it is fine.

--
cheers,
-roger.

      reply	other threads:[~2013-01-23  9:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-22 11:01 [PATCH v2] usb: phy: moving all PHY API definitions to usb/phy directory Venu Byravarasu
2013-01-22 11:08 ` Felipe Balbi
2013-01-22 14:21 ` Roger Quadros
2013-01-22 23:56   ` Venu Byravarasu
2013-01-23  9:32     ` Roger Quadros [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=50FFAE28.3070003@ti.com \
    --to=rogerq@ti.com \
    --cc=balbi@ti.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@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 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.