From: patchwork-bot+netdevbpf@kernel.org
To: Chris Arges <carges@cloudflare.com>
Cc: bpf@vger.kernel.org, linux-kernel@vger.kernel.org,
quentin@isovalent.com, ast@kernel.org, andrii@kernel.org
Subject: Re: [PATCH] bpftool: ensure bytes_memlock json output is correct
Date: Thu, 10 Mar 2022 23:30:10 +0000 [thread overview]
Message-ID: <164695501010.21304.950456748637627330.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <b6601087-0b11-33cc-904a-1133d1500a10@cloudflare.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Thu, 10 Mar 2022 16:28:13 -0600 you wrote:
> >From 40107402b805c4eaca5ce7a0db66d10e9219f2bf Mon Sep 17 00:00:00 2001
> From: Chris J Arges <carges@cloudflare.com>
> Date: Wed, 9 Mar 2022 15:41:58 -0600
> Subject: [PATCH] bpftool: ensure bytes_memlock json output is correct
>
> If a bpf map is created over 2^32 the memlock value as displayed in JSON
> format will be incorrect. Use atoll instead of atoi so that the correct
> number is displayed.
>
> [...]
Here is the summary with links:
- bpftool: ensure bytes_memlock json output is correct
https://git.kernel.org/bpf/bpf-next/c/357b3cc3c046
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:[~2022-03-10 23:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-10 22:28 [PATCH] bpftool: ensure bytes_memlock json output is correct Chris Arges
2022-03-10 23: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=164695501010.21304.950456748637627330.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=carges@cloudflare.com \
--cc=linux-kernel@vger.kernel.org \
--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 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.