From: patchwork-bot+netdevbpf@kernel.org
To: Furong Xu <0x1207@gmail.com>
Cc: davem@davemloft.net, alexandre.torgue@foss.st.com,
joabreu@synopsys.com, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, mcoquelin.stm32@gmail.com,
jpinto@synopsys.com, horms@kernel.org, netdev@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, xfr@outlook.com, rock.xu@nio.com
Subject: Re: [PATCH net-next v1 1/1] net: stmmac: xgmac: show more MAC HW features in debugfs
Date: Mon, 14 Aug 2023 07:10:23 +0000 [thread overview]
Message-ID: <169199702331.11756.17114238819765963207.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230811125139.284272-1-0x1207@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Fri, 11 Aug 2023 20:51:39 +0800 you wrote:
> 1. Show TSSTSSEL(Timestamp System Time Source),
> ADDMACADRSEL(additional MAC addresses), SMASEL(SMA/MDIO Interface),
> HDSEL(Half-duplex Support) in debugfs.
> 2. Show exact number of additional MAC address registers for XGMAC2 core.
> 3. XGMAC2 core does not have different IP checksum offload types, so just
> show rx_coe instead of rx_coe_type1 or rx_coe_type2.
> 4. XGMAC2 core does not have rxfifo_over_2048 definition, skip it.
>
> [...]
Here is the summary with links:
- [net-next,v1,1/1] net: stmmac: xgmac: show more MAC HW features in debugfs
https://git.kernel.org/netdev/net-next/c/58c1e0bace59
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-08-14 7:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-11 12:51 [PATCH net-next v1 1/1] net: stmmac: xgmac: show more MAC HW features in debugfs Furong Xu
2023-08-14 7:10 ` patchwork-bot+netdevbpf [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=169199702331.11756.17114238819765963207.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=0x1207@gmail.com \
--cc=alexandre.torgue@foss.st.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=joabreu@synopsys.com \
--cc=jpinto@synopsys.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=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rock.xu@nio.com \
--cc=xfr@outlook.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