netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: MD Danish Anwar <danishanwar@ti.com>,
	Roger Quadros <rogerq@kernel.org>,
	Andrew Lunn <andrew+netdev@lunn.ch>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Paolo Abeni <pabeni@redhat.com>,
	Alexandre Torgue <alexandre.torgue@foss.st.com>,
	Jose Abreu <joabreu@synopsys.com>,
	Maxime Coquelin <mcoquelin.stm32@gmail.com>,
	Shawn Guo <shawnguo@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Fabio Estevam <festevam@gmail.com>,
	linux-arm-kernel@lists.infradead.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-stm32@st-md-mailman.stormreply.com, imx@lists.linux.dev
Subject: Re: [PATCH net-next 2/5] net: ti: icssg-prueth: Use syscon_regmap_lookup_by_phandle_args
Date: Tue, 14 Jan 2025 18:06:50 -0800	[thread overview]
Message-ID: <20250114180650.4ba50ea4@kernel.org> (raw)
In-Reply-To: <1376b2b3-90c4-4f06-b05c-10b9e5d1535e@linaro.org>

On Mon, 13 Jan 2025 12:04:35 +0100 Krzysztof Kozlowski wrote:
> > The patch only touches `drivers/net/ethernet/ti/am65-cpsw-nuss.c`
> > however the subject suggests the patch is related to "icssg-prueth".
> > 
> > I suppose the subject should be changed to "am65-cpsw-nuss" instead of
> > "icssg-prueth"  
> 
> Indeed, copy paste.

Will fix when applying.

  reply	other threads:[~2025-01-15  2:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-12 13:32 [PATCH net-next 0/5] net: ethernet: Simplify few things Krzysztof Kozlowski
2025-01-12 13:32 ` [PATCH net-next 1/5] net: ti: icssg-prueth: Do not print physical memory addresses Krzysztof Kozlowski
2025-01-13  8:03   ` MD Danish Anwar
2025-01-12 13:32 ` [PATCH net-next 2/5] net: ti: icssg-prueth: Use syscon_regmap_lookup_by_phandle_args Krzysztof Kozlowski
2025-01-13  8:07   ` MD Danish Anwar
2025-01-13 11:04     ` Krzysztof Kozlowski
2025-01-15  2:06       ` Jakub Kicinski [this message]
2025-01-12 13:32 ` [PATCH net-next 3/5] net: stmmac: imx: " Krzysztof Kozlowski
2025-01-12 13:32 ` [PATCH net-next 4/5] net: stmmac: sti: " Krzysztof Kozlowski
2025-01-12 13:32 ` [PATCH net-next 5/5] net: stmmac: stm32: " Krzysztof Kozlowski
2025-01-13  8:05   ` Yanteng Si
2025-01-13 11:08     ` Krzysztof Kozlowski
2025-01-13 17:01     ` Andrew Lunn
2025-01-14  1:58       ` Yanteng Si
2025-01-15  2:10 ` [PATCH net-next 0/5] net: ethernet: Simplify few things patchwork-bot+netdevbpf

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=20250114180650.4ba50ea4@kernel.org \
    --to=kuba@kernel.org \
    --cc=alexandre.torgue@foss.st.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=danishanwar@ti.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=festevam@gmail.com \
    --cc=imx@lists.linux.dev \
    --cc=joabreu@synopsys.com \
    --cc=kernel@pengutronix.de \
    --cc=krzysztof.kozlowski@linaro.org \
    --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 \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=rogerq@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.org \
    /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).