From: Linkui Xiao <xiaolinkui@126.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: maxime.chevallier@bootlin.com, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
mcoquelin.stm32@gmail.com, alexandre.torgue@foss.st.com,
lorenzo.bianconi@oss.qualcomm.com, netdev@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Linkui Xiao <xiaolinkui@kylinos.cn>,
stable@vger.kernel.org
Subject: Re: [PATCH net v3] net: stmmac: request the MDIO reset GPIO only once
Date: Sat, 26 Sep 2026 16:22:10 +0800 [thread overview]
Message-ID: <9ecf6f60-a2ab-4905-9ba6-011523684547@126.com> (raw)
In-Reply-To: <20260924093720.1aaa697e@kernel.org>
Hi Jakub,
On 2026/9/25 00:37, Jakub Kicinski wrote:
> On Mon, 21 Sep 2026 09:57:27 +0800 Linkui Xiao wrote:
>> +struct gpio_desc;
>> struct stmmac_pcs;
>>
>> struct stmmac_resources {
>> @@ -287,6 +288,8 @@ struct stmmac_priv {
>>
>> unsigned int pause_time;
>> struct mii_bus *mii;
>> + struct gpio_desc *mdio_reset_gpio;
>> + u32 mdio_reset_delays[3];
>
> Someone already marked it as changes requested but also no need to
> forward declare structs unless first use is as function arguemnt.
Thanks for the review. I'll remove the forward declaration of
struct gpio_desc and include <linux/gpio/consumer.h> in stmmac.h
instead, since its first use is as a struct member.
I'll send v4 shortly.
Thanks,
Linkui
prev parent reply other threads:[~2026-09-26 8:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 1:57 [PATCH net v3] net: stmmac: request the MDIO reset GPIO only once Linkui Xiao
2026-09-23 4:57 ` netdev-bot+sashiko
2026-09-24 16:37 ` Jakub Kicinski
2026-09-26 8:22 ` Linkui Xiao [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=9ecf6f60-a2ab-4905-9ba6-011523684547@126.com \
--to=xiaolinkui@126.com \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=lorenzo.bianconi@oss.qualcomm.com \
--cc=maxime.chevallier@bootlin.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stable@vger.kernel.org \
--cc=xiaolinkui@kylinos.cn \
/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