From: Simon Horman <horms@kernel.org>
To: "A. Sverdlin" <alexander.sverdlin@siemens.com>
Cc: netdev@vger.kernel.org, Roger Quadros <rogerq@kernel.org>,
Grygorii Strashko <grygorii.strashko@ti.com>,
Chintan Vankar <c-vankar@ti.com>
Subject: Re: [PATCH 1/2] net: ethernet: ti: am65-cpsw-nuss: rename phy_node -> port_np
Date: Wed, 15 May 2024 11:04:09 +0100 [thread overview]
Message-ID: <20240515100409.GD154012@kernel.org> (raw)
In-Reply-To: <20240514122232.662060-1-alexander.sverdlin@siemens.com>
On Tue, May 14, 2024 at 02:22:27PM +0200, A. Sverdlin wrote:
> From: Alexander Sverdlin <alexander.sverdlin@siemens.com>
>
> Rename phy_node to port_np to better reflect what it actually is,
> because the new phylink API takes netdev node (or DSA port node),
> and resolves the phandle internally.
>
> Signed-off-by: Alexander Sverdlin <alexander.sverdlin@siemens.com>
Hi Alexander,
Thanks for your patches. A few minor notes on process:
1. Please provide a cover letter when posting Networking patch-sets
with more than 1 patch.
2. As an enhancement - as opposed to a fix - this patch should be
targeted at the net-next kernel. And it's best to explicitly note that
in the subject.
Subject: [PATCH net-next] ...
3. As it happens, net-next is currently closed for the v6.10 merge window.
Please consider reposting as a PATCH once net-next re-opens, after 27th May.
In the meantime, feel free to post new versions as you get feedback,
but please switch to posting as RFC during that time.
Link: https://docs.kernel.org/process/maintainer-netdev.html
--
pw-bot: defer
prev parent reply other threads:[~2024-05-15 10:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-14 12:22 [PATCH 1/2] net: ethernet: ti: am65-cpsw-nuss: rename phy_node -> port_np A. Sverdlin
2024-05-14 12:22 ` [PATCH 2/2] net: ethernet: ti: am65-cpsw-nuss: populate netdev of_node A. Sverdlin
2024-05-15 10:04 ` Simon Horman [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=20240515100409.GD154012@kernel.org \
--to=horms@kernel.org \
--cc=alexander.sverdlin@siemens.com \
--cc=c-vankar@ti.com \
--cc=grygorii.strashko@ti.com \
--cc=netdev@vger.kernel.org \
--cc=rogerq@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;
as well as URLs for NNTP newsgroup(s).