DPDK-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Evgeny Sokolov <Evgeny.Sokolov@infotecs.ru>
Cc: Thomas Monjalon <thomas@monjalon.net>,
	Chas Williams <3chas3@gmail.com>,
	"Min Hu (Connor)" <humin29@huawei.com>,
	Declan Doherty <declan.doherty@intel.com>, <dev@dpdk.org>,
	<stable@dpdk.org>, <chas3@att.com>
Subject: Re: [PATCH] net/bonding: fix the log MAC address restore failure
Date: Wed, 22 Jul 2026 11:20:26 -0700	[thread overview]
Message-ID: <20260722112026.180bf024@phoenix.local> (raw)
In-Reply-To: <20260629135841.1181247-1-Evgeny.Sokolov@infotecs.ru>

On Mon, 29 Jun 2026 13:58:40 +0000
Evgeny Sokolov <Evgeny.Sokolov@infotecs.ru> wrote:

> Log an error when rte_eth_dev_default_mac_addr_set() fails while
> restoring the default MAC address of a member device removed from a
> bonding device.
> This improves visibility of failures without changing the existing
> behavior.
> 
> Fixes: aa7791ba8de0 ("net/bonding: fix setting slave MAC addresses")
> Cc: chas3@att.com
> 
> Signed-off-by: Evgeny Sokolov <Evgeny.Sokolov@infotecs.ru>
> Cc: stable@dpdk.org
> ---

This patch is technically correct, and I have no issues with the code itself.

However, the submitter's mail domain (infotecs.ru) belongs to JSC
InfoTeCS, which is on the EU consolidated sanctions list. Whether a
contribution from a sanctioned entity can be accepted is a legal
question, and not one a maintainer has the authority to decide.

Holding off on merging this patch until there is direction from LF
legal and/or the DPDK governing board.

      parent reply	other threads:[~2026-07-22 18:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-29 13:58 [PATCH] net/bonding: fix the log MAC address restore failure Evgeny Sokolov
2026-07-21 10:37 ` Sokolov Evgeny
2026-07-22 18:20 ` Stephen Hemminger [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=20260722112026.180bf024@phoenix.local \
    --to=stephen@networkplumber.org \
    --cc=3chas3@gmail.com \
    --cc=Evgeny.Sokolov@infotecs.ru \
    --cc=chas3@att.com \
    --cc=declan.doherty@intel.com \
    --cc=dev@dpdk.org \
    --cc=humin29@huawei.com \
    --cc=stable@dpdk.org \
    --cc=thomas@monjalon.net \
    /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