From: "Köry Maincent" <kory.maincent@bootlin.com>
To: Max Georgiev <glipus@gmail.com>
Cc: Vladimir Oltean <vladimir.oltean@nxp.com>,
kuba@kernel.org, netdev@vger.kernel.org,
maxime.chevallier@bootlin.com, vadim.fedorenko@linux.dev,
richardcochran@gmail.com, gerhard@engleder-embedded.com
Subject: Re: [RFC PATCH v3 1/5] Add NDOs for hardware timestamp get/set
Date: Fri, 21 Apr 2023 15:03:44 +0200 [thread overview]
Message-ID: <20230421150344.278bece3@kmaincent-XPS-13-7390> (raw)
In-Reply-To: <CAP5jrPFytnMku6TQNFQGBh4-=mL0z3XVq7ofY1z3LPYMP7_G0Q@mail.gmail.com>
On Thu, 20 Apr 2023 12:04:06 -0600
Max Georgiev <glipus@gmail.com> wrote:
> I've updated the patches in the stack based on the feedback you folks
> kindly shared
> for v3. I'm currently testing the combination of the changes in
> dev_ioctl.c and netdevsim
> driver changes - almost done with that. Let me finish this testing,
> then update the patch
> descriptions, and I'll be ready to send it out for review.
>
> Regarding e1000e conversion patch: I don't have access to any NICs
> with hw timestamping
> support. I was going to drop the e1000e patch from v4 unless someone
> volunteered to test it on real hardware. But that will have to wait till the
> rest of the stack is reviewed and
> at least preliminary accepted, right?
Great, thanks for the status.
Indeed, if no one raise its hand to test the e1000e conversion you can drop it.
prev parent reply other threads:[~2023-04-21 13:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-05 6:31 [RFC PATCH v3 1/5] Add NDOs for hardware timestamp get/set Maxim Georgiev
2023-04-05 12:31 ` Vladimir Oltean
2023-04-05 15:54 ` Max Georgiev
2023-04-20 14:16 ` Köry Maincent
2023-04-20 18:04 ` Max Georgiev
2023-04-21 13:03 ` Köry Maincent [this message]
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=20230421150344.278bece3@kmaincent-XPS-13-7390 \
--to=kory.maincent@bootlin.com \
--cc=gerhard@engleder-embedded.com \
--cc=glipus@gmail.com \
--cc=kuba@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox