From: Borislav Petkov <bp@alien8.de>
To: "Ghannam, Yazen" <Yazen.Ghannam@amd.com>
Cc: "linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"tony.luck@intel.com" <tony.luck@intel.com>,
"x86@kernel.org" <x86@kernel.org>
Subject: [5/5] EDAC, mce_amd: Print ExtErrorCode and description on a single line
Date: Mon, 4 Feb 2019 17:36:19 +0100 [thread overview]
Message-ID: <20190204163618.GF29639@zn.tnic> (raw)
On Mon, Feb 04, 2019 at 03:14:27PM +0000, Ghannam, Yazen wrote:
> Yes, you're right. But it seems that the next pr_* that's not a pr_cont will be on
> a newline automatically.
Ah, that must be that printk continuation fun around
4bcc595ccd80 ("printk: reinstate KERN_CONT for printing continuation lines")
> Should I add an explicit newline just to be sure we get one?
Nah, no need. If anything, we should strive to get rid of KERN_CONT, if
possible.
Thx.
next reply other threads:[~2019-02-04 16:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-04 16:36 Borislav Petkov [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-02-04 15:14 [5/5] EDAC, mce_amd: Print ExtErrorCode and description on a single line Yazen Ghannam
2019-02-03 12:21 Borislav Petkov
2019-02-01 22:55 Yazen Ghannam
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=20190204163618.GF29639@zn.tnic \
--to=bp@alien8.de \
--cc=Yazen.Ghannam@amd.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.com \
--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