From: Vinod Koul <vkoul@kernel.org>
To: Amelie DELAUNAY <amelie.delaunay@st.com>
Cc: Etienne Carriere <etienne.carriere@st.com>,
Alexandre Torgue <alexandre.torgue@st.com>,
linux-kernel@vger.kernel.org,
Kishon Vijay Abraham I <kishon@ti.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2] phy: stm32: don't print an error on probe deferral
Date: Mon, 16 Nov 2020 15:20:14 +0530 [thread overview]
Message-ID: <20201116095014.GU7499@vkoul-mobl> (raw)
In-Reply-To: <1b91bea5-ffbf-37fb-98ac-6abc5f373375@st.com>
On 16-11-20, 09:02, Amelie DELAUNAY wrote:
> Hi Vinod,
>
> On 11/16/20 8:37 AM, Vinod Koul wrote:
> > On 10-11-20, 11:23, Amelie Delaunay wrote:
> > > Change stm32-usbphyc driver to not print an error message when the device
> > > probe operation is deferred.
> >
> > Applied all, thanks
> >
>
> I'm sorry for the mess, I sent a v2 for the patch 1/2:
> https://lore.kernel.org/patchwork/patch/1336206/
> Indeed, I forgot the "return" before dev_err_probe.
No worries, I have dropped this and picked v2.
Do check if the patches are fine.
Thanks for letting me know
--
~Vinod
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-11-16 9:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-10 10:23 [PATCH 1/2] phy: stm32: don't print an error on probe deferral Amelie Delaunay
2020-11-10 10:23 ` [PATCH 2/2] phy: stm32: defer probe for reset controller Amelie Delaunay
2020-11-16 7:37 ` [PATCH 1/2] phy: stm32: don't print an error on probe deferral Vinod Koul
2020-11-16 8:02 ` Amelie DELAUNAY
2020-11-16 9:50 ` Vinod Koul [this message]
2020-11-16 10:18 ` Amelie DELAUNAY
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=20201116095014.GU7499@vkoul-mobl \
--to=vkoul@kernel.org \
--cc=alexandre.torgue@st.com \
--cc=amelie.delaunay@st.com \
--cc=etienne.carriere@st.com \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.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