From: Andrew Lunn <andrew@lunn•ch>
To: Florian Fainelli <f.fainelli@gmail•com>
Cc: netdev@vger•kernel.org,
Vivien Didelot <vivien.didelot@savoirfairelinux•com>,
"David S. Miller" <davem@davemloft•net>,
open list <linux-kernel@vger•kernel.org>
Subject: Re: [PATCH net-next] net: dsa: dsa_loop: Make dynamic debugging helpful
Date: Fri, 25 May 2018 14:16:09 +0200 [thread overview]
Message-ID: <20180525121609.GC20060@lunn.ch> (raw)
In-Reply-To: <20180525035215.19341-1-f.fainelli@gmail.com>
On Thu, May 24, 2018 at 08:52:14PM -0700, Florian Fainelli wrote:
> Remove redundant debug prints from phy_read/write since we can trace those
> calls through trace events. Enhance dynamic debug prints to print arguments
> which helps figuring how what is going on at the driver level with higher level
> configuration interfaces.
>
> Signed-off-by: Florian Fainelli <f.fainelli@gmail•com>
Reviewed-by: Andrew Lunn <andrew@lunn•ch>
Andrew
next prev parent reply other threads:[~2018-05-25 12:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-25 3:52 [PATCH net-next] net: dsa: dsa_loop: Make dynamic debugging helpful Florian Fainelli
2018-05-25 12:16 ` Andrew Lunn [this message]
2018-05-25 20:52 ` David Miller
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=20180525121609.GC20060@lunn.ch \
--to=andrew@lunn$(echo .)ch \
--cc=davem@davemloft$(echo .)net \
--cc=f.fainelli@gmail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=vivien.didelot@savoirfairelinux$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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