From: patchwork-bot+netdevbpf@kernel.org
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: rajur@chelsio.com, kuba@kernel.org, davem@davemloft.net,
netdev@vger.kernel.org, rahul.lakkireddy@chelsio.com
Subject: Re: [PATCH net-next] cxgb4: remove unused vpd_cap_addr
Date: Tue, 09 Feb 2021 00:10:06 +0000 [thread overview]
Message-ID: <161282940695.21160.16687766217971899380.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <55c53828-1071-1bdb-6a47-c1f41e3f83d1@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (refs/heads/master):
On Mon, 8 Feb 2021 21:26:07 +0100 you wrote:
> It is likely that this is a leftover from T3 driver heritage. cxgb4 uses
> the PCI core VPD access code that handles detection of VPD capabilities.
>
> Reviewed-by: Alexander Duyck <alexanderduyck@fb.com>
> Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
> ---
> - resend after dropping patches 2 and 3 from the series
>
> [...]
Here is the summary with links:
- [net-next] cxgb4: remove unused vpd_cap_addr
https://git.kernel.org/netdev/net-next/c/4429c5fc3dbd
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:[~2021-02-09 0:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-05 19:26 [PATCH resend net-next v2 0/3] cxgb4: improve PCI VPD handling Heiner Kallweit
2021-02-05 19:29 ` [PATCH resend net-next v2 1/3] cxgb4: remove unused vpd_cap_addr Heiner Kallweit
2021-02-05 19:29 ` [PATCH resend net-next v2 2/3] PCI/VPD: Change Chelsio T4 quirk to provide access to full virtual address space Heiner Kallweit
2021-02-05 21:46 ` Bjorn Helgaas
2021-02-05 22:31 ` Heiner Kallweit
2021-02-08 19:47 ` Rahul Lakkireddy
2021-02-08 20:21 ` Heiner Kallweit
2021-02-05 19:30 ` [PATCH resend net-next v2 3/3] cxgb4: remove changing VPD len Heiner Kallweit
2021-02-08 20:26 ` [PATCH net-next] cxgb4: remove unused vpd_cap_addr Heiner Kallweit
2021-02-09 0: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=161282940695.21160.16687766217971899380.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rahul.lakkireddy@chelsio.com \
--cc=rajur@chelsio.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).