From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org, NXP Linux Team <linux-imx@nxp.com>,
Joakim Zhang <qiangqing.zhang@nxp.com>,
kernel@pengutronix.de, "David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH net-next] net: fec: Do proper error checking for enet_out clk
Date: Tue, 29 Mar 2022 07:47:10 +0200 [thread overview]
Message-ID: <20220329054710.rw75gc74wunsf7ms@pengutronix.de> (raw)
In-Reply-To: <20220328160910.3eb8fb87@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 844 bytes --]
On Mon, Mar 28, 2022 at 04:09:10PM -0700, Jakub Kicinski wrote:
> On Fri, 25 Mar 2022 17:55:43 +0100 Uwe Kleine-König wrote:
> > An error code returned by devm_clk_get() might have other meanings than
> > "This clock doesn't exist". So use devm_clk_get_optional() and handle
> > all remaining errors as fatal.
> >
> > Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> > ---
> > Hello,
> >
> > this isn't urgent and doesn't fix a problem I encountered, just noticed
> > this patch opportunity while looking up something different in the
> > driver.
>
> Would you mind reposting after the merge window?
> We keep net-next closed until -rc1 is cut.
I somehow expected there is an implicit queue of patches that is
processed once net-next opens again. But sure, will resend after -rc1.
Best regards
Uwe
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2022-03-29 5:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-25 16:55 [PATCH net-next] net: fec: Do proper error checking for enet_out clk Uwe Kleine-König
2022-03-28 23:09 ` Jakub Kicinski
2022-03-29 5:47 ` Uwe Kleine-König [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=20220329054710.rw75gc74wunsf7ms@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=davem@davemloft.net \
--cc=kernel@pengutronix.de \
--cc=kuba@kernel.org \
--cc=linux-imx@nxp.com \
--cc=netdev@vger.kernel.org \
--cc=qiangqing.zhang@nxp.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;
as well as URLs for NNTP newsgroup(s).