From: Nick Alcock <nick.alcock@oracle.com>
To: Kris Van Hees <kris.van.hees@oracle.com>
Cc: dtrace@lists.linux.dev, dtrace-devel@oss.oracle.com
Subject: Re: [PATCH] bpf: be less picky about the content of bpf_helper_defs.h
Date: Mon, 06 May 2024 20:10:39 +0100 [thread overview]
Message-ID: <87wmo6iwnk.fsf@esperi.org.uk> (raw)
In-Reply-To: <SN7PR10MB62872FF9878DAAEE6F33AFD3C21C2@SN7PR10MB6287.namprd10.prod.outlook.com> (Kris Van Hees's message of "Mon, 06 May 2024 15:05:26 -0400")
On 6 May 2024, Kris Van Hees verbalised:
> There are small differences in the format of the BPF helper definitions
> in bpf_helper_defs.h in libbpf headers. This patch allows mkHelpers to
> be more accepting of these differences.
... looks like it does that to me, and just as importantly doesn't emit
rubbish if the match fails.
> Signed-off-by: Kris Van Hees <kris.van.hees@oracle.com>
Reviewed-by: Nick Alcock <nick.alcock@oracle.com>
next prev parent reply other threads:[~2024-05-06 19:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-06 19:05 [PATCH] bpf: be less picky about the content of bpf_helper_defs.h Kris Van Hees
2024-05-06 19:10 ` Nick Alcock [this message]
2024-05-06 19:43 ` Eugene Loh
2024-05-06 20:33 ` Kris Van Hees
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=87wmo6iwnk.fsf@esperi.org.uk \
--to=nick.alcock@oracle.com \
--cc=dtrace-devel@oss.oracle.com \
--cc=dtrace@lists.linux.dev \
--cc=kris.van.hees@oracle.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