public inbox for bpf@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: martin.lau@linux.dev, bpf@vger.kernel.org, laoar.shao@gmail.com,
	quentin@isovalent.com
Subject: Re: [PATCH bpf-next 1/2] bpftool: Implement link show support for tcx
Date: Wed, 16 Aug 2023 17:20:22 +0000	[thread overview]
Message-ID: <169220642222.4978.1255568633447531671.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230816095651.10014-1-daniel@iogearbox.net>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Martin KaFai Lau <martin.lau@kernel.org>:

On Wed, 16 Aug 2023 11:56:50 +0200 you wrote:
> Add support to dump tcx link information to bpftool. This adds a
> common helper show_link_ifindex_{plain,json}() which can be reused
> also for other link types. The plain text and json device output is
> the same format as in bpftool net dump.
> 
> Below shows an example link dump output along with a cgroup link
> for comparison:
> 
> [...]

Here is the summary with links:
  - [bpf-next,1/2] bpftool: Implement link show support for tcx
    https://git.kernel.org/bpf/bpf-next/c/e16e6c6df475
  - [bpf-next,2/2] bpftool: Implement link show support for xdp
    https://git.kernel.org/bpf/bpf-next/c/053bbf9bff58

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-16 17:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-16  9:56 [PATCH bpf-next 1/2] bpftool: Implement link show support for tcx Daniel Borkmann
2023-08-16  9:56 ` [PATCH bpf-next 2/2] bpftool: Implement link show support for xdp Daniel Borkmann
2023-08-16 14:23 ` [PATCH bpf-next 1/2] bpftool: Implement link show support for tcx Yafang Shao
2023-08-16 15:11   ` Daniel Borkmann
2023-08-16 16:23     ` Yafang Shao
2023-08-16 17:20 ` 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=169220642222.4978.1255568633447531671.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=laoar.shao@gmail.com \
    --cc=martin.lau@linux.dev \
    --cc=quentin@isovalent.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