From: Greg KH <gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org>
To: Carlos Hernandez <ceh-l0cyMroinI0@public.gmane.org>
Cc: "lcpd_connectivity-uAqBSO/uNfhBDgjK7y7TUQ@public.gmane.org -
Linux Core Product Development - Connectivity"
<lcpd_connectivity-uAqBSO/uNfhBDgjK7y7TUQ@public.gmane.org>,
linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Tony Lindgren <tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>,
linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: usb-related linux-next boot failures
Date: Wed, 28 Jun 2017 06:55:43 +0200 [thread overview]
Message-ID: <20170628045543.GA28759@kroah.com> (raw)
In-Reply-To: <0d1a491c-41c4-a02d-cdf8-e1a95a1fe989-l0cyMroinI0@public.gmane.org>
On Tue, Jun 27, 2017 at 02:28:56PM -0400, Carlos Hernandez wrote:
> Still seeing AM57xx/DRA72/DRA7x usb-related boot failures on linux-next...
Is this a regression? If so, any specific commit that caused it?
thanks,
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-06-28 4:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-27 18:28 usb-related linux-next boot failures Carlos Hernandez
[not found] ` <0d1a491c-41c4-a02d-cdf8-e1a95a1fe989-l0cyMroinI0@public.gmane.org>
2017-06-28 4:55 ` Greg KH [this message]
[not found] ` <20170628045543.GA28759-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2017-06-28 8:31 ` Felipe Balbi
[not found] ` <87r2y45x97.fsf-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2017-06-28 10:30 ` Tony Lindgren
[not found] ` <20170628103014.GC3730-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2017-06-28 10:51 ` Vignesh R
[not found] ` <34a37d06-1929-814b-3476-6eaa5a45cd39-l0cyMroinI0@public.gmane.org>
2017-06-28 10:54 ` Felipe Balbi
[not found] ` <87k23w5qn2.fsf-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2017-06-28 13:38 ` Vignesh R
[not found] ` <71bae311-f85b-4fe1-06c2-d43bfee42b88-l0cyMroinI0@public.gmane.org>
2017-06-29 5:54 ` Felipe Balbi
2017-06-28 17:13 ` Grygorii Strashko
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=20170628045543.GA28759@kroah.com \
--to=gregkh-hqyy1w1ycw8ekmwlsbkhg0b+6bgklq7r@public.gmane.org \
--cc=ceh-l0cyMroinI0@public.gmane.org \
--cc=lcpd_connectivity-uAqBSO/uNfhBDgjK7y7TUQ@public.gmane.org \
--cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.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