From: Felipe Balbi <balbi@ti.com>
To: kishon <kishon@ti.com>
Cc: <balbi@ti.com>, <gregkh@linuxfoundation.org>,
<linux-usb@vger.kernel.org>, <linux-omap@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <tony@atomide.com>,
<notasas@gmail.com>
Subject: Re: [PATCH 0/5] usb: musb/otg: cleanup and fixes
Date: Wed, 20 Mar 2013 17:59:27 +0200 [thread overview]
Message-ID: <20130320155927.GH1567@arwen.pp.htv.fi> (raw)
In-Reply-To: <5149D43C.3060506@ti.com>
[-- Attachment #1: Type: text/plain, Size: 1488 bytes --]
On Wed, Mar 20, 2013 at 08:52:36PM +0530, kishon wrote:
> Felipe,
>
> On Wednesday 20 March 2013 06:42 PM, Felipe Balbi wrote:
> >On Wed, Mar 13, 2013 at 02:17:05PM +0530, Kishon Vijay Abraham I wrote:
> >>This series has some misc cleanup and fixes. The fix solves the cold
> >>plug issue in omap3 which some have reported. Developed these patches on
> >>Linux 3.9-rc2 after applying http://www.spinics.net/lists/linux-usb/msg81563.html
> >>(Grazvydas Ignotas patch series)
> >>
> >>Tested for g_zero enumeration in pandaboard and beagleboard in both
> >>cold plug and hot plug case. Any kind of testing for this series is welcome.
> >>
> >>Kishon Vijay Abraham I (5):
> >> usb: musb: omap: remove the check before calling otg_set_vbus
> >> usb: musb: omap: always glue have the correct vbus/id status
> >> usb: otg: twl4030: use devres API for regulator get and request irq
> >> usb: musb: omap: add usb_phy_init in omap2430_musb_init
> >> usb: otg: twl4030: fix cold plug on OMAP3
> >>
> >> drivers/usb/musb/omap2430.c | 22 ++++++++++------------
> >> drivers/usb/otg/twl4030-usb.c | 35 ++++++++++++-----------------------
> >> 2 files changed, 22 insertions(+), 35 deletions(-)
> >
> >this needs to be rebased against my 'next' branch.
>
> The v2 of this series is already in your testing branch. You still
> want it to be rebased to your 'next' branch?
sorry, no need. I just forgot to mark this one as read. My bad.
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-03-20 15:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-13 8:47 Kishon Vijay Abraham I
2013-03-13 8:47 ` [PATCH 1/5] usb: musb: omap: remove the check before calling otg_set_vbus Kishon Vijay Abraham I
2013-03-13 8:47 ` [PATCH 2/5] usb: musb: omap: always glue have the correct vbus/id status Kishon Vijay Abraham I
2013-03-13 21:59 ` Grazvydas Ignotas
2013-03-14 5:26 ` kishon
2013-03-13 8:47 ` [PATCH 3/5] usb: otg: twl4030: use devres API for regulator get and request irq Kishon Vijay Abraham I
2013-03-13 8:47 ` [PATCH 4/5] usb: musb: omap: add usb_phy_init in omap2430_musb_init Kishon Vijay Abraham I
2013-03-13 8:47 ` [PATCH 5/5] usb: otg: twl4030: fix cold plug on OMAP3 Kishon Vijay Abraham I
2013-03-13 22:00 ` [PATCH 0/5] usb: musb/otg: cleanup and fixes Grazvydas Ignotas
2013-03-20 13:12 ` Felipe Balbi
2013-03-20 15:22 ` kishon
2013-03-20 15:59 ` Felipe Balbi [this message]
2014-06-02 7:31 ` sarfaraz5286
2014-06-04 6:21 ` sarfaraz5286
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=20130320155927.GH1567@arwen.pp.htv.fi \
--to=balbi@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=notasas@gmail.com \
--cc=tony@atomide.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
all inboxes | Powered by JetHome®