From: Andrew Lunn <andrew@lunn.ch>
To: Xiaoliang Yang <xiaoliang.yang_1@nxp.com>
Cc: Vladimir Oltean <vladimir.oltean@nxp.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"allan.nielsen@microchip.com" <allan.nielsen@microchip.com>,
"joergen.andreasen@microchip.com"
<joergen.andreasen@microchip.com>,
"UNGLinuxDriver@microchip.com" <UNGLinuxDriver@microchip.com>,
Alexandru Marginean <alexandru.marginean@nxp.com>,
Po Liu <po.liu@nxp.com>, Claudiu Manoil <claudiu.manoil@nxp.com>,
Leo Li <leoyang.li@nxp.com>
Subject: Re: [net-next] net: dsa: felix: convert TAS link speed based on phylink speed
Date: Thu, 24 Sep 2020 14:30:26 +0200 [thread overview]
Message-ID: <20200924123026.GB3802929@lunn.ch> (raw)
In-Reply-To: <DB8PR04MB578529D733A50F048A1EB793F0390@DB8PR04MB5785.eurprd04.prod.outlook.com>
> I modify the commit and resend this patch to "net tree", please reject this one.
Hi Xiaoliang Yang
You dropped "PATCH" from the subject. Please also include a version
number, so it is possible to identify which is the last version:
[PATCH net v2] net: dsa: felix: convert TAS link speed based on phylink speed
https://www.kernel.org/doc/html/latest/process/submitting-patches.html
https://www.kernel.org/doc/html/latest/networking/netdev-FAQ.html
It is a good idea to spend a few minutes every day just reading
patches and review comments to get an idea how the process works.
Andrew
prev parent reply other threads:[~2020-09-24 12:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-22 10:43 [net-next] net: dsa: felix: convert TAS link speed based on phylink speed Xiaoliang Yang
2020-09-22 11:36 ` Vladimir Oltean
2020-09-24 2:10 ` Xiaoliang Yang
2020-09-24 12:30 ` Andrew Lunn [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=20200924123026.GB3802929@lunn.ch \
--to=andrew@lunn.ch \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandru.marginean@nxp.com \
--cc=allan.nielsen@microchip.com \
--cc=claudiu.manoil@nxp.com \
--cc=davem@davemloft.net \
--cc=joergen.andreasen@microchip.com \
--cc=leoyang.li@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=po.liu@nxp.com \
--cc=vladimir.oltean@nxp.com \
--cc=xiaoliang.yang_1@nxp.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