From: patchwork-bot+netdevbpf@kernel.org
To: RubenKelevra <rubenkelevra@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
edumazet@google.com, pabeni@redhat.com, horms@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2] net: pfcp: fix typo in message_priority field name
Date: Sat, 14 Jun 2025 01:20:33 +0000 [thread overview]
Message-ID: <174986403351.949218.16498839735634988981.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250612145012.185321-1-rubenkelevra@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 12 Jun 2025 16:50:12 +0200 you wrote:
> The field is spelled “message_priprity” in the big-endian bit-field
> definition. Nothing in-tree currently references the member, so the
> typo does not break kernel builds, but it is clearly incorrect and
> confuses out-of-tree code.
>
> Signed-off-by: RubenKelevra <rubenkelevra@gmail.com>
>
> [...]
Here is the summary with links:
- [net-next,v2] net: pfcp: fix typo in message_priority field name
https://git.kernel.org/netdev/net-next/c/b776999bf25d
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-06-14 1:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-10 16:06 [PATCH] net: pfcp: fix typo in message_priority field name RubenKelevra
2025-06-10 18:42 ` Charalampos Mitrodimas
2025-06-11 21:51 ` Jakub Kicinski
2025-06-12 6:38 ` Ruben Kelevra
2025-06-12 14:29 ` Jakub Kicinski
2025-06-12 14:50 ` [PATCH net-next v2] " RubenKelevra
2025-06-14 1: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=174986403351.949218.16498839735634988981.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rubenkelevra@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 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).