From: Christian Herber <christian.herber@nxp.com>
To: David Miller <davem@davemloft.net>,
"hkallweit1@gmail.com" <hkallweit1@gmail.com>
Cc: "andrew@lunn.ch" <andrew@lunn.ch>,
"f.fainelli@gmail.com" <f.fainelli@gmail.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Re: [PATCH v2 net-next 0/1] Add BASE-T1 PHY support
Date: Wed, 21 Aug 2019 16:16:32 +0000 [thread overview]
Message-ID: <AM6PR0402MB37983B7CA4DC2EF962D75D0886AA0@AM6PR0402MB3798.eurprd04.prod.outlook.com> (raw)
In-Reply-To: 20190820.122234.1290995026664280862.davem@davemloft.net
On 20.08.2019 21:22, David Miller wrote:
>
> From: Christian Herber <christian.herber@nxp.com>
> Date: Mon, 19 Aug 2019 15:19:52 +0000
>
>> v1 patchset can be found here: https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flkml.org%2Flkml%2F2019%2F8%2F15%2F626&data=02%7C01%7Cchristian.herber%40nxp.com%7Ccbb5f329425240eda10a08d725a3c305%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C1%7C637019257604516613&sdata=IdBZbqGgA0upPZZrBQSxPL%2Fh7Tn4BtYA4%2FfS6dZngWU%3D&reserved=0
>
> Please expand and clarify your commit messages as requested by Heiner
> in his feedback to v1.
>
Hi David, Heiner,
could you please be specific what to add? The discussion was on various
topics. Agree that it would probably help to add some more clarity, but
it would be good if you can specify your expectation in this.
Christian
prev parent reply other threads:[~2019-08-21 16:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-19 15:19 [PATCH v2 net-next 0/1] Add BASE-T1 PHY support Christian Herber
2019-08-19 15:19 ` [PATCH v2 net-next 1/1] net: phy: Added BASE-T1 PHY support to PHY Subsystem Christian Herber
2019-08-20 19:22 ` [PATCH v2 net-next 0/1] Add BASE-T1 PHY support David Miller
2019-08-21 16:16 ` Christian Herber [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=AM6PR0402MB37983B7CA4DC2EF962D75D0886AA0@AM6PR0402MB3798.eurprd04.prod.outlook.com \
--to=christian.herber@nxp.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.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).