public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel•org
To: Zheng Zengkai <zhengzengkai@huawei•com>
Cc: davem@davemloft•net, edumazet@google•com, kuba@kernel•org,
	pabeni@redhat•com, mark.einon@gmail•com,
	siva.kallam@broadcom•com, prashant@broadcom•com,
	mchan@broadcom•com, steve.glendinning@shawell•net,
	mw@semihalf•com, jiawenwu@trustnetic•com,
	mengyuanlou@net-swift•com, netdev@vger•kernel.org,
	wangxiongfeng2@huawei•com
Subject: Re: [PATCH net-next 0/5] net: Use pci_dev_id() to simplify the code
Date: Sun, 13 Aug 2023 11:40:21 +0000	[thread overview]
Message-ID: <169192682167.1919.12638086769759586741.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230811110702.31019-1-zhengzengkai@huawei.com>

Hello:

This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft•net>:

On Fri, 11 Aug 2023 19:06:57 +0800 you wrote:
> PCI core API pci_dev_id() can be used to get the BDF number for a pci
> device. Use the API to simplify the code.
> 
> Zheng Zengkai (5):
>   et131x: Use pci_dev_id() to simplify the code
>   tg3: Use pci_dev_id() to simplify the code
>   net: smsc: Use pci_dev_id() to simplify the code
>   net: tc35815: Use pci_dev_id() to simplify the code
>   net: ngbe: use pci_dev_id() to simplify the code
> 
> [...]

Here is the summary with links:
  - [net-next,1/5] et131x: Use pci_dev_id() to simplify the code
    https://git.kernel.org/netdev/net-next/c/fcbb797458e1
  - [net-next,2/5] tg3: Use pci_dev_id() to simplify the code
    https://git.kernel.org/netdev/net-next/c/6ecb2ced346f
  - [net-next,3/5] net: smsc: Use pci_dev_id() to simplify the code
    https://git.kernel.org/netdev/net-next/c/adc4d18538ec
  - [net-next,4/5] net: tc35815: Use pci_dev_id() to simplify the code
    https://git.kernel.org/netdev/net-next/c/ca51d1356071
  - [net-next,5/5] net: ngbe: use pci_dev_id() to simplify the code
    https://git.kernel.org/netdev/net-next/c/cf9b107f5fdd

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2023-08-13 11:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-11 11:06 [PATCH net-next 0/5] net: Use pci_dev_id() to simplify the code Zheng Zengkai
2023-08-11 11:06 ` [PATCH net-next 1/5] et131x: " Zheng Zengkai
2023-08-11 11:06 ` [PATCH net-next 2/5] tg3: " Zheng Zengkai
2023-08-11 11:07 ` [PATCH net-next 3/5] net: smsc: " Zheng Zengkai
2023-08-11 11:07 ` [PATCH net-next 4/5] net: tc35815: " Zheng Zengkai
2023-08-11 11:07 ` [PATCH net-next 5/5] net: ngbe: use " Zheng Zengkai
2023-08-11 12:18 ` [PATCH net-next 0/5] net: Use " Przemek Kitszel
2023-08-13 11:40 ` 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=169192682167.1919.12638086769759586741.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel$(echo .)org \
    --cc=davem@davemloft$(echo .)net \
    --cc=edumazet@google$(echo .)com \
    --cc=jiawenwu@trustnetic$(echo .)com \
    --cc=kuba@kernel$(echo .)org \
    --cc=mark.einon@gmail$(echo .)com \
    --cc=mchan@broadcom$(echo .)com \
    --cc=mengyuanlou@net-swift$(echo .)com \
    --cc=mw@semihalf$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=pabeni@redhat$(echo .)com \
    --cc=prashant@broadcom$(echo .)com \
    --cc=siva.kallam@broadcom$(echo .)com \
    --cc=steve.glendinning@shawell$(echo .)net \
    --cc=wangxiongfeng2@huawei$(echo .)com \
    --cc=zhengzengkai@huawei$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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