All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Varun R Mallya <varunrmallya@gmail.com>
Cc: andrii@kernel.org, eddyz87@gmail.com, toke@redhat.com,
	ast@kernel.org, daniel@iogearbox.net, song@kernel.org,
	bpf@vger.kernel.org, linux-kselftest@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next] selftests/bpf: Fix const qualifier warning in fexit_bpf2bpf.c
Date: Wed, 11 Mar 2026 18:20:06 +0000	[thread overview]
Message-ID: <177325320607.3779062.5511337420258180281.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260305222132.470700-1-varunrmallya@gmail.com>

Hello:

This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:

On Fri,  6 Mar 2026 03:51:32 +0530 you wrote:
> Building selftests with
> clang 23.0.0 (6fae863eba8a72cdd82f37e7111a46a70be525e0) triggers
> the following error:
> 
>   tools/testing/selftests/bpf/prog_tests/fexit_bpf2bpf.c:117:12:
>   error: assigning to 'char *' from 'const char *' discards qualifiers
>   [-Werror,-Wincompatible-pointer-types-discards-qualifiers]
> 
> [...]

Here is the summary with links:
  - [bpf-next] selftests/bpf: Fix const qualifier warning in fexit_bpf2bpf.c
    https://git.kernel.org/bpf/bpf-next/c/ca0f39a369c5

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-03-11 18:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-05 22:21 [PATCH bpf-next] selftests/bpf: Fix const qualifier warning in fexit_bpf2bpf.c Varun R Mallya
2026-03-06  1:16 ` Menglong Dong
2026-03-06  1:40   ` Alexei Starovoitov
2026-03-06  2:26     ` Alexei Starovoitov
2026-03-06  2:47       ` Menglong Dong
2026-03-06 12:11 ` Varun R Mallya
2026-03-11 18:20 ` 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:
  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=177325320607.3779062.5511337420258180281.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=song@kernel.org \
    --cc=toke@redhat.com \
    --cc=varunrmallya@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.