All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: netdev@vger.kernel.org, donald.hunter@gmail.com, kuba@kernel.org,
	davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
	horms@kernel.org
Subject: Re: [PATCH net-next] tools: ynl: avoid "use of uninitialized variable" false positive in generated code
Date: Tue, 16 Sep 2025 15:38:04 +0000	[thread overview]
Message-ID: <175803708499.1166060.6121503858718992957.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250915144414.1185788-1-vladimir.oltean@nxp.com>

Hello:

This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Mon, 15 Sep 2025 17:44:14 +0300 you wrote:
> With indexed-array types such as "ops" from
> Documentation/netlink/specs/nlctrl.yaml, the generator creates code
> such as:
> 
> int nlctrl_getfamily_rsp_parse(const struct nlmsghdr *nlh,
> 			       struct ynl_parse_arg *yarg)
> {
> 	struct nlctrl_getfamily_rsp *dst;
> 	const struct nlattr *attr_ops;
> 	const struct nlattr *attr;
> 	struct ynl_parse_arg parg;
> 	unsigned int n_ops = 0;
> 	int i;
> 
> [...]

Here is the summary with links:
  - [net-next] tools: ynl: avoid "use of uninitialized variable" false positive in generated code
    https://git.kernel.org/netdev/net-next/c/a6824f65c996

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



      parent reply	other threads:[~2025-09-16 15:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-15 14:44 [PATCH net-next] tools: ynl: avoid "use of uninitialized variable" false positive in generated code Vladimir Oltean
2025-09-15 21:40 ` Jakub Kicinski
2025-09-16 15:38 ` 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=175803708499.1166060.6121503858718992957.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=donald.hunter@gmail.com \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=vladimir.oltean@nxp.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.