From: Peter Delevoryas <peter@pjd.dev>
To: unlisted-recipients:; (no To-header on input)
Cc: sam@mendozajonas.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, joel@jms.id.au,
gwshan@linux.vnet.ibm.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [net-next PATCH 0/1] net/ncsi: Fix netlink major/minor version numbers
Date: Thu, 2 Feb 2023 09:53:26 -0800 [thread overview]
Message-ID: <20230202175327.23429-1-peter@pjd.dev> (raw)
Background:
This fixes some nonsensical behavior with the NCSI version numbers that has
existed since the NCSI driver was introduced. Details in the commit message.
Functionally, this is only visible through the netlink interface, so I've
titled this commit as "fixing netlink".
But actually, the real reason I care about this is to provide a proper mechanism
for using the network card's NCSI version in the driver state machine.
With the major and minor versions parsed correctly here, the state machine can
decide to send NCSI 1.1 or 1.2 commands when the card supports it.
I submitted this patch previously[1] with two other changes, but that series
was ignored (wrong time to submit, invalid subject prefix, and the last patch
is controversial until hardware propagates).
I decided to just resubmit this first patch, since I think it's valuable on its
own. I'll follow up with the other ones later.
[1] https://lore.kernel.org/lkml/20221221052246.519674-1-peter@pjd.dev/
Implementation notes:
I found that "include/linux/bcd.h" doesn't actually do what we would want, so I
added a local static function. Perhaps I actually should have added that to
"include/linux/bcd.h" so other people can use it in the future? Let me know
what you guys think.
Thanks,
Peter
Peter Delevoryas (1):
net/ncsi: Fix netlink major/minor version numbers
net/ncsi/internal.h | 7 +++++--
net/ncsi/ncsi-netlink.c | 4 ++--
net/ncsi/ncsi-pkt.h | 7 +++++--
net/ncsi/ncsi-rsp.c | 26 ++++++++++++++++++++++++--
4 files changed, 36 insertions(+), 8 deletions(-)
--
2.30.2
next reply other threads:[~2023-02-02 17:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 17:53 Peter Delevoryas [this message]
2023-02-02 17:53 ` [net-next PATCH 1/1] net/ncsi: Fix netlink major/minor version numbers Peter Delevoryas
2023-02-04 9:19 ` Simon Horman
2023-02-07 8:21 ` Peter Delevoryas
2023-02-07 8:44 ` Simon Horman
2023-02-07 15:39 ` Peter Delevoryas
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=20230202175327.23429-1-peter@pjd.dev \
--to=peter@pjd.dev \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gwshan@linux.vnet.ibm.com \
--cc=joel@jms.id.au \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sam@mendozajonas.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).