From: patchwork-bot+netdevbpf@kernel.org
To: Rangoju@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org,
Raju <Raju.Rangoju@amd.com>
Cc: horms@kernel.org, andrew+netdev@lunn.ch, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Shyam-sundar.S-k@amd.com
Subject: Re: [PATCH net-next v3 0/5] amd-xgbe: add support for AMD Renoir
Date: Tue, 13 May 2025 12:00:36 +0000 [thread overview]
Message-ID: <174713763601.1640156.13599661807797356779.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250509155325.720499-1-Raju.Rangoju@amd.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Fri, 9 May 2025 21:23:20 +0530 you wrote:
> Add support for a new AMD Ethernet device called "Renoir". It has a new
> PCI ID, add this to the current list of supported devices in the
> amd-xgbe devices. Also, the BAR1 addresses cannot be used to access the
> PCS registers on Renoir platform, use the indirect addressing via SMN
> instead.
>
> Changes since v2:
> - include linux/pci.h in xgbe-dev.c to ensure pci_err() is defined
> - line wrap to 80 columns wide
> - address Checkpatch warning "Improper SPDX comment style"
> - use the correct device name Renoir instead of Crater
> - follow reverse Xmass tree ordering
>
> [...]
Here is the summary with links:
- [net-next,v3,1/5] amd-xgbe: reorganize the code of XPCS access
https://git.kernel.org/netdev/net-next/c/2d4407160f60
- [net-next,v3,2/5] amd-xgbe: reorganize the xgbe_pci_probe() code path
https://git.kernel.org/netdev/net-next/c/bbbd7303ea18
- [net-next,v3,3/5] amd-xgbe: add support for new XPCS routines
https://git.kernel.org/netdev/net-next/c/e49479f30ef9
- [net-next,v3,4/5] amd-xgbe: Add XGBE_XPCS_ACCESS_V3 support to xgbe_pci_probe()
https://git.kernel.org/netdev/net-next/c/ab95bc9aa795
- [net-next,v3,5/5] amd-xgbe: add support for new pci device id 0x1641
https://git.kernel.org/netdev/net-next/c/795f86ff0505
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:[~2025-05-13 11:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-09 15:53 [PATCH net-next v3 0/5] amd-xgbe: add support for AMD Renoir Raju Rangoju
2025-05-09 15:53 ` [PATCH net-next v3 1/5] amd-xgbe: reorganize the code of XPCS access Raju Rangoju
2025-05-12 13:55 ` Simon Horman
2025-05-09 15:53 ` [PATCH net-next v3 2/5] amd-xgbe: reorganize the xgbe_pci_probe() code path Raju Rangoju
2025-05-12 13:56 ` Simon Horman
2025-05-09 15:53 ` [PATCH net-next v3 3/5] amd-xgbe: add support for new XPCS routines Raju Rangoju
2025-05-12 13:56 ` Simon Horman
2025-05-09 15:53 ` [PATCH net-next v3 4/5] amd-xgbe: Add XGBE_XPCS_ACCESS_V3 support to xgbe_pci_probe() Raju Rangoju
2025-05-12 13:56 ` Simon Horman
2025-05-09 15:53 ` [PATCH net-next v3 5/5] amd-xgbe: add support for new pci device id 0x1641 Raju Rangoju
2025-05-12 13:56 ` Simon Horman
2025-05-13 12:00 ` 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=174713763601.1640156.13599661807797356779.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Raju.Rangoju@amd.com \
--cc=Rangoju@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
--cc=Shyam-sundar.S-k@amd.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).