From: Stephen Hemminger <stephen@networkplumber.org>
To: Max Tottenham <mtottenh@akamai.com>
Cc: <netdev@vger.kernel.org>, <johunt@akamai.com>
Subject: Re: [RFC PATCH iproute2] Add ability to specify eBPF pin path
Date: Wed, 3 May 2023 11:51:23 -0700 [thread overview]
Message-ID: <20230503115123.13a1c077@hermes.local> (raw)
In-Reply-To: <20230503173348.703437-2-mtottenh@akamai.com>
On Wed, 3 May 2023 13:33:49 -0400
Max Tottenham <mtottenh@akamai.com> wrote:
> diff --git a/tc/f_bpf.c b/tc/f_bpf.c
> index a6d4875f..4eb3e817 100644
> --- a/tc/f_bpf.c
> +++ b/tc/f_bpf.c
> @@ -28,7 +28,7 @@ static void explain(void)
> "\n"
> "eBPF use case:\n"
> " object-file FILE [ section CLS_NAME ] [ export UDS_FILE ]"
> - " [ verbose ] [ direct-action ] [ skip_hw | skip_sw ]\n"
> + " [ verbose ] [ direct-action ] [ skip_hw | skip_sw ] [pin_path PATH]\n"
Help text should match other options.
You need to update man page man/man8/tc-bpf.8 as well.
next prev parent reply other threads:[~2023-05-03 18:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-03 17:33 [RFC PATCH iproute2] Add ability to specify eBPF pin path Max Tottenham
2023-05-03 17:33 ` Max Tottenham
2023-05-03 18:50 ` Stephen Hemminger
2023-05-03 18:51 ` Stephen Hemminger [this message]
2023-05-26 15:09 ` [RFC PATCH v2 iproute2 0/1] Add ability to specify eBPF map " Max Tottenham
2023-05-26 15:09 ` [RFC PATCH v2 iproute2 1/1] tc/f_bpf.c: " Max Tottenham
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=20230503115123.13a1c077@hermes.local \
--to=stephen@networkplumber.org \
--cc=johunt@akamai.com \
--cc=mtottenh@akamai.com \
--cc=netdev@vger.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;
as well as URLs for NNTP newsgroup(s).