All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Quentin Deslandes <qde@naccy.de>
Cc: bpf@vger.kernel.org, andrii@kernel.org, eddyz87@gmail.com,
	ast@kernel.org, daniel@iogearbox.net, martin.lau@linux.dev,
	song@kernel.org, yonghong.song@linux.dev,
	john.fastabend@gmail.com, kpsingh@kernel.org, sdf@google.com,
	haoluo@google.com, jolsa@kernel.org,
	linux-kernel@vger.kernel.org, kernel-team@meta.com
Subject: Re: [PATCH 0/2] libbpf: fixes for character arrays dump
Date: Wed, 17 Apr 2024 13:30:44 +0000	[thread overview]
Message-ID: <171336064453.13200.11475290179451492010.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240413211258.134421-1-qde@naccy.de>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:

On Sat, 13 Apr 2024 23:12:56 +0200 you wrote:
> Patch #1 fixes an issue where character arrays in dumps would
> have their last bracket misaligned if a '\0' was found in the
> array.
> 
> Patch #2 fixes an issue where only the first character array
> containing '\0' would be printed, the other ones would be
> dumped as empty.
> 
> [...]

Here is the summary with links:
  - [1/2] libbpf: fix misaligned array closing bracket
    https://git.kernel.org/bpf/bpf-next/c/9213e52970a5
  - [2/2] libbpf: fix dump of subsequent char arrays
    https://git.kernel.org/bpf/bpf-next/c/e739e01d8df8

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-04-17 13:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-13 21:12 [PATCH 0/2] libbpf: fixes for character arrays dump Quentin Deslandes
2024-04-13 21:12 ` [PATCH 1/2] libbpf: fix misaligned array closing bracket Quentin Deslandes
2024-04-13 21:12 ` [PATCH 2/2] libbpf: fix dump of subsequent char arrays Quentin Deslandes
2024-04-17 13:30 ` 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=171336064453.13200.11475290179451492010.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=haoluo@google.com \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=kernel-team@meta.com \
    --cc=kpsingh@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=qde@naccy.de \
    --cc=sdf@google.com \
    --cc=song@kernel.org \
    --cc=yonghong.song@linux.dev \
    /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.