From: Vladimir Oltean <vladimir.oltean@nxp.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Jacob Keller <jacob.e.keller@intel.com>,
netdev@vger.kernel.org, Tony Nguyen <anthony.l.nguyen@intel.com>,
Przemek Kitszel <przemyslaw.kitszel@intel.com>,
intel-wired-lan@lists.osuosl.org,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
Vadim Fedorenko <vadim.fedorenko@linux.dev>,
Richard Cochran <richardcochran@gmail.com>
Subject: Re: [PATCH net-next] ice: convert to ndo_hwtstamp_get() and ndo_hwtstamp_set()
Date: Tue, 13 May 2025 12:31:51 +0300 [thread overview]
Message-ID: <20250513093151.2ppznd3isu4xgpoa@skbuf> (raw)
In-Reply-To: <20250512171652.5bb0b0ee@kernel.org>
On Mon, May 12, 2025 at 05:16:52PM -0700, Jakub Kicinski wrote:
> On Mon, 12 May 2025 12:06:56 -0700 Jacob Keller wrote:
> > > Ok. I have 3 more Intel conversions pending (igb, ixgbe, i40e), but I've
> > > put a stop for today. I assume it's fine to post these to net-next and
> > > not to the iwl-next tree, or would you prefer otherwise?
> >
> > I think we typically prefer to go through iwl-next because that lets us
> > run a validation test pass. I have no personal objection if the netdev
> > maintainers want to take these directly.
>
> The real question is whether you can get these back to the list before
> Vladimir is done converting all drivers :) If yes - let's follow the
> usual path and take these via iwl. If Vladimir can convert faster than
> you can validate then we should take these direct..
I think I will be the limiting factor anyway. Let me send all Intel
conversions to iwl-next.
prev parent reply other threads:[~2025-05-13 9:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-12 16:00 [PATCH net-next] ice: convert to ndo_hwtstamp_get() and ndo_hwtstamp_set() Vladimir Oltean
2025-05-12 18:38 ` Jacob Keller
2025-05-12 18:53 ` Vladimir Oltean
2025-05-12 19:06 ` Jacob Keller
2025-05-13 0:16 ` Jakub Kicinski
2025-05-13 9:31 ` Vladimir Oltean [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=20250513093151.2ppznd3isu4xgpoa@skbuf \
--to=vladimir.oltean@nxp.com \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jacob.e.keller@intel.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.com \
--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