From: Jakub Kicinski <kuba@kernel.org>
To: "Fijalkowski, Maciej" <maciej.fijalkowski@intel.com>
Cc: "patchwork-bot+netdevbpf@kernel.org"
<patchwork-bot+netdevbpf@kernel.org>,
"Gardocki, PiotrX" <piotrx.gardocki@intel.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"intel-wired-lan@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>,
"Kitszel, Przemyslaw" <przemyslaw.kitszel@intel.com>,
"michal.swiatkowski@linux.intel.com"
<michal.swiatkowski@linux.intel.com>,
"pmenzel@molgen.mpg.de" <pmenzel@molgen.mpg.de>,
"Nguyen, Anthony L" <anthony.l.nguyen@intel.com>,
"simon.horman@corigine.com" <simon.horman@corigine.com>,
"Lobakin, Aleksander" <aleksander.lobakin@intel.com>
Subject: Re: [PATCH net-next v3 0/3] optimize procedure of changing MAC address on interface
Date: Fri, 16 Jun 2023 08:29:31 -0700 [thread overview]
Message-ID: <20230616082931.4d265f51@kernel.org> (raw)
In-Reply-To: <DM4PR11MB6117E6A199A2CEF4694A6E0C8258A@DM4PR11MB6117.namprd11.prod.outlook.com>
On Fri, 16 Jun 2023 10:02:12 +0000 Fijalkowski, Maciej wrote:
> > Here is the summary with links:
> > - [net-next,v3,1/3] net: add check for current MAC address in dev_set_mac_address
> > https://git.kernel.org/netdev/net-next/c/ad72c4a06acc
> > - [net-next,v3,2/3] i40e: remove unnecessary check for old MAC == new MAC
> > https://git.kernel.org/netdev/net-next/c/c45a6d1a23c5
> > - [net-next,v3,3/3] ice: remove unnecessary check for old MAC == new MAC
> > https://git.kernel.org/netdev/net-next/c/96868cca7971
>
> Ah, so next time I will respond to each revision with rev-by tags 😉
I may have done this slightly out of spite :P
You tell the man that he didn't keep your R-b tag, why not throw it in
again in one of your responses? It's bit of a PITA for me to add it
manually. One tag in reply to the cover letter is enough FWIW (at least
on netdev, I explained to BPF folks how to get the tag propagation
from cover letter to work but I'm not 100% sure they set it up for
themselves).
prev parent reply other threads:[~2023-06-16 15:29 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
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 [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=20230616082931.4d265f51@kernel.org \
--to=kuba@kernel.org \
--cc=aleksander.lobakin@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=maciej.fijalkowski@intel.com \
--cc=michal.swiatkowski@linux.intel.com \
--cc=netdev@vger.kernel.org \
--cc=patchwork-bot+netdevbpf@kernel.org \
--cc=piotrx.gardocki@intel.com \
--cc=pmenzel@molgen.mpg.de \
--cc=przemyslaw.kitszel@intel.com \
--cc=simon.horman@corigine.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).