From: Simon Horman <simon.horman@corigine•com>
To: Piotr Gardocki <piotrx.gardocki@intel•com>
Cc: netdev@vger•kernel.org, intel-wired-lan@lists•osuosl.org,
przemyslaw.kitszel@intel•com, michal.swiatkowski@linux•intel.com,
pmenzel@molgen•mpg.de, kuba@kernel•org,
maciej.fijalkowski@intel•com, anthony.l.nguyen@intel•com,
aleksander.lobakin@intel•com
Subject: Re: [PATCH net-next v3 0/3] optimize procedure of changing MAC address on interface
Date: Thu, 15 Jun 2023 09:31:20 +0200 [thread overview]
Message-ID: <ZIq+SMD6fdMU84Dg@corigine.com> (raw)
In-Reply-To: <20230614145302.902301-1-piotrx.gardocki@intel.com>
On Wed, Jun 14, 2023 at 04:52:59PM +0200, Piotr Gardocki wrote:
> The first patch adds an if statement in core to skip early when
> the MAC address is not being changes.
> The remaining patches remove such checks from Intel drivers
> as they're redundant at this point.
Hi Pitor,
I am wondering if you audited other drivers to see if they
could also be updated in a similar way to the Intel changes
in this patch-set.
next prev parent reply other threads:[~2023-06-15 7:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-14 14:52 [PATCH net-next v3 0/3] optimize procedure of changing MAC address on interface Piotr Gardocki
2023-06-14 14:53 ` [PATCH net-next v3 1/3] net: add check for current MAC address in dev_set_mac_address Piotr Gardocki
2023-06-15 11:34 ` Simon Horman
2023-06-14 14:53 ` [PATCH net-next v3 2/3] i40e: remove unnecessary check for old MAC == new MAC Piotr Gardocki
2023-06-15 11:34 ` Simon Horman
2023-06-14 14:53 ` [PATCH net-next v3 3/3] ice: " Piotr Gardocki
2023-06-15 11:34 ` Simon Horman
2023-06-14 15:50 ` [PATCH net-next v3 0/3] optimize procedure of changing MAC address on interface Maciej Fijalkowski
2023-06-14 15:52 ` Piotr Gardocki
2023-06-14 15:53 ` Maciej Fijalkowski
2023-06-15 7:31 ` Simon Horman [this message]
2023-06-15 8:51 ` Piotr Gardocki
2023-06-15 11:31 ` Simon Horman
2023-06-16 6:00 ` patchwork-bot+netdevbpf
2023-06-16 10:02 ` Fijalkowski, Maciej
2023-06-16 15:29 ` Jakub Kicinski
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=ZIq+SMD6fdMU84Dg@corigine.com \
--to=simon.horman@corigine$(echo .)com \
--cc=aleksander.lobakin@intel$(echo .)com \
--cc=anthony.l.nguyen@intel$(echo .)com \
--cc=intel-wired-lan@lists$(echo .)osuosl.org \
--cc=kuba@kernel$(echo .)org \
--cc=maciej.fijalkowski@intel$(echo .)com \
--cc=michal.swiatkowski@linux$(echo .)intel.com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=piotrx.gardocki@intel$(echo .)com \
--cc=pmenzel@molgen$(echo .)mpg.de \
--cc=przemyslaw.kitszel@intel$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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