From: peter.chen@freescale.com (Peter Chen)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 2/3] usb: udc: delete the vbus indicator at individual driver
Date: Wed, 13 Mar 2013 11:10:43 +0800 [thread overview]
Message-ID: <20130313031042.GA18168@nchen-desktop> (raw)
In-Reply-To: <20130312094649.GC15163@arwen.pp.htv.fi>
On Tue, Mar 12, 2013 at 11:46:49AM +0200, Felipe Balbi wrote:
> On Tue, Mar 12, 2013 at 05:03:18PM +0800, Peter Chen wrote:
> > Let the common struct usb_gadget own it.
> >
> > CC: Alexander Shishkin <alexander.shishkin@linux.intel.com>
> > CC: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
> > CC: Li Yang <leoli@freescale.com>
> > CC: Roland Stigge <stigge@antcom.de>
> > CC: Yu Xu <yuxu@marvell.com>
> > CC: Chao Xie <chao.xie@marvell.com>
> > CC: Eric Miao <eric.y.miao@gmail.com>
> > CC: Ben Dooks <ben-linux@fluff.org>
> > Signed-off-by: Peter Chen <peter.chen@freescale.com>
>
> you need to split this patch, should be something like below:
>
> for_each_driver() {
> initialize gadget->vbus_active (don't remove private method)
> }
>
> add vbus_active support to udc-core
>
> for_each_driver() {
> remove driver's private vbus_active method
> }
>
> you need one patch per driver so it's easy to review and ack.
Eg, If I changed 10 udc drivers, I need
1(add vbus_active to struct usb_gadget) + 10 + 1 + 10 = 22 patches?
>
> --
> balbi
--
Best Regards,
Peter Chen
next prev parent reply other threads:[~2013-03-13 3:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-12 9:03 [RFC PATCH 1/3] usb: udc-core: introduce vbus_active for struct usb_gadget Peter Chen
2013-03-12 9:03 ` [RFC PATCH 2/3] usb: udc: delete the vbus indicator at individual driver Peter Chen
2013-03-12 9:46 ` Felipe Balbi
2013-03-13 3:10 ` Peter Chen [this message]
2013-03-13 7:44 ` Felipe Balbi
2013-03-13 7:49 ` Peter Chen
2013-03-13 8:43 ` Felipe Balbi
2013-03-12 9:54 ` Peter Chen
2013-03-12 9:03 ` [RFC PATCH 3/3] usb: udc-core: add judgement logic for usb_gadget_connect Peter Chen
2013-03-12 9:47 ` Felipe Balbi
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=20130313031042.GA18168@nchen-desktop \
--to=peter.chen@freescale.com \
--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;
as well as URLs for NNTP newsgroup(s).