All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
	pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org,
	donald.hunter@gmail.com, johannes@sipsolutions.net, fw@strlen.de,
	pablo@netfilter.org
Subject: Re: [PATCH net-next v2] netlink: policy: report the big endian attributes
Date: Wed, 16 Sep 2026 00:10:12 +0000	[thread overview]
Message-ID: <178951741263.2328807.1084523593940033347.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260912202401.141336-1-kuba@kernel.org>

Hello:

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

On Sat, 12 Sep 2026 13:24:01 -0700 you wrote:
> Paolo pointed out an issue flagged at low priority by Sashiko -
> we're currently not handling BE{16,32} attributes in policy dumps.
> 
> Commit 3f4285d741b4 ("netlink: specs: fou: local-v4 and peer-v4 are big
> endian") flipped two fou attributes from NLA_U32 to NLA_BE32.
> This made them vanish from the policy dump.
> 
> [...]

Here is the summary with links:
  - [net-next,v2] netlink: policy: report the big endian attributes
    https://git.kernel.org/netdev/net-next/c/b785f5c56fb3

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



      reply	other threads:[~2026-09-16  0:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-12 20:24 [PATCH net-next v2] netlink: policy: report the big endian attributes Jakub Kicinski
2026-09-16  0:10 ` 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=178951741263.2328807.1084523593940033347.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=donald.hunter@gmail.com \
    --cc=edumazet@google.com \
    --cc=fw@strlen.de \
    --cc=horms@kernel.org \
    --cc=johannes@sipsolutions.net \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=pablo@netfilter.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 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.