From: Andrew Lunn <andrew@lunn.ch>
To: Vladimir Oltean <olteanv@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Russell King <linux@armlinux.org.uk>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Mattias Forsblad <mattias.forsblad@gmail.com>
Subject: Re: [PATCH 0/3] dsa: mv88e6xxx: Add RMU enable/disable ops
Date: Sun, 15 Dec 2024 18:42:09 +0100 [thread overview]
Message-ID: <1a168ea7-92d2-47fe-86cf-c45556810d1c@lunn.ch> (raw)
In-Reply-To: <20241215-v6-13-rc1-net-next-mv88e6xxx-rmu-ops-v1-0-87671db17a65@lunn.ch>
On Sun, Dec 15, 2024 at 05:30:02PM +0000, Andrew Lunn wrote:
> Add internal APIs for enabling the Remote Management Unit, and
> extending the existing implementation to other families. Actually
> making use of the RMU is not included here, that will be part of a
> later big patch set, which without this preliminary patchset would be
> too big.
Gerr, forget to use b4 --set-prefixes net-next
Andrew
next prev parent reply other threads:[~2024-12-15 17:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-15 17:30 Andrew Lunn
2024-12-15 17:30 ` [PATCH 1/3] net: dsa: mv88e6xxx: Add RMU enable for switches that support disable Andrew Lunn
2024-12-15 17:30 ` [PATCH 2/3] net: dsa: mv88e6xxx: Enable RMU on 6165 family Andrew Lunn
2024-12-15 17:30 ` [PATCH 3/3] net: dsa: mv88e6xxx: Enable RMU on 6351 family Andrew Lunn
2024-12-15 17:42 ` Andrew Lunn [this message]
2024-12-15 22:59 ` [PATCH 0/3] dsa: mv88e6xxx: Add RMU enable/disable ops Vladimir Oltean
2024-12-16 9:50 ` Andrew Lunn
2024-12-16 14:59 ` Vladimir Oltean
2024-12-18 3:31 ` Jakub Kicinski
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=1a168ea7-92d2-47fe-86cf-c45556810d1c@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mattias.forsblad@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.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
all inboxes | Powered by JetHome®