From: Greg KH <gregkh@linuxfoundation.org>
To: Felipe Balbi <balbi@ti.com>
Cc: John Youn <John.Youn@synopsys.com>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"david.fisher1@synopsys.com" <david.fisher1@synopsys.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH 1/6] usb: dwc3: Support Synopsys USB 3.1 IP
Date: Sat, 3 Oct 2015 00:02:54 +0200 [thread overview]
Message-ID: <20151002220254.GA4869@kroah.com> (raw)
In-Reply-To: <20151002192101.GF5552@saruman.tx.rr.com>
On Fri, Oct 02, 2015 at 02:21:01PM -0500, Felipe Balbi wrote:
> > We're trying to avoid the situation where where we have to ship
> > patches or maintain a separate kernel tree.
> >
> > Do you have any objections to these going into stable?
>
> I'm not the one you need to convince. That would be Greg :-)
What's the git commit id of the patch in Linus's tree?
thanks,
greg k-h
next prev parent reply other threads:[~2015-10-02 22:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-02 1:14 [PATCH 0/6] usb: dwc3: Various updates for Synopsys platforms John Youn
2015-08-07 18:04 ` [PATCH 2/6] usb: dwc3: pci: Add the Synopsys HAPS AXI Product ID John Youn
2015-08-07 18:47 ` [PATCH 3/6] usb: dwc3: pci: Add the PCI Product ID for Synopsys USB 3.1 John Youn
2015-09-05 2:15 ` [PATCH 1/6] usb: dwc3: Support Synopsys USB 3.1 IP John Youn
2015-10-02 2:03 ` Felipe Balbi
2015-10-02 3:09 ` John Youn
2015-10-02 14:05 ` Felipe Balbi
2015-10-02 19:16 ` John Youn
2015-10-02 19:21 ` Felipe Balbi
2015-10-02 22:02 ` Greg KH [this message]
2015-10-03 0:33 ` Felipe Balbi
2015-10-03 1:14 ` John Youn
2015-10-03 5:54 ` Greg KH
2015-10-02 19:47 ` John Youn
2015-10-02 19:55 ` Felipe Balbi
2015-09-26 6:47 ` [PATCH 6/6] usb: dwc3: pci: trivial: Formatting John Youn
2015-09-26 7:11 ` [PATCH 4/6] usb: dwc3: pci: Add platform data for Synopsys HAPS John Youn
2015-09-26 7:31 ` [PATCH 5/6] usb: dwc3: Add dis_enblslpm_quirk John Youn
2015-10-02 2:06 ` 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=20151002220254.GA4869@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=John.Youn@synopsys.com \
--cc=balbi@ti.com \
--cc=david.fisher1@synopsys.com \
--cc=linux-usb@vger.kernel.org \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).