From: Javier Carrasco <javier.carrasco.cruz@gmail.com>
To: Marcin Wojtas <marcin.s.wojtas@gmail.com>,
Russell King <linux@armlinux.org.uk>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Javier Carrasco <javier.carrasco.cruz@gmail.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>
Subject: [PATCH PARTIAL RESEND 0/2] net: mvpp2: rework child node/port removal handling
Date: Thu, 08 Aug 2024 11:47:31 +0200 [thread overview]
Message-ID: <20240808-mvpp2_child_nodes-v1-0-19f854dd669d@gmail.com> (raw)
These two patches used to be part of another series [1] that did not
apply to the networking tree without conflicts. This is therefore just a
partial resend with no code modifications, just rebased onto net/main.
Link: https://lore.kernel.org/all/20240806181026.5fe7f777@kernel.org/ [1]
Signed-off-by: Javier Carrasco <javier.carrasco.cruz@gmail.com>
---
Javier Carrasco (2):
net: mvpp2: use port_count to remove ports
net: mvpp2: use device_for_each_child_node() to access device child nodes
drivers/net/ethernet/marvell/mvpp2/mvpp2_main.c | 31 +++++++------------------
1 file changed, 9 insertions(+), 22 deletions(-)
---
base-commit: b928e7d19dfd8a336e13ec0d21e1d60dc285efd5
change-id: 20240807-mvpp2_child_nodes-b92f8eae0f87
Best regards,
--
Javier Carrasco <javier.carrasco.cruz@gmail.com>
next reply other threads:[~2024-08-08 9:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-08 9:47 Javier Carrasco [this message]
2024-08-08 9:47 ` [PATCH PARTIAL RESEND 1/2] net: mvpp2: use port_count to remove ports Javier Carrasco
2024-08-08 9:47 ` [PATCH PARTIAL RESEND 2/2] net: mvpp2: use device_for_each_child_node() to access device child nodes Javier Carrasco
2024-08-11 16:12 ` [PATCH PARTIAL RESEND 0/2] net: mvpp2: rework child node/port removal handling patchwork-bot+netdevbpf
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=20240808-mvpp2_child_nodes-v1-0-19f854dd669d@gmail.com \
--to=javier.carrasco.cruz@gmail.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=marcin.s.wojtas@gmail.com \
--cc=netdev@vger.kernel.org \
--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®