[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c327164e-e544-ecd8-3501-44e68942b725@synopsys.com>
Date: Wed, 25 Jan 2017 10:47:56 -0800
From: Vineet Gupta <Vineet.Gupta1@...opsys.com>
To: Alexey Brodkin <Alexey.Brodkin@...opsys.com>,
"peppe.cavallaro@...com" <peppe.cavallaro@...com>
CC: "manabian@...il.com" <manabian@...il.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"fabrice.gasnier@...com" <fabrice.gasnier@...com>,
"linux-snps-arc@...ts.infradead.org"
<linux-snps-arc@...ts.infradead.org>,
"alexandre.torgue@...il.com" <alexandre.torgue@...il.com>,
"preid@...ctromag.com.au" <preid@...ctromag.com.au>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"davem@...emloft.net" <davem@...emloft.net>
Subject: Re: stmmac: GMAC_RGSMIIIS reports bogus values
On 01/25/2017 10:39 AM, Alexey Brodkin wrote:
>> Also I wonder if, other version of the stmmac worked on this platform
>> before.
> It did work and still works. The only problem is we're getting
> a lot of noise now about bogus link status change. That's because
> this info is now in pr_info() compared to being previously in pr_debug().
While we sort out the real technical details, it is OK to go back to pr_debug
please - print_once or some such !
There is lot of useless console noise when we run any networking loads here !
echo 0 > /proc/sys/kernel/printk
only helps in that it is not printed on console but clobbers dmesg nonetheless !
Thx,
-Vineet
Powered by blists - more mailing lists