From: gregkh@linuxfoundation.org (gregkh at linuxfoundation.org)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM part of USB patches
Date: Tue, 5 Feb 2013 09:27:24 -0800 [thread overview]
Message-ID: <20130205172724.GA1601@kroah.com> (raw)
In-Reply-To: <51112495.4060908@ti.com>
On Tue, Feb 05, 2013 at 08:56:13PM +0530, kishon wrote:
> Hi Tony, Greg,
>
> On Tuesday 05 February 2013 08:54 PM, kishon wrote:
> >Hi Tony,
> >
> >As discussed, I'm sending a pull request for the arch/arm part of my USB
> >patches. These patches are necessary to get MUSB functional in both dt
> >and non-dt boot. Also added dt data for dwc3 present in OMAP. This patch
> >series *depends* on some of the patches which are merged in usb-next.
>
> This patch series should go in only after USB. Or else it will break
> compilation.
Then it probably should go through the USB tree, right? We don't want
to break bisectability.
thanks,
greg k-h
next prev parent reply other threads:[~2013-02-05 17:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-05 15:24 [GIT PULL] ARM part of USB patches kishon
2013-02-05 15:26 ` kishon
2013-02-05 17:27 ` gregkh at linuxfoundation.org [this message]
2013-02-05 18:19 ` Tony Lindgren
2013-02-05 18:37 ` gregkh at linuxfoundation.org
2013-02-06 5:16 ` Hiremath, Vaibhav
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=20130205172724.GA1601@kroah.com \
--to=gregkh@linuxfoundation.org \
--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).