All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: Max Georgiev <glipus@gmail.com>,
	kory.maincent@bootlin.com, 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 16:25:51 -0700	[thread overview]
Message-ID: <20230404162551.1d45d031@kernel.org> (raw)
In-Reply-To: <20230404123015.wzv5l5owgkppoarr@skbuf>

On Tue, 4 Apr 2023 15:30:15 +0300 Vladimir Oltean wrote:
> On Mon, Apr 03, 2023 at 09:42:09AM -0600, Max Georgiev wrote:
> > 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.

Alternatively we could have them call back to the core helper
to descend to a lower device. Stuff ifr into struct
kernel_hwtstamp_config for now in case lower is not converted.

  reply	other threads:[~2023-04-04 23:25 UTC|newest]

Thread overview: 16+ 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 16:01 ` kernel test robot
2023-04-02 16:33 ` kernel test robot
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 [this message]
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=20230404162551.1d45d031@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=richardcochran@gmail.com \
    --cc=vadim.fedorenko@linux.dev \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.