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,
Vadim Fedorenko <vadim.fedorenko@linux.dev>,
Richard Cochran <richardcochran@gmail.com>,
Gerhard Engleder <gerhard@engleder-embedded.com>
Subject: Re: [PATCH net-next RFC v2] Add NDOs for hardware timestamp get/set
Date: Wed, 5 Apr 2023 15:06:32 +0300 [thread overview]
Message-ID: <20230405120632.b7pfceyrtxwidyef@skbuf> (raw)
In-Reply-To: <CAP5jrPGwyyLMTNpriOA71sMH4fRAefV5Bbe=X=2v_ML9JJdwdw@mail.gmail.com>
On Wed, Apr 05, 2023 at 12:42:28AM -0600, Max Georgiev wrote:
> Thank you for the comments!
>
> I've sent out v3 of the RFC stack to let the comment flow, and to
> potentially unblock Köry.
> I've added patches to insert ifr pointer into struct
> kernel_hwtstamp_config as Jakub suggested, but no code is relying on
> this new field yet.
> I also added a patch which is supposed to fix the VLAN code path. I
> can implement ndo_hwtstamp_get/set in VLAN as well - please comment if
> it would be a good idea.
> I haven't fixed bond_eth_ioctl() yet - will add it in the next
> version. More driver conversion patches are planned as was discussed.
macvlan_eth_ioctl() needs changing too.
next prev parent reply other threads:[~2023-04-05 12:06 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 [this message]
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=20230405120632.b7pfceyrtxwidyef@skbuf \
--to=vladimir.oltean@nxp.com \
--cc=gerhard@engleder-embedded.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