From: David Miller <davem@davemloft.net>
To: hau@realtek.com
Cc: netdev@vger.kernel.org, nic_swsd@realtek.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 0/9] r8169:update hardware ephy parameter
Date: Tue, 09 Dec 2014 18:35:49 -0500 (EST) [thread overview]
Message-ID: <20141209.183549.1930188640715074097.davem@davemloft.net> (raw)
In-Reply-To: <1418143563-7652-1-git-send-email-hau@realtek.com>
From: Chunhao Lin <hau@realtek.com>
Date: Wed, 10 Dec 2014 00:45:54 +0800
> Update hardware ephy parameter to improve pcie compatibility.
This really doesn't tell me anything, I really dislike patch
series like this one.
All of the programming is magic values to magic offsets.
You aren't even trying to describe in the commit log message exactly
what kind of settings are being changed, and exactly how those changes
achieve the stated goal.
Furthermore, the commit description makes no sense at all to me.
How can programming the ethernet MAC PHY have any influence on PCI-E
bus compatability? Or are you programming the PCI bus interface's
PHY?
In what way are you adjusting which settings and in what way do those
adjustments help improve PCI-E bus behavior?
You absolutely must describe exactly what the new programming
is actually doing, precisely, and in detail. I want to know
if some kind of timings are being adjusted, and in what way.
Are some fifo limits being changes? If so, in what way, and
why does that help.
You have to describe what you are doing. Short and non-informative
commit log messages alongside random changes to undocumented magic
constant registers is simply unacceptable.
next prev parent reply other threads:[~2014-12-09 23:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-09 16:45 [PATCH net-next 0/9] r8169:update hardware ephy parameter Chunhao Lin
2014-12-09 16:45 ` [PATCH net-next 1/9] r8169:update rtl8168g " Chunhao Lin
2014-12-09 16:45 ` [PATCH net-next 2/9] r8169:update rtl8168gu " Chunhao Lin
2014-12-09 16:45 ` [PATCH net-next 3/9] r8169:update rtl8411b " Chunhao Lin
2014-12-09 16:45 ` [PATCH net-next 4/9] r8169:update rtl8411 " Chunhao Lin
2014-12-09 16:45 ` [PATCH net-next 5/9] r8169:update rtl8168fb " Chunhao Lin
2014-12-09 23:48 ` Francois Romieu
2014-12-09 16:46 ` [PATCH net-next 6/9] r8169:update rtl8168e-vl " Chunhao Lin
2014-12-09 16:46 ` [PATCH net-next 7/9] r8169:update rtl8168dp " Chunhao Lin
2014-12-09 23:50 ` Francois Romieu
2014-12-09 16:46 ` [PATCH net-next 8/9] r8169:update rtl8105e " Chunhao Lin
2014-12-09 16:46 ` [PATCH net-next 9/9] r8169:update rtl8402 " Chunhao Lin
2014-12-09 23:35 ` David Miller [this message]
2014-12-10 7:17 ` [PATCH net-next 0/9] r8169:update hardware " Hau
2014-12-09 23:47 ` Francois Romieu
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=20141209.183549.1930188640715074097.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=hau@realtek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nic_swsd@realtek.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