From: Jakub Kicinski <kuba@kernel.org>
To: Maxim Georgiev <glipus@gmail.com>
Cc: kory.maincent@bootlin.com, netdev@vger.kernel.org,
maxime.chevallier@bootlin.com, vladimir.oltean@nxp.com,
vadim.fedorenko@linux.dev, richardcochran@gmail.com,
gerhard@engleder-embedded.com
Subject: Re: [RFC PATCH v4 3/5] Add ndo_hwtstamp_get/set support to vlan/maxvlan code path
Date: Tue, 25 Apr 2023 08:58:54 -0700 [thread overview]
Message-ID: <20230425085854.1520d220@kernel.org> (raw)
In-Reply-To: <20230423032835.285406-1-glipus@gmail.com>
On Sat, 22 Apr 2023 21:28:35 -0600 Maxim Georgiev wrote:
> - if (!net_eq(dev_net(dev), &init_net))
> - break;
Did we agree that the net namespace check is no longer needed?
I don't see it anywhere after the changes.
next prev parent reply other threads:[~2023-04-25 15:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-23 3:28 [RFC PATCH v4 3/5] Add ndo_hwtstamp_get/set support to vlan/maxvlan code path Maxim Georgiev
2023-04-25 15:58 ` Jakub Kicinski [this message]
2023-04-26 4:43 ` Max Georgiev
2023-04-26 4:55 ` [RFC PATCH v5 " Maxim Georgiev
2023-04-27 2:37 ` [RFC PATCH v4 " Jakub Kicinski
2023-04-27 4:07 ` Max Georgiev
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=20230425085854.1520d220@kernel.org \
--to=kuba@kernel.org \
--cc=gerhard@engleder-embedded.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).