From: Greg KH <greg@kroah.com>
To: Felipe Balbi <balbi@ti.com>
Cc: Linux USB Mailing List <linux-usb@vger.kernel.org>,
Linux OMAP Mailing List <linux-omap@vger.kernel.org>
Subject: Re: [GIT PULL] OMAP USB Patches for 2.6.39
Date: Fri, 18 Feb 2011 08:35:14 -0800 [thread overview]
Message-ID: <20110218163514.GA11555@kroah.com> (raw)
In-Reply-To: <20110218163144.GA11460@kroah.com>
On Fri, Feb 18, 2011 at 08:31:44AM -0800, Greg KH wrote:
> On Fri, Feb 18, 2011 at 02:11:45PM +0200, Felipe Balbi wrote:
> > Hi Greg,
> >
> > Here are the patches I have for the next merge window.
> >
> > The outstanding feature is the introduction of pm_runtime
> > support for the OMAP glue layer for MUSB.
> >
> > These patches have been tested on omap4430 with g_zero
> > + testusb overnight and no problems have come from those.
> >
> > These are on top of greg/usb-next, if you want me to rebase
> > on top of another commit, please let me know about it and I'll
> > do it quickly.
> >
> > Thanks, pull request below.
> >
> > The following changes since commit 04b31c776f34d127b422da92899272a0b8cda21d:
> >
> > usb: isp1362-hcd: use bitmap_clear() and bitmap_set() (2011-02-17 11:00:24 -0800)
> >
> > are available in the git repository at:
> > git://gitorious.org/usb/usb.git for-next
>
> $ git pull git://gitorious.org/usb/usb.git for-next
> fatal: The remote end hung up unexpectedly
>
> Something's wrong on gitorious's side and I can't seem to pull this :(
>
> Any ideas?
Nevermind, it took 7 tried, but eventually it worked. Wierd.
pulled and pushed out now, thanks.
greg k-h
next prev parent reply other threads:[~2011-02-18 16:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-18 12:11 [GIT PULL] OMAP USB Patches for 2.6.39 Felipe Balbi
[not found] ` <20110218121145.GB11151-UiBtZHVXSwEVvW8u9ZQWYwjfymiNCTlR@public.gmane.org>
2011-02-18 13:32 ` Sergei Shtylyov
2011-02-18 15:38 ` Felipe Balbi
2011-02-18 16:31 ` Greg KH
2011-02-18 16:35 ` Greg KH [this message]
2011-02-19 14:50 ` 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=20110218163514.GA11555@kroah.com \
--to=greg@kroah.com \
--cc=balbi@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.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