From: kalavakunta.hari.prasad@gmail.com
To: sam@mendozajonas.com, fercerpav@gmail.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: npeacock@meta.com, akozlov@meta.com,
Hari Kalavakunta <kalavakunta.hari.prasad@gmail.com>
Subject: [PATCH net-next 0/2] GCPS Spec Compliance Patch Set
Date: Mon, 7 Apr 2025 11:19:47 -0700 [thread overview]
Message-ID: <cover.1744048182.git.kalavakunta.hari.prasad@gmail.com> (raw)
From: Hari Kalavakunta <kalavakunta.hari.prasad@gmail.com>
Make Get Controller Packet Statistics (GCPS) 64-bit member variables
spec-compliant, as per DSP0222 v1.0.0 and forward specs
Hari Kalavakunta (2):
net: ncsi: Format structure for longer names
net: ncsi: Fix GCPS 64-bit member variables
net/ncsi/internal.h | 21 +++++-----
net/ncsi/ncsi-pkt.h | 95 +++++++++++++++++++++++++--------------------
net/ncsi/ncsi-rsp.c | 31 +++++++++------
3 files changed, 82 insertions(+), 65 deletions(-)
--
2.47.1
next reply other threads:[~2025-04-07 18:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-07 18:19 kalavakunta.hari.prasad [this message]
2025-04-07 18:19 ` [PATCH net-next 1/2] net: ncsi: Format structure for longer names kalavakunta.hari.prasad
2025-04-07 18:19 ` [PATCH net-next 2/2] net: ncsi: Fix GCPS 64-bit member variables kalavakunta.hari.prasad
2025-04-07 22:23 ` Paul Fertser
2025-04-07 21:44 ` [PATCH net-next 0/2] GCPS Spec Compliance Patch Set Sam Mendoza-Jonas
2025-04-08 17:01 ` Hari Kalavakunta
2025-04-08 18:26 ` Paul Fertser
2025-04-08 18:53 ` Hari Kalavakunta
2025-04-08 19:19 ` Paul Fertser
2025-04-08 22:02 ` Hari Kalavakunta
2025-04-08 22:35 ` Paul Fertser
2025-04-08 23:23 ` Hari Kalavakunta
2025-04-09 3:27 ` Hari Kalavakunta
2025-04-09 9:08 ` Paul Fertser
2025-04-09 16:39 ` Hari Kalavakunta
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=cover.1744048182.git.kalavakunta.hari.prasad@gmail.com \
--to=kalavakunta.hari.prasad@gmail.com \
--cc=akozlov@meta.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fercerpav@gmail.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=npeacock@meta.com \
--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).