From: Hungyu Lin <dennylin0707@gmail.com>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: qmo@kernel.org, bpf@vger.kernel.org, andrii@kernel.org,
ast@kernel.org, daniel@iogearbox.net,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH bpf-next] bpftool: avoid sign extension in unsigned enum JSON dumps
Date: Fri, 30 Oct 2026 13:00:25 -0700 [thread overview]
Message-ID: <CAGEkeHcq7HeecPyTSYuHWMhCyOAbF7br+UjrFfLiQmgi6kTxhw@mail.gmail.com> (raw)
In-Reply-To: <CAEf4BzaMDRa8xD1oR587P82MYKCYR61gyjgvjKySSnnqFb27pw@mail.gmail.com>
> please drop RFC tag and report with Quentin's ack
Reposted as v2 with the RFC tag removed and Quentin's ack added.
For future bpftool fixes during the merge window, would you prefer
regular bpf-next patches or RFCs?
Thanks,
Hungyu
next prev parent reply other threads:[~2026-10-30 20:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-30 9:09 Hungyu Lin
2026-10-30 10:26 ` Quentin Monnet
2026-10-30 19:46 ` Andrii Nakryiko
2026-10-30 20:00 ` Hungyu Lin [this message]
2026-10-30 20:02 ` Andrii Nakryiko
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=CAGEkeHcq7HeecPyTSYuHWMhCyOAbF7br+UjrFfLiQmgi6kTxhw@mail.gmail.com \
--to=dennylin0707@gmail.com \
--cc=andrii.nakryiko@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=linux-kernel@vger.kernel.org \
--cc=qmo@kernel.org \
/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
all inboxes | Powered by JetHome®