bpf.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Yucong Sun <fallentree@fb.com>
Cc: bpf@vger.kernel.org, andrii@kernel.org, sunyucong@gmail.com
Subject: Re: [PATCH bpf-next] tools/bpftool: Avoid using "?:" in generated code
Date: Tue, 28 Sep 2021 22:30:07 +0000	[thread overview]
Message-ID: <163286820718.3640.11148798241879130769.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210928184221.1545079-1-fallentree@fb.com>


This patch was applied to bpf/bpf-next.git (refs/heads/master):

On Tue, 28 Sep 2021 11:42:21 -0700 you wrote:
> "?:" is a GNU C extension, some environment has warning flags for its
> use, or even prohibit it directly.  This patch avoid triggering these
> problems by simply expand it to its full form, no functionality change.
> Signed-off-by: Yucong Sun <fallentree@fb.com>
> ---
>  tools/bpf/bpftool/gen.c | 5 ++++-
>  1 file changed, 4 insertions(+), 1 deletion(-)

Here is the summary with links:
  - [bpf-next] tools/bpftool: Avoid using "?:" in generated code

You are awesome, thank you!
Deet-doot-dot, I am a bot.

      reply	other threads:[~2021-09-28 22:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-28 18:42 [PATCH bpf-next] tools/bpftool: Avoid using "?:" in generated code Yucong Sun
2021-09-28 22: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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=163286820718.3640.11148798241879130769.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrii@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=fallentree@fb.com \
    --cc=sunyucong@gmail.com \


* 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).