From: Jakub Kicinski <kuba@kernel.org>
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: netdev@vger.kernel.org, devicetree@vger.kernel.org,
Woojung Huh <woojung.huh@microchip.com>,
Arun Ramadoss <arun.ramadoss@microchip.com>,
UNGLinuxDriver@microchip.com, Andrew Lunn <andrew@lunn.ch>,
Vivien Didelot <vivien.didelot@gmail.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Vladimir Oltean <olteanv@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Brian Hutchinson <b.hutchman@gmail.com>
Subject: Re: [PATCH net] net: dsa: microchip: make learning configurable and keep it off while standalone
Date: Tue, 2 Aug 2022 21:53:36 -0700 [thread overview]
Message-ID: <20220802215336.6bc61114@kernel.org> (raw)
In-Reply-To: <20220802002636.3963025-1-vladimir.oltean@nxp.com>
On Tue, 2 Aug 2022 03:26:36 +0300 Vladimir Oltean wrote:
> This is compile-tested only, but the equivalent change was tested by
> Brian on a 5.10 kernel and it worked.
>
> I'm targeting just the "net" tree here (today 5.19 release candidates),
> but this needs to be fixed separately for net-next and essentially every
> other stable branch, since we will be lacking the port_bridge_flags
> callbacks, and there has been a lot of general refactoring in the
> microchip driver.
>
> Jakub, I wonder if I should let you do the merge resolution between
> "net" and "net-next", or should I just resend against "net-next" and
> keep this patch as one of the stable backports?
I missed this question, sorry. Let's do the latter.
prev parent reply other threads:[~2022-08-03 4:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-02 0:26 [PATCH net] net: dsa: microchip: make learning configurable and keep it off while standalone Vladimir Oltean
2022-08-03 4:53 ` 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=20220802215336.6bc61114@kernel.org \
--to=kuba@kernel.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=arun.ramadoss@microchip.com \
--cc=b.hutchman@gmail.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=vivien.didelot@gmail.com \
--cc=vladimir.oltean@nxp.com \
--cc=woojung.huh@microchip.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).