From: Yonghong Song <yonghong.song@linux.dev>
To: Will Hawkins <hawkinsw@obs.cr>, bpf@vger.kernel.org, bpf@ietf.org
Subject: Re: [PATCH v2] docs/bpf: Add constant values for linkages
Date: Wed, 11 Sep 2024 07:30:04 -0700 [thread overview]
Message-ID: <eb09643f-0be7-476c-bc9c-067fc38d3637@linux.dev> (raw)
In-Reply-To: <20240911055033.2084881-1-hawkinsw@obs.cr>
On 9/10/24 10:50 PM, Will Hawkins wrote:
> Make the values of the symbolic constants that define the valid linkages
> for functions and variables explicit.
>
> Signed-off-by: Will Hawkins <hawkinsw@obs.cr>
LGTM. Thanks!
Acked-by: Yonghong Song <yonghong.song@linux.dev>
WARNING: multiple messages have this Message-ID (diff)
From: Yonghong Song <yonghong.song@linux.dev>
To: Will Hawkins <hawkinsw@obs.cr>, bpf@vger.kernel.org, bpf@ietf.org
Subject: [Bpf] Re: [PATCH v2] docs/bpf: Add constant values for linkages
Date: Wed, 11 Sep 2024 07:30:04 -0700 [thread overview]
Message-ID: <eb09643f-0be7-476c-bc9c-067fc38d3637@linux.dev> (raw)
Message-ID: <20240911143004.9aRJ5dxGcWw4AlrYvzgBT7qubFNIBRMotXn7C_B1-G8@z> (raw)
In-Reply-To: <20240911055033.2084881-1-hawkinsw@obs.cr>
On 9/10/24 10:50 PM, Will Hawkins wrote:
> Make the values of the symbolic constants that define the valid linkages
> for functions and variables explicit.
>
> Signed-off-by: Will Hawkins <hawkinsw@obs.cr>
LGTM. Thanks!
Acked-by: Yonghong Song <yonghong.song@linux.dev>
--
Bpf mailing list -- bpf@ietf.org
To unsubscribe send an email to bpf-leave@ietf.org
next prev parent reply other threads:[~2024-09-11 14:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-11 5:50 [PATCH v2] docs/bpf: Add constant values for linkages Will Hawkins
2024-09-11 5:50 ` [Bpf] " Will Hawkins
2024-09-11 14:30 ` Yonghong Song [this message]
2024-09-11 14:30 ` [Bpf] " Yonghong Song
2024-09-11 20:50 ` patchwork-bot+netdevbpf
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=eb09643f-0be7-476c-bc9c-067fc38d3637@linux.dev \
--to=yonghong.song@linux.dev \
--cc=bpf@ietf.org \
--cc=bpf@vger.kernel.org \
--cc=hawkinsw@obs.cr \
/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