public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: John Ogness <john.ogness@linutronix.de>
Cc: Petr Mladek <pmladek@suse.com>,
	Paul Menzel <pmenzel@molgen.mpg.de>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>,
	x86@kernel.org, LKML <linux-kernel@vger.kernel.org>,
	it+linux-x86@molgen.mpg.de,
	Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Subject: Re: smpboot: CPU numbers printed as warning
Date: Tue, 16 Feb 2021 12:39:36 +0100	[thread overview]
Message-ID: <20210216113936.GC10592@zn.tnic> (raw)
In-Reply-To: <871rdg8dyb.fsf@jogness.linutronix.de>

On Tue, Feb 16, 2021 at 12:17:24PM +0106, John Ogness wrote:
> It is supported to provide loglevels for CONT messages. The loglevel is
> then only used if the append fails:
> 
>     pr_cont(KERN_INFO "message part");
> 
> I don't know if we want to go down that path. But it is supported.

Sounds ok to me. I leave it up to you guys to decide whether we wanna
change that there.

But I don't care that much about the CPU numbers ending up getting
issued at warning level so we can just as well do nothing and leave it
as is.

Thx.

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette

  reply	other threads:[~2021-02-16 11:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-15 19:22 smpboot: CPU numbers printed as warning Paul Menzel
2021-02-16  9:49 ` Petr Mladek
2021-02-16 10:14   ` Borislav Petkov
2021-02-16 11:11     ` John Ogness
2021-02-16 11:39       ` Borislav Petkov [this message]
2021-02-16 11:58     ` Paul Menzel
2021-02-16 12:35       ` Peter Zijlstra
2021-02-16 10:38   ` Paul Menzel

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=20210216113936.GC10592@zn.tnic \
    --to=bp@alien8.de \
    --cc=it+linux-x86@molgen.mpg.de \
    --cc=john.ogness@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=pmenzel@molgen.mpg.de \
    --cc=pmladek@suse.com \
    --cc=sergey.senozhatsky@gmail.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.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