From: Simon Horman <horms@kernel.org>
To: Minda Chen <minda.chen@starfivetech.com>
Cc: Alexandre Torgue <alexandre.torgue@foss.st.com>,
Jose Abreu <joabreu@synopsys.com>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com
Subject: Re: [PATCH v1] stmmac: mmc: dwmac4: Add ip payload error statistics
Date: Mon, 16 Sep 2024 16:23:25 +0100 [thread overview]
Message-ID: <20240916152325.GB396300@kernel.org> (raw)
In-Reply-To: <20240916094812.29804-1-minda.chen@starfivetech.com>
On Mon, Sep 16, 2024 at 05:48:12PM +0800, Minda Chen wrote:
> Add dwmac4 ip payload error statistics, and rename discripter bit macro
> because latest version descriptor IPCE bit claims include ip checksum
> error and l4 segment length error.
>
> Signed-off-by: Minda Chen <minda.chen@starfivetech.com>
Hi Minda,
Some feedback on process.
net-next is currently closed for the v6.12 merge window.
Please consider reposting this patch once it re-opens,
after v6.12-rc1 is released, likely about two weeks from now.
RFC patches, and fixes for net are, OTOH, welcome any time.
Also, when posting patches for net-next, please explicitly
target them as such.
Subject: [PATCH net-next] ...
Link: https://docs.kernel.org/process/maintainer-netdev.html
And lastly, I don't think 'mmc: ' belongs in the patch prefix.
This is an Ethernet driver, right? Looking over git history,
it seems that 'net: stmmac: ' is appropriate here.
Subject: [PATCH net-next] net: stmmac: ...
--
pw-bot: defer
next prev parent reply other threads:[~2024-09-16 15:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-16 9:48 [PATCH v1] stmmac: mmc: dwmac4: Add ip payload error statistics Minda Chen
2024-09-16 15:23 ` Simon Horman [this message]
2024-09-18 1:15 ` Minda Chen
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=20240916152325.GB396300@kernel.org \
--to=horms@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=joabreu@synopsys.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=minda.chen@starfivetech.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 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).