From: Vladimir Oltean <olteanv@gmail.com>
To: "Marek Behún" <kabel@kernel.org>
Cc: netdev@vger.kernel.org, Andrew Lunn <andrew@lunn.ch>,
Florian Fainelli <f.fainelli@gmail.com>
Subject: Re: [PATCH net-next v2 2/2] net: dsa: update the unicast MAC address when changing conduit
Date: Wed, 8 May 2024 16:44:03 +0300 [thread overview]
Message-ID: <20240508134403.kr5btyx6iekkxjf7@skbuf> (raw)
In-Reply-To: <20240508111328.ya4ydnmd6w764q5k@kandell>
On Wed, May 08, 2024 at 01:13:52PM +0200, Marek Behún wrote:
> I did send this to net-next. The question is whether I should keep the
> Fixes tag.
Well, sorry, I didn't notice that. Yes, please reference the commit in
some other way which does not appear to automated tooling that it fixes
a user visible bug.
prev parent reply other threads:[~2024-05-08 13:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-02 12:29 [PATCH net-next v2 0/2] Fix changing DSA conduit Marek Behún
2024-05-02 12:29 ` [PATCH net-next v2 1/2] net: dsa: deduplicate code adding / deleting the port address to fdb Marek Behún
2024-05-02 12:29 ` [PATCH net-next v2 2/2] net: dsa: update the unicast MAC address when changing conduit Marek Behún
2024-05-07 20:18 ` Vladimir Oltean
2024-05-08 11:13 ` Marek Behún
2024-05-08 13:44 ` Vladimir Oltean [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=20240508134403.kr5btyx6iekkxjf7@skbuf \
--to=olteanv@gmail.com \
--cc=andrew@lunn.ch \
--cc=f.fainelli@gmail.com \
--cc=kabel@kernel.org \
--cc=netdev@vger.kernel.org \
/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