From: Jakub Kicinski <kuba@kernel.org>
To: "Russell King (Oracle)" <linux@armlinux.org.uk>
Cc: Andrew Lunn <andrew@lunn.ch>,
Heiner Kallweit <hkallweit1@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
linux-arm-kernel@lists.infradead.org,
linux-stm32@st-md-mailman.stormreply.com,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
netdev@vger.kernel.org, Paolo Abeni <pabeni@redhat.com>
Subject: Re: [PATCH net-next 2/2] net: stmmac: dwc-qos: clean up clock initialisation
Date: Mon, 24 Feb 2025 13:29:38 -0800 [thread overview]
Message-ID: <20250224132938.4b352786@kernel.org> (raw)
In-Reply-To: <Z7yjLjfNq89vPnOd@shell.armlinux.org.uk>
On Mon, 24 Feb 2025 16:49:50 +0000 Russell King (Oracle) wrote:
> On Mon, Feb 24, 2025 at 02:47:19PM +0000, Russell King (Oracle) wrote:
> > Clean up the clock initialisation by providing a helper to find a
> > named clock in the bulk clocks, and provide the name of the stmmac
> > clock in match data so we can locate the stmmac clock in generic
> > code.
> >
> > Signed-off-by: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
>
> Yet more warnings and errors from NIPA, yet this patch passes my local
> build tests.
>
> As no one looked at v1, I don't see the point of waiting 24h before
> posting v3... no one is probably looking at v2.
NIPA builds with W=1 C=1, FWIW, looks like a sparse warning.
prev parent reply other threads:[~2025-02-24 21:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-24 14:47 [PATCH net-next v2 0/2] net: stmmac: dwc-qos: clean up clock initialisation Russell King (Oracle)
2025-02-24 14:47 ` [PATCH net-next 1/2] net: stmmac: dwc-qos: name struct plat_stmmacenet_data consistently Russell King (Oracle)
2025-02-24 14:47 ` [PATCH net-next 2/2] net: stmmac: dwc-qos: clean up clock initialisation Russell King (Oracle)
2025-02-24 16:49 ` Russell King (Oracle)
2025-02-24 21:29 ` Jakub Kicinski [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=20250224132938.4b352786@kernel.org \
--to=kuba@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux@armlinux.org.uk \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.