linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: Ralf Baechle <ralf@linux-mips.org>,
	Paul Burton <paulburton@kernel.org>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	linux-kernel@vger.kernel.org, linux-mips@vger.kernel.org
Subject: Re: [PATCH v1] MIPS: reduce print level for cache information
Date: Fri, 28 Feb 2020 12:46:08 +0100	[thread overview]
Message-ID: <20200228114608.GB10905@alpha.franken.de> (raw)
In-Reply-To: <20200228055238.11140-1-o.rempel@pengutronix.de>

On Fri, Feb 28, 2020 at 06:52:38AM +0100, Oleksij Rempel wrote:
> Default printk log level is KERN_WARNING. This makes automatic log
> parsing problematic, since we get false positive alarms on not critical
> information.
> 
> Set all not critical cache related information to KERN_INFO, the same level
> as used on most kernel drivers.
> 
> Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
> ---
>  arch/mips/mm/c-octeon.c | 18 +++++++++---------
>  arch/mips/mm/c-r3k.c    |  4 ++--
>  arch/mips/mm/c-r4k.c    | 20 ++++++++++----------
>  arch/mips/mm/c-tx39.c   |  4 ++--
>  4 files changed, 23 insertions(+), 23 deletions(-)

applied to mips-next.

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]

      reply	other threads:[~2020-02-28 11:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-28  5:52 [PATCH v1] MIPS: reduce print level for cache information Oleksij Rempel
2020-02-28 11:46 ` Thomas Bogendoerfer [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=20200228114608.GB10905@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=kernel@pengutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=o.rempel@pengutronix.de \
    --cc=paulburton@kernel.org \
    --cc=ralf@linux-mips.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).