From: "Heiko Stübner" <heiko@sntech.de>
To: Tomeu Vizoso <tomeu.vizoso@collabora.com>
Cc: Minas Harutyunyan <Minas.Harutyunyan@synopsys.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Felipe Balbi <felipe.balbi@linux.intel.com>,
Amelie Delaunay <amelie.delaunay@st.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: Re: [PATCH v4] usb: dwc2: dwc2_vbus_supply_init: fix error check
Date: Tue, 24 Apr 2018 10:58:34 +0200 [thread overview]
Message-ID: <3454244.YafNKb8Syk@diego> (raw)
In-Reply-To: <CAAObsKC3BiojwOhHoDe1-NJ-p135GZmpLGpTBRKP3-9ryuY2uA@mail.gmail.com>
Hi Tomeu,
Am Montag, 23. April 2018, 15:24:04 CEST schrieb Tomeu Vizoso:
> Hi,
>
> could this patch be picked up, please? Or if for some reason it cannot
> be, could the commit that introduced the regression be reverted?
>
> It's causing some tests in KernelCI to fail:
>
> https://storage.kernelci.org/next/master/next-20180423/arm/multi_v7_defconfi
> g/lab-collabora/sleep-rk3288-veyron-jaq.html
I think at this point, it might be good to do a "v4 RESEND" in a _new_ mail
thread, because from the lack of communication it really looks like this
fell through completely.
Ideally also include in the commit message that his breaks kernelCI tests
and real board users (and of course recent tags).
Heiko
prev parent reply other threads:[~2018-04-24 8:58 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-22 9:39 [PATCH] usb: dwc2: dwc2_vbus_supply_init: fix error check Tomeu Vizoso
2018-03-22 11:39 ` Heiko Stübner
2018-03-22 11:41 ` Heiko Stübner
2018-03-22 12:21 ` Amelie DELAUNAY
2018-03-22 13:06 ` [PATCH v2] " Tomeu Vizoso
2018-03-22 13:14 ` [PATCH v3] " Tomeu Vizoso
2018-03-22 13:26 ` Heiko Stübner
2018-03-22 13:34 ` Tomeu Vizoso
2018-03-24 0:24 ` kbuild test robot
2018-03-26 9:00 ` [PATCH v4] " Tomeu Vizoso
2018-03-26 10:56 ` Amelie DELAUNAY
2018-03-26 11:51 ` Heiko Stübner
2018-04-04 13:33 ` Tomeu Vizoso
2018-04-05 7:54 ` Minas Harutyunyan
2018-04-05 8:10 ` Tomeu Vizoso
2018-04-05 9:02 ` Grigor Tovmasyan
2018-04-05 8:58 ` Grigor Tovmasyan
2018-04-05 9:51 ` Minas Harutyunyan
2018-04-10 12:28 ` Heiko Stuebner
2018-04-10 13:52 ` Minas Harutyunyan
2018-04-10 15:37 ` Heiko Stübner
2018-04-11 6:50 ` Minas Harutyunyan
2018-04-23 13:24 ` Tomeu Vizoso
2018-04-24 8:58 ` Heiko Stübner [this message]
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=3454244.YafNKb8Syk@diego \
--to=heiko@sntech.de \
--cc=Minas.Harutyunyan@synopsys.com \
--cc=amelie.delaunay@st.com \
--cc=felipe.balbi@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=tomeu.vizoso@collabora.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