From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: Alexey Brodkin <Alexey.Brodkin@synopsys.com>,
"peppe.cavallaro@st.com" <peppe.cavallaro@st.com>
Cc: "manabian@gmail.com" <manabian@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"fabrice.gasnier@st.com" <fabrice.gasnier@st.com>,
"linux-snps-arc@lists.infradead.org"
<linux-snps-arc@lists.infradead.org>,
"alexandre.torgue@gmail.com" <alexandre.torgue@gmail.com>,
"preid@electromag.com.au" <preid@electromag.com.au>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>
Subject: Re: stmmac: GMAC_RGSMIIIS reports bogus values
Date: Wed, 25 Jan 2017 10:47:56 -0800 [thread overview]
Message-ID: <c327164e-e544-ecd8-3501-44e68942b725@synopsys.com> (raw)
In-Reply-To: <1485369563.7117.81.camel@synopsys.com>
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
next prev parent reply other threads:[~2017-01-25 18:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-03 16:17 stmmac: GMAC_RGSMIIIS reports bogus values Alexey Brodkin
2016-11-14 8:14 ` Giuseppe CAVALLARO
2017-01-25 18:39 ` Alexey Brodkin
2017-01-25 18:47 ` Vineet Gupta [this message]
2017-01-27 10:23 ` Alexey Brodkin
2017-01-31 9:55 ` Giuseppe CAVALLARO
2017-01-31 13:24 ` Alexey Brodkin
2017-01-31 13:46 ` Giuseppe CAVALLARO
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=c327164e-e544-ecd8-3501-44e68942b725@synopsys.com \
--to=vineet.gupta1@synopsys.com \
--cc=Alexey.Brodkin@synopsys.com \
--cc=alexandre.torgue@gmail.com \
--cc=davem@davemloft.net \
--cc=fabrice.gasnier@st.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=manabian@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=peppe.cavallaro@st.com \
--cc=preid@electromag.com.au \
/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).