public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: WanLi Niu <kiraskyler@163.com>
Cc: qmo@kernel.org, andrii.nakryiko@gmail.com,
	jose.marchesi@oracle.com, ast@kernel.org, daniel@iogearbox.net,
	andrii@kernel.org, martin.lau@linux.dev, eddyz87@gmail.com,
	song@kernel.org, yonghong.song@linux.dev,
	john.fastabend@gmail.com, kpsingh@kernel.org, sdf@fomichev.me,
	haoluo@google.com, jolsa@kernel.org, menglong8.dong@gmail.com,
	bpf@vger.kernel.org, linux-kernel@vger.kernel.org,
	niuwl1@chinatelecom.cn, dongml2@chinatelecom.cn
Subject: Re: [PATCH v5 bpf-next] bpftool: Make skeleton C++ compatible with explicit casts
Date: Fri, 09 Jan 2026 19:00:06 +0000	[thread overview]
Message-ID: <176798520655.368147.17396600775278527236.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260106023123.2928-1-kiraskyler@163.com>

Hello:

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

On Tue,  6 Jan 2026 10:31:23 +0800 you wrote:
> From: WanLi Niu <niuwl1@chinatelecom.cn>
> 
> Fix C++ compilation errors in generated skeleton by adding explicit
> pointer casts and use char * subtraction for offset calculation
> 
> error: invalid conversion from 'void*' to '<obj_name>*' [-fpermissive]
>       |         skel = skel_alloc(sizeof(*skel));
>       |                ~~~~~~~~~~^~~~~~~~~~~~~~~
>       |                          |
>       |                          void*
> 
> [...]

Here is the summary with links:
  - [v5,bpf-next] bpftool: Make skeleton C++ compatible with explicit casts
    https://git.kernel.org/bpf/bpf-next/c/4effccde0a05

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



  reply	other threads:[~2026-01-09 19:03 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-31  9:25 [PATCH bpf-next] bpftool: Make skeleton C++ compatible with explicit casts WanLi Niu
2025-12-31  9:48 ` bot+bpf-ci
2025-12-31 10:29 ` [PATCH v2 " WanLi Niu
2026-01-02 19:35   ` Yonghong Song
2026-01-04  2:14   ` [PATCH v3 " WanLi Niu
2026-01-05  5:27     ` Yonghong Song
2026-01-05  7:12     ` [PATCH v4 " WanLi Niu
2026-01-05 10:39       ` Quentin Monnet
2026-01-05 11:50       ` Jose E. Marchesi
2026-01-05 12:53         ` WanLi Niu
2026-01-05 16:05           ` Jose E. Marchesi
2026-01-06  2:31       ` [PATCH v5 " WanLi Niu
2026-01-09 19:00         ` patchwork-bot+netdevbpf [this message]
2026-01-06  0:46     ` [PATCH v3 " Andrii Nakryiko

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=176798520655.368147.17396600775278527236.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrii.nakryiko@gmail.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=dongml2@chinatelecom.cn \
    --cc=eddyz87@gmail.com \
    --cc=haoluo@google.com \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=jose.marchesi@oracle.com \
    --cc=kiraskyler@163.com \
    --cc=kpsingh@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=menglong8.dong@gmail.com \
    --cc=niuwl1@chinatelecom.cn \
    --cc=qmo@kernel.org \
    --cc=sdf@fomichev.me \
    --cc=song@kernel.org \
    --cc=yonghong.song@linux.dev \
    /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