From: "Steinar H. Gunderson" <sgunderson@bigfoot.com>
To: Vivek Gautam <gautamvivek1987@gmail.com>
Cc: "Steinar H. Gunderson" <sesse@google.com>,
"Krzysztof Kozłowski" <k.kozlowski@samsung.com>,
"Mark Brown" <broonie@debian.org>,
"linux-samsung-soc@vger.kernel.org"
<linux-samsung-soc@vger.kernel.org>,
823552@bugs.debian.org, balbi@kernel.org,
"Linux USB Mailing List" <linux-usb@vger.kernel.org>
Subject: Re: [PATCH] dwc3-exynos: Fix deferred probing storm.
Date: Fri, 27 May 2016 13:46:41 +0200 [thread overview]
Message-ID: <20160527114641.GA39472@sesse.net> (raw)
In-Reply-To: <CAFp+6iGFkquYkHCCJRkQALRZ2g-htiKbrJZbJwMoAMR=+A5u_Q@mail.gmail.com>
On Fri, May 27, 2016 at 03:23:35PM +0530, Vivek Gautam wrote:
> I don't have any concerns with the patch apart from the ones
> Krzysztof has already pointed out.
> LGTM.
Should I repost the patch, or will people just make these commit message
changes for me? I guess balbi@ is the right person to review and merge,
since he maintains the driver.
/* Steinar */
--
Homepage: https://www.sesse.net/
next prev parent reply other threads:[~2016-05-27 11:47 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160515173900.GC21194@sesse.net>
2016-05-21 14:43 ` Endless "supply vcc not found, using dummy regulator" Steinar H. Gunderson
2016-05-23 13:47 ` Steinar H. Gunderson
2016-05-23 14:40 ` Steinar H. Gunderson
2016-05-23 16:24 ` Mark Brown
2016-05-23 17:06 ` Steinar H. Gunderson
2016-05-23 17:46 ` Steinar H. Gunderson
2016-05-23 18:56 ` Mark Brown
2016-05-23 18:44 ` Mark Brown
2016-05-24 15:06 ` Krzysztof Kozlowski
2016-05-24 15:26 ` Steinar H. Gunderson
2016-05-24 15:45 ` Mark Brown
2016-05-24 15:53 ` Krzysztof Kozlowski
2016-05-24 16:44 ` Steinar H. Gunderson
[not found] ` <574478FE.4070800-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2016-05-24 19:24 ` [PATCH] " Steinar H. Gunderson
2016-05-24 18:13 ` [PATCH v2] dwc3-exynos: Fix deferred probing storm Steinar H. Gunderson
2016-05-24 18:13 ` [PATCH] " Steinar H. Gunderson
2016-05-25 7:54 ` Krzysztof Kozlowski
2016-05-27 9:53 ` Vivek Gautam
2016-05-27 11:46 ` Steinar H. Gunderson [this message]
2016-05-27 13:13 ` Krzysztof Kozlowski
[not found] ` <5748480D.8000501-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2016-05-27 13:12 ` Felipe Balbi
[not found] ` <87bn3rprtw.fsf-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2016-05-27 13:25 ` Steinar H. Gunderson
2016-05-27 13:26 ` Felipe Balbi
2016-05-30 17:46 ` Steinar H. Gunderson
2016-05-25 12:16 ` [PATCH] Re: Endless "supply vcc not found, using dummy regulator" Anand Moon
2016-05-25 17:52 ` Steinar H. Gunderson
2016-05-26 12:57 ` Steinar H. Gunderson
[not found] ` <20160526125757.GA23797-gdzBep0Ce9heoWH0uzbU5w@public.gmane.org>
2016-05-27 9:32 ` Vivek Gautam
[not found] ` <CAFp+6iE_QW0BDO-Z1Ce5zrUJiToWD_8UtnCFnfKLeaYyys7U8A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-05-27 9:39 ` Steinar H. Gunderson
[not found] ` <20160527093919.GA34987-gdzBep0Ce9heoWH0uzbU5w@public.gmane.org>
2016-05-27 9:43 ` Vivek Gautam
2016-05-24 15:39 ` Mark Brown
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=20160527114641.GA39472@sesse.net \
--to=sgunderson@bigfoot.com \
--cc=823552@bugs.debian.org \
--cc=balbi@kernel.org \
--cc=broonie@debian.org \
--cc=gautamvivek1987@gmail.com \
--cc=k.kozlowski@samsung.com \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=sesse@google.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