public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Antoine Ténart" <antoine.tenart@free-electrons.com>
To: Felipe Balbi <balbi@ti.com>
Cc: "Antoine Ténart" <antoine.tenart@free-electrons.com>,
	gregkh@linuxfoundation.org, Peter.Chen@freescale.com,
	kishon@ti.com, stern@rowland.harvard.edu,
	alexandre.belloni@free-electrons.com,
	thomas.petazzoni@free-electrons.com, zmxu@marvell.com,
	jszhang@marvell.com, linux-usb@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] usb: move the OTG state from the USB PHY to the OTG structure
Date: Thu, 10 Jul 2014 15:47:58 +0200	[thread overview]
Message-ID: <20140710134758.GA32462@kwain> (raw)
In-Reply-To: <20140710134023.GJ15340@saruman.home>

Hi Felipe,

On Thu, Jul 10, 2014 at 08:40:23AM -0500, Felipe Balbi wrote:
> On Wed, Jul 09, 2014 at 12:17:13PM +0200, Antoine Ténart wrote:
> > Before using the PHY framework instead of the USB PHY one, we need to
> > move the OTG state into another place, since it won't be available when
> > USB PHY isn't used. This patch moves the OTG state into the OTG
> > structure, and makes all the needed modifications in the drivers
> > using the OTG state.
> > 
> > Signed-off-by: Antoine Ténart <antoine.tenart@free-electrons.com>
> 
> This looks good to me. I'm interested in what will be the best way to
> merge this series :-)

I was asking myself the same question :) If splits or squashes are needed
please ask. At least, I'll split the s/phy/usb_phy/ and the generic PHY
addition in two patches as Alan asked.

Antoine


-- 
Antoine Ténart, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2014-07-10 13:48 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-09 10:17 [PATCH 0/4] usb: add support for the generic PHY framework Antoine Ténart
2014-07-09 10:17 ` [PATCH 1/4] usb: move the OTG state from the USB PHY to the OTG structure Antoine Ténart
2014-07-10 13:40   ` Felipe Balbi
2014-07-10 13:47     ` Antoine Ténart [this message]
2014-07-16 15:02       ` Felipe Balbi
2014-07-15 11:27   ` Peter Chen
2014-07-22 21:33   ` Bin Liu
2014-07-23  7:08     ` Antoine Ténart
2014-07-09 10:17 ` [PATCH 2/4] usb: add support to the PHY framework for OTG Antoine Ténart
2014-07-10 13:41   ` Felipe Balbi
2014-07-09 10:17 ` [PATCH 3/4] usb: add support to the PHY framework for HCD Antoine Ténart
2014-07-09 14:41   ` Alan Stern
2014-07-09 15:08     ` Antoine Ténart
2014-07-14  9:08   ` Vivek Gautam
2014-07-15  9:09     ` Antoine Ténart
2014-07-09 10:17 ` [PATCH 4/4] usb: chipidea: add support to the PHY framework for ChipIdea Antoine Ténart
2014-07-10 13:42   ` Felipe Balbi
2014-07-10 13:51     ` Antoine Ténart
2014-07-10 13:56       ` Felipe Balbi
2014-07-10 14:01         ` Antoine Ténart

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=20140710134758.GA32462@kwain \
    --to=antoine.tenart@free-electrons.com \
    --cc=Peter.Chen@freescale.com \
    --cc=alexandre.belloni@free-electrons.com \
    --cc=balbi@ti.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jszhang@marvell.com \
    --cc=kishon@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    --cc=thomas.petazzoni@free-electrons.com \
    --cc=zmxu@marvell.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