All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Maciej Fijalkowski <maciej.fijalkowski@intel.com>,
	Piotr Gardocki <piotrx.gardocki@intel.com>
Cc: Tony Nguyen <anthony.l.nguyen@intel.com>, <davem@davemloft.net>,
	<pabeni@redhat.com>, <edumazet@google.com>,
	<netdev@vger.kernel.org>,
	Michal Swiatkowski <michal.swiatkowski@linux.intel.com>,
	Rafal Romanowski <rafal.romanowski@intel.com>,
	<aleksander.lobakin@intel.com>
Subject: Re: [PATCH net-next 1/3] iavf: add check for current MAC address in set_mac callback
Date: Tue, 6 Jun 2023 10:24:30 -0700	[thread overview]
Message-ID: <20230606102430.294dee2f@kernel.org> (raw)
In-Reply-To: <ZH8Ik3XyOzd28ao2@boxer>

On Tue, 6 Jun 2023 12:21:07 +0200 Maciej Fijalkowski wrote:
> > > couldn't this be checked the layer above then? and pulled out of drivers?
> > 
> > Probably it could, but I can't tell for all drivers if such request should
> > always be ignored. I'm not aware of all possible use cases for this callback
> > to be called and I can imagine designs where such request should be
> > always handled.  
> 
> if you can imagine a case where such request should be handled then i'm
> all ears. it feels like this is in an optimization where everyone could
> benefit from (no expert in this scope though), but yeah this callback went
> into the wild and it's implemented all over the place.

+1, FWIW, this is a net-next change, let's try to put it in the core
unless we see a clear enough reason not to.

  parent reply	other threads:[~2023-06-06 17:24 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-02 17:12 [PATCH net-next 0/3][pull request] Intel Wired LAN Driver Updates 2023-06-02 (iavf) Tony Nguyen
2023-06-02 17:13 ` [PATCH net-next 1/3] iavf: add check for current MAC address in set_mac callback Tony Nguyen
2023-06-03 14:06   ` Simon Horman
2023-06-05 19:02   ` Maciej Fijalkowski
2023-06-06  9:22     ` Piotr Gardocki
2023-06-06 10:21       ` Maciej Fijalkowski
2023-06-06 12:54         ` Alexander Lobakin
2023-06-06 17:24         ` Jakub Kicinski [this message]
2023-06-07 10:29           ` Piotr Gardocki
2023-06-07 16:38             ` Jakub Kicinski
2023-06-07 20:22               ` Maciej Fijalkowski
2023-06-02 17:13 ` [PATCH net-next 2/3] iavf: fix err handling for MAC replace Tony Nguyen
2023-06-03 14:07   ` Simon Horman
2023-06-05 19:17   ` Maciej Fijalkowski
2023-06-06 10:14     ` Przemek Kitszel
2023-06-06 10:23       ` Maciej Fijalkowski
2023-06-06 11:59         ` Przemek Kitszel
2023-06-07 13:57       ` Przemek Kitszel
2023-06-07 19:08         ` Fijalkowski, Maciej
2023-06-16  7:09           ` Przemek Kitszel
2023-06-16 17:13             ` Tony Nguyen
2023-06-02 17:13 ` [PATCH net-next 3/3] iavf: remove mask from iavf_irq_enable_queues() Tony Nguyen
2023-06-03 14:07   ` Simon Horman
2023-06-05 19:25   ` Maciej Fijalkowski
2023-06-05 19:56     ` Ahmed Zaki
2023-06-06 10:26       ` Maciej Fijalkowski
2023-06-06 15:23         ` Ahmed Zaki
2023-06-06 16:01           ` Romanowski, Rafal

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=20230606102430.294dee2f@kernel.org \
    --to=kuba@kernel.org \
    --cc=aleksander.lobakin@intel.com \
    --cc=anthony.l.nguyen@intel.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=maciej.fijalkowski@intel.com \
    --cc=michal.swiatkowski@linux.intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=piotrx.gardocki@intel.com \
    --cc=rafal.romanowski@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.