public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Vladimir Oltean <vladimir.oltean@nxp.com>
To: Max Georgiev <glipus@gmail.com>
Cc: Jakub Kicinski <kuba@kernel.org>,
	kory.maincent@bootlin.com, netdev@vger.kernel.org,
	maxime.chevallier@bootlin.com
Subject: Re: [PATCH net-next RFC] Add NDOs for hardware timestamp get/set
Date: Sun, 2 Apr 2023 19:56:56 +0300	[thread overview]
Message-ID: <20230402165656.h5v43cnxdsctkire@skbuf> (raw)
In-Reply-To: <CAP5jrPGtdTxt4UOg+pst2q0bxqwZgknO9V2sP4umh9G4PcPebg@mail.gmail.com>

On Sun, Apr 02, 2023 at 08:28:08AM -0600, Max Georgiev wrote:
> On Sat, Apr 1, 2023 at 2:18 PM Vladimir Oltean <vladimir.oltean@nxp.com> wrote:
> >
> > On Sat, Apr 01, 2023 at 12:24:50PM -0700, Jakub Kicinski wrote:
> > > It should be relatively easy to plumb both the ifr and the in-kernel
> > > config thru all the DSA APIs and have it call the right helper, too,
> > > tho? SMOC?
> >
> > Sorry, this does not compute.
> >
> > "Plumbing the in-kernel config thru all the DSA APIs" would be the
> > netdev notifier that I proposed one year ago. I just need you to say
> > "yes, sounds ok, let's see how that looks with last year's feedback
> > addressed".
> 
> I sent out a second iteration of the ndo_hwtstamp_get/set patch.
> I tried to address all the comments except fixing DSA API - I still
> don't have a full understanding of what is the plan there.

Well, my plan is for this patch set (to which you were copied before
sending out your v2) to be merged, then you could see what remains to be
done on top of that, and that should be easy-peasy:
https://patchwork.kernel.org/project/netdevbpf/cover/20230402123755.2592507-1-vladimir.oltean@nxp.com/

I think that patch set explains quite clearly what's with DSA's API and
what I intend it to become.

  reply	other threads:[~2023-04-02 16:57 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-31  4:56 [PATCH net-next RFC] Add NDOs for hardware timestamp get/set Maxim Georgiev
2023-03-31  5:35 ` Jakub Kicinski
2023-03-31 17:51   ` Max Georgiev
2023-03-31 18:10     ` Jakub Kicinski
2023-04-01 18:16       ` Vladimir Oltean
2023-04-01 19:12       ` Vladimir Oltean
2023-04-01 19:24         ` Jakub Kicinski
2023-04-01 19:30           ` Vladimir Oltean
2023-04-01 20:18           ` Vladimir Oltean
2023-04-02 14:28             ` Max Georgiev
2023-04-02 16:56               ` Vladimir Oltean [this message]
2023-04-01 16:08   ` Vladimir Oltean
2023-04-01 17:55     ` Jakub Kicinski
2023-04-01 18:20       ` Vladimir Oltean
2023-04-01 18:22         ` Vladimir Oltean
2023-04-01 19:14         ` Jakub Kicinski
2023-04-01 19:19           ` Vladimir Oltean

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=20230402165656.h5v43cnxdsctkire@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 \
    /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