From: Jakub Kicinski <kuba@kernel.org>
To: Vadim Fedorenko <vadim.fedorenko@linux.dev>
Cc: "Jian Shen" <shenjian15@huawei.com>,
"Salil Mehta" <salil.mehta@huawei.com>,
"Jijie Shao" <shaojijie@huawei.com>,
"Andrew Lunn" <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Paolo Abeni" <pabeni@redhat.com>,
"Sunil Goutham" <sgoutham@marvell.com>,
"Geetha sowjanya" <gakula@marvell.com>,
"Subbaraya Sundeep" <sbhatta@marvell.com>,
"Bharat Bhushan" <bbhushan2@marvell.com>,
"Tariq Toukan" <tariqt@nvidia.com>,
"Brett Creeley" <brett.creeley@amd.com>,
"Niklas Söderlund" <niklas.soderlund@ragnatech.se>,
"Paul Barker" <paul@pbarker.dev>,
"Yoshihiro Shimoda" <yoshihiro.shimoda.uh@renesas.com>,
linux-renesas-soc@vger.kernel.org,
"Richard Cochran" <richardcochran@gmail.com>,
"Russell King" <linux@armlinux.org.uk>,
"Vladimir Oltean" <vladimir.oltean@nxp.com>,
"Simon Horman" <horms@kernel.org>,
"Jacob Keller" <jacob.e.keller@intel.com>,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next v2 1/6] octeontx2: convert to ndo_hwtstamp API
Date: Mon, 20 Oct 2025 18:45:37 -0700 [thread overview]
Message-ID: <20251020184537.711e3ebc@kernel.org> (raw)
In-Reply-To: <20251017182128.895687-2-vadim.fedorenko@linux.dev>
On Fri, 17 Oct 2025 18:21:23 +0000 Vadim Fedorenko wrote:
> + if (!test_bit(CN10K_PTP_ONESTEP, &pfvf->hw.cap_flag)) {
> + NL_SET_ERR_MSG(extack,
> + "One-step time stamping is not supported");
> return -ERANGE;
> + }
You're adding quite a few extacks in this series.
Drivers should generally used the _MOD() flavor of the extack helpers
--
pw-bot: cr
next prev parent reply other threads:[~2025-10-21 1:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-17 18:21 [PATCH net-next v2 0/6] convert net drivers to ndo_hwtstamp API part 2 Vadim Fedorenko
2025-10-17 18:21 ` [PATCH net-next v2 1/6] octeontx2: convert to ndo_hwtstamp API Vadim Fedorenko
2025-10-21 1:45 ` Jakub Kicinski [this message]
2025-10-17 18:21 ` [PATCH net-next v2 2/6] mlx4: " Vadim Fedorenko
2025-10-20 10:11 ` Tariq Toukan
2025-10-20 10:15 ` Vadim Fedorenko
2025-10-17 18:21 ` [PATCH net-next v2 3/6] ionic: " Vadim Fedorenko
2025-10-17 18:21 ` [PATCH net-next v2 4/6] net: ravb: " Vadim Fedorenko
2025-10-17 18:21 ` [PATCH net-next v2 5/6] net: renesas: rswitch: " Vadim Fedorenko
2025-10-17 18:21 ` [PATCH net-next v2 6/6] net: hns3: add hwtstamp_get/hwtstamp_set ops Vadim Fedorenko
2025-10-20 2:00 ` Jijie Shao
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=20251020184537.711e3ebc@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=bbhushan2@marvell.com \
--cc=brett.creeley@amd.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gakula@marvell.com \
--cc=horms@kernel.org \
--cc=jacob.e.keller@intel.com \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=niklas.soderlund@ragnatech.se \
--cc=pabeni@redhat.com \
--cc=paul@pbarker.dev \
--cc=richardcochran@gmail.com \
--cc=salil.mehta@huawei.com \
--cc=sbhatta@marvell.com \
--cc=sgoutham@marvell.com \
--cc=shaojijie@huawei.com \
--cc=shenjian15@huawei.com \
--cc=tariqt@nvidia.com \
--cc=vadim.fedorenko@linux.dev \
--cc=vladimir.oltean@nxp.com \
--cc=yoshihiro.shimoda.uh@renesas.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).