From: Vladimir Oltean <vladimir.oltean@nxp.com>
To: Max Georgiev <glipus@gmail.com>
Cc: kory.maincent@bootlin.com, kuba@kernel.org,
netdev@vger.kernel.org, maxime.chevallier@bootlin.com,
Vadim Fedorenko <vadim.fedorenko@linux.dev>,
Richard Cochran <richardcochran@gmail.com>
Subject: Re: [PATCH net-next RFC v2] Add NDOs for hardware timestamp get/set
Date: Tue, 4 Apr 2023 15:30:15 +0300 [thread overview]
Message-ID: <20230404123015.wzv5l5owgkppoarr@skbuf> (raw)
In-Reply-To: <CAP5jrPExLX5nF7BWSSc1LeE_HOSWsDNLiGB52U0dzxfXFKb+Lw@mail.gmail.com> <CAP5jrPExLX5nF7BWSSc1LeE_HOSWsDNLiGB52U0dzxfXFKb+Lw@mail.gmail.com>
On Mon, Apr 03, 2023 at 09:42:09AM -0600, Max Georgiev wrote:
> > 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?
>
> The conversions are going to be easy (that was the point of adding these NDO
> functions). But there is still a problem of validating these
> conversions with testing.
> Unfortunately I don't have an e1000 card available to validate this conversion.
> I'll let you and Jakub decide what will be the best strategy here.
If you can convert one of the drivers under drivers/net/ethernet/freescale/
with the exception of fec_main.c, or net/dsa/ + drivers/net/dsa/sja1105/
or drivers/net/dsa/mv88e6xxx/, then I can help with testing.
By the way, after inspecting the kernel code a bit more, it also looks
like we need to convert vlan_dev_ioctl() and bond_eth_ioctl() to
something compatible with lower interfaces using the new and the old
API, before converting any driver. Otherwise we'll need to do that later
anyway, when regression reports start coming in. So these 2 are
non-optional whatever you do.
next prev parent reply other threads:[~2023-04-04 12:30 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 [this message]
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
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=20230404123015.wzv5l5owgkppoarr@skbuf \
--to=vladimir.oltean@nxp.com \
--cc=glipus@gmail.com \
--cc=kory.maincent@bootlin.com \
--cc=kuba@kernel.org \
--cc=maxime.chevallier@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.com \
--cc=vadim.fedorenko@linux.dev \
/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