From: Jakub Kicinski <kuba@kernel.org>
To: Charalampos Mitrodimas <charmitro@posteo.net>
Cc: RubenKelevra <rubenkelevra@gmail.com>,
netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
pabeni@redhat.com, horms@kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] net: pfcp: fix typo in message_priority field name
Date: Wed, 11 Jun 2025 14:51:44 -0700 [thread overview]
Message-ID: <20250611145144.2bc0a7b7@kernel.org> (raw)
In-Reply-To: <87cybbzbe3.fsf@posteo.net>
On Tue, 10 Jun 2025 18:42:28 +0000 Charalampos Mitrodimas wrote:
> > 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>
>
> I had the same issue today, happy there's a patch for this.
Could y'all share more? What compilation does this break?
The field is never used.
More info about how you found the problem would be useful.
And I believe this can go to net-next, without the CC stable
and without the Fixes tag. Unless my grep is lying to me:
net-next$ git grep message_priority
include/net/pfcp.h: u8 message_priority:4,
--
pw-bot: cr
next prev parent reply other threads:[~2025-06-11 21:51 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 [this message]
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=20250611145144.2bc0a7b7@kernel.org \
--to=kuba@kernel.org \
--cc=charmitro@posteo.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rubenkelevra@gmail.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 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.