From: Joe Perches <joe@perches.com>
To: Colin King <colin.king@canonical.com>, linuxppc-dev@lists.ozlabs.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] powerpc/32: add missing \n at end of printk warning message
Date: Mon, 12 Sep 2016 09:34:27 -0700 [thread overview]
Message-ID: <1473698067.11006.10.camel@perches.com> (raw)
In-Reply-To: <20160912101224.24877-1-colin.king@canonical.com>
On Mon, 2016-09-12 at 11:12 +0100, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
> The message is missing a \n, add it.
Was this found via inspection or a tool?
next prev parent reply other threads:[~2016-09-12 16:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-12 10:12 [PATCH] powerpc/32: add missing \n at end of printk warning message Colin King
2016-09-12 15:21 ` Christophe Leroy
2016-09-13 1:25 ` Michael Ellerman
2016-09-12 16:34 ` Joe Perches [this message]
2016-09-12 16:49 ` Colin Ian King
2016-09-13 12:16 ` Michael Ellerman
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=1473698067.11006.10.camel@perches.com \
--to=joe@perches.com \
--cc=colin.king@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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