From: <Jerry.Ray@microchip.com>
To: <olteanv@gmail.com>
Cc: <andrew@lunn.ch>, <f.fainelli@gmail.com>, <davem@davemloft.net>,
<edumazet@google.com>, <kuba@kernel.org>, <pabeni@redhat.com>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux@armlinux.org.uk>
Subject: RE: [PATCH net-next v3 0/2] dsa: lan9303: Move to PHYLINK
Date: Tue, 6 Dec 2022 23:58:03 +0000 [thread overview]
Message-ID: <MWHPR11MB169321FC086EAD9BDFECD40AEF1B9@MWHPR11MB1693.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20221206185756.hfecpkcy2lqahng7@skbuf>
> > This patch series moves the lan9303 driver to use the phylink
> > api away from phylib.
> >
> > 1) adds port_max_mtu api support.
> > 2) Replace .adjust_link with .phylink_get_caps dsa api
>
> What does the max MTU have to do with phylink? What is it that makes
> these two patches related?
>
I'm touching the same file, so I created this series of patches to avoid
piecewise patching conflicts that might have resulted if they were
independent patches.
> >
> > Clearing the Turbo Mode bit previously done in the adjust_link
> > API is moved to the driver initialization immediately following
> > the successful detection of a LAN93xx device. It is forced to a
> > disabled state and never enabled.
> >
> > At this point, I do not see anything this driver needs from the other
> > phylink APIs.
> >
> > Signed-off-by: Jerry Ray <jerry.ray@microchip.com>
>
> You don't need to put your sign off on the cover letter.
>
Understood. Thx,
J.
prev parent reply other threads:[~2022-12-06 23:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-06 18:34 [PATCH net-next v3 0/2] dsa: lan9303: Move to PHYLINK Jerry Ray
2022-12-06 18:34 ` [PATCH net-next v3 1/2] dsa: lan9303: Add port_max_mtu API Jerry Ray
2022-12-06 18:56 ` Vladimir Oltean
2022-12-06 23:44 ` Jerry.Ray
2022-12-07 11:39 ` Vladimir Oltean
2022-12-06 18:35 ` [PATCH net-next v3 2/2] dsa: lan9303: Move to PHYLINK Jerry Ray
2022-12-06 19:32 ` Vladimir Oltean
2022-12-06 21:07 ` Russell King (Oracle)
2022-12-06 22:12 ` Vladimir Oltean
2022-12-06 22:58 ` Jerry.Ray
2022-12-07 14:01 ` Vladimir Oltean
2022-12-06 18:57 ` [PATCH net-next v3 0/2] " Vladimir Oltean
2022-12-06 23:58 ` Jerry.Ray [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=MWHPR11MB169321FC086EAD9BDFECD40AEF1B9@MWHPR11MB1693.namprd11.prod.outlook.com \
--to=jerry.ray@microchip.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--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;
as well as URLs for NNTP newsgroup(s).