From: RubenKelevra <rubenkelevra@gmail.com>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, kuba@kernel.org, edumazet@google.com,
pabeni@redhat.com, horms@kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
RubenKelevra <rubenkelevra@gmail.com>
Subject: [PATCH] net: pfcp: fix typo in message_priority field name
Date: Tue, 10 Jun 2025 18:06:12 +0200 [thread overview]
Message-ID: <20250610160612.268612-1-rubenkelevra@gmail.com> (raw)
Fix 'message_priprity' typo to 'message_priority' in big endian
bitfield definition. This typo breaks compilation on big endian
architectures.
Fixes: 6dd514f48110 ("pfcp: always set pfcp metadata")
Cc: stable@vger.kernel.org # commit 6dd514f48110 ("pfcp: always set pfcp metadata")
Signed-off-by: RubenKelevra <rubenkelevra@gmail.com>
---
include/net/pfcp.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/net/pfcp.h b/include/net/pfcp.h
index af14f970b80e1..639553797d3e4 100644
--- a/include/net/pfcp.h
+++ b/include/net/pfcp.h
@@ -45,7 +45,7 @@ struct pfcphdr_session {
reserved:4;
#elif defined(__BIG_ENDIAN_BITFIELD)
u8 reserved:4,
- message_priprity:4;
+ message_priority:4;
#else
#error "Please fix <asm/byteorder>"
#endif
--
2.49.0
next reply other threads:[~2025-06-10 16:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-10 16:06 RubenKelevra [this message]
2025-06-10 18:42 ` [PATCH] net: pfcp: fix typo in message_priority field name 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
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=20250610160612.268612-1-rubenkelevra@gmail.com \
--to=rubenkelevra@gmail.com \
--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=stable@vger.kernel.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 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).