From: Jakub Kicinski <kuba@kernel.org>
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: Maxim Georgiev <glipus@gmail.com>,
kory.maincent@bootlin.com, netdev@vger.kernel.org,
maxime.chevallier@bootlin.com
Subject: Re: [PATCH net-next RFC v2] Add NDOs for hardware timestamp get/set
Date: Mon, 3 Apr 2023 14:19:18 -0700 [thread overview]
Message-ID: <20230403141918.3257a195@kernel.org> (raw)
In-Reply-To: <20230403122622.ixpiy2o7irxb3xpp@skbuf>
On Mon, 3 Apr 2023 15:26:22 +0300 Vladimir Oltean wrote:
> > @@ -7365,6 +7364,8 @@ static const struct net_device_ops e1000e_netdev_ops = {
> > .ndo_set_features = e1000_set_features,
> > .ndo_fix_features = e1000_fix_features,
> > .ndo_features_check = passthru_features_check,
> > + .ndo_hwtstamp_get = e1000e_hwtstamp_get,
> > + .ndo_hwtstamp_set = e1000e_hwtstamp_set,
> > };
>
> The conversion per se looks almost in line with what I was expecting to
> see, except for the comments. I guess you can convert a single driver
> first (e1000 seems fine), to get the API merged, then more people could
> work in parallel?
>
> Or do you want netdevsim to cover hardware timestamping from the
> beginning too, Jakub?
I'd vote to split netdevsim out, and it needs a selftest which
exercises it under tools/testing/selftests/drivers/net/netdevsim/
to get merged...
next prev parent reply other threads:[~2023-04-03 21:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-02 14:24 [PATCH net-next RFC v2] Add NDOs for hardware timestamp get/set Maxim Georgiev
2023-04-02 18:23 ` Gerhard Engleder
2023-04-03 1:10 ` Max Georgiev
2023-04-03 12:26 ` Vladimir Oltean
2023-04-03 15:42 ` Max Georgiev
2023-04-03 17:18 ` Vadim Fedorenko
2023-04-04 7:57 ` Köry Maincent
2023-04-05 3:07 ` Max Georgiev
2023-04-04 12:30 ` Vladimir Oltean
2023-04-04 23:25 ` Jakub Kicinski
2023-04-05 6:42 ` Max Georgiev
2023-04-05 12:06 ` Vladimir Oltean
2023-04-03 21:19 ` Jakub Kicinski [this message]
2023-04-03 22:48 ` Richard Cochran
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=20230403141918.3257a195@kernel.org \
--to=kuba@kernel.org \
--cc=glipus@gmail.com \
--cc=kory.maincent@bootlin.com \
--cc=maxime.chevallier@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=vladimir.oltean@nxp.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).