All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@google.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
	idosch@nvidia.com, netdev@vger.kernel.org,
	eric.dumazet@gmail.com
Subject: Re: [PATCH v2 net-next 0/2] net: use net->dev_by_index in two places
Date: Wed, 14 Feb 2024 02:50:30 +0000	[thread overview]
Message-ID: <170787903011.13249.14481317448658195771.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240211214404.1882191-1-edumazet@google.com>

Hello:

This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Sun, 11 Feb 2024 21:44:02 +0000 you wrote:
> Bring "ip link" ordering to /proc/net/dev one (by ifindexes).
> 
> Do the same for /proc/net/vlan/config
> 
> v2: added suggestions from Jakub Kicinski and Ido Schimmel, thanks !
>   Link: https://lore.kernel.org/all/20240209142441.6c56435b@kernel.org/
>   Link: https://lore.kernel.org/all/ZckR-XOsULLI9EHc@shredder/
> 
> [...]

Here is the summary with links:
  - [v2,net-next,1/2] vlan: use xarray iterator to implement /proc/net/vlan/config
    https://git.kernel.org/netdev/net-next/c/f383ced24d6a
  - [v2,net-next,2/2] rtnetlink: use xarray iterator to implement rtnl_dump_ifinfo()
    https://git.kernel.org/netdev/net-next/c/3e41af90767d

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



      parent reply	other threads:[~2024-02-14  2:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-11 21:44 [PATCH v2 net-next 0/2] net: use net->dev_by_index in two places Eric Dumazet
2024-02-11 21:44 ` [PATCH v2 net-next 1/2] vlan: use xarray iterator to implement /proc/net/vlan/config Eric Dumazet
2024-02-12 16:09   ` Ido Schimmel
2024-02-11 21:44 ` [PATCH v2 net-next 2/2] rtnetlink: use xarray iterator to implement rtnl_dump_ifinfo() Eric Dumazet
2024-02-12 16:10   ` Ido Schimmel
2024-02-14  2:50 ` 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=170787903011.13249.14481317448658195771.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=eric.dumazet@gmail.com \
    --cc=idosch@nvidia.com \
    --cc=kuba@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.