From: Hariprasad Kelam <hkelam@marvell.com>
To: Carolina Jubran <cjubran@nvidia.com>
Cc: Michal Kubecek <mkubecek@suse.cz>,
"John W . Linville" <linville@tuxdriver.com>,
<netdev@vger.kernel.org>, Yael Chemla <ychemla@nvidia.com>
Subject: Re: [PATCH ethtool 1/2] update UAPI header copies
Date: Thu, 11 Dec 2025 18:54:33 +0530 [thread overview]
Message-ID: <aTrGEQIX6b40assX@test-OptiPlex-Tower-Plus-7010> (raw)
In-Reply-To: <20251204075930.979564-2-cjubran@nvidia.com>
On 2025-12-04 at 13:29:29, Carolina Jubran (cjubran@nvidia.com) wrote:
> From: Yael Chemla <ychemla@nvidia.com>
>
> Update to kernel commit 491c5dc98b84.
>
> Signed-off-by: Yael Chemla <ychemla@nvidia.com>
> Signed-off-by: Carolina Jubran <cjubran@nvidia.com>
> ---
> uapi/linux/ethtool.h | 6 ++++
> uapi/linux/ethtool_netlink_generated.h | 47 ++++++++++++++++++++++++++
> uapi/linux/if_ether.h | 2 ++
> uapi/linux/if_link.h | 3 ++
> uapi/linux/stddef.h | 1 -
> 5 files changed, 58 insertions(+), 1 deletion(-)
>
looks like there are no changes in "stddef.h", but its part of this patch.
Thanks,
Hariprasad k
next prev parent reply other threads:[~2025-12-11 13:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-04 7:59 [PATCH ethtool 0/2] ethtool: Add support for 1600G link modes Carolina Jubran
2025-12-04 7:59 ` [PATCH ethtool 1/2] update UAPI header copies Carolina Jubran
2025-12-11 13:24 ` Hariprasad Kelam [this message]
2025-12-11 13:41 ` Michal Kubecek
2025-12-04 7:59 ` [PATCH ethtool 2/2] ethtool: add new 1600G modes to link mode tables Carolina Jubran
2025-12-23 21:04 ` [PATCH ethtool 0/2] ethtool: Add support for 1600G link modes Carolina Jubran
-- strict thread matches above, loose matches on Subject: below --
2025-06-10 12:50 [PATCH ethtool 0/2] Add support for PTP hardware source Kory Maincent
2025-06-10 12:50 ` [PATCH ethtool 1/2] update UAPI header copies Kory Maincent
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=aTrGEQIX6b40assX@test-OptiPlex-Tower-Plus-7010 \
--to=hkelam@marvell.com \
--cc=cjubran@nvidia.com \
--cc=linville@tuxdriver.com \
--cc=mkubecek@suse.cz \
--cc=netdev@vger.kernel.org \
--cc=ychemla@nvidia.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).