From: Simon Horman <horms@kernel.org>
To: Raju Lakkaraju <Raju.Lakkaraju@microchip.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net,
linux@armlinux.org.uk, kuba@kernel.org, andrew@lunn.ch,
hkallweit1@gmail.com, richardcochran@gmail.com,
rdunlap@infradead.org, Bryan.Whitehead@microchip.com,
edumazet@google.com, pabeni@redhat.com,
linux-kernel@vger.kernel.org, UNGLinuxDriver@microchip.com
Subject: Re: [PATCH net-next] net: phylink: Add phylinksetfixed_link() to configure fixed link state in phylink
Date: Mon, 19 Aug 2024 17:23:53 +0100 [thread overview]
Message-ID: <20240819162353.GJ11472@kernel.org> (raw)
In-Reply-To: <20240819052335.346184-1-Raju.Lakkaraju@microchip.com>
On Mon, Aug 19, 2024 at 10:53:35AM +0530, Raju Lakkaraju wrote:
> From: Russell King <linux@armlinux.org.uk>
>
> The function allows for the configuration of a fixed link state for a given
> phylink instance. This addition is particularly useful for network devices that
> operate with a fixed link configuration, where the link parameters do not change
> dynamically. By using `phylink_set_fixed_link()`, drivers can easily set up
> the fixed link state during initialization or configuration changes.
>
> Signed-off-by: Russell King <linux@armlinux.org.uk>
> Signed-off-by: Raju Lakkaraju <Raju.Lakkaraju@microchip.com>
> ---
> Note: This code was developed by Mr.Russell King.
Hi,
I am wondering if we need a user of this function in order for this patch
to be accepted, as is often the practice for new features.
next prev parent reply other threads:[~2024-08-19 16:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-19 5:23 [PATCH net-next] net: phylink: Add phylinksetfixed_link() to configure fixed link state in phylink Raju Lakkaraju
2024-08-19 16:08 ` Andrew Lunn
2024-08-21 7:48 ` Raju.Lakkaraju
2024-08-19 16:23 ` Simon Horman [this message]
2024-08-21 7:55 ` Raju.Lakkaraju
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=20240819162353.GJ11472@kernel.org \
--to=horms@kernel.org \
--cc=Bryan.Whitehead@microchip.com \
--cc=Raju.Lakkaraju@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rdunlap@infradead.org \
--cc=richardcochran@gmail.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).