From: Joe Perches <joe@perches.com>
To: Ryan Mallon <rmallon@gmail.com>
Cc: Toshiaki Yamane <yamanetoshi@gmail.com>,
greg@kroah.com, willy@meta-x.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] panel: Use pr_err(...) rather than printk(KERN_ERR ...)
Date: Wed, 11 Jul 2012 22:43:08 -0700 [thread overview]
Message-ID: <1342071788.1970.18.camel@joe2Laptop> (raw)
In-Reply-To: <4FFE5F0F.8020904@gmail.com>
On Thu, 2012-07-12 at 15:22 +1000, Ryan Mallon wrote:
> On 12/07/12 12:35, Toshiaki Yamane wrote:
> > This change is inspired by checkpatch.
>
> Your changelog needs to describe all of the changes you are making. The
> subject line only describes one. This patch is doing the following:
>
> - Converting printk(KERN_ERR to pr_err
> - Adding __func__ prefixes to printk lines
> - Refactoring split printk strings onto a single line
>
> There are a few other printks in this file which could be converted to
> pr_* to make the code more consistent. Perhaps a follow up patch?
>
> Typically for a sub-sequent version of a patch/series you should list
> the changes since the last round. Put these below the --- so that they
> don't become part of the change log, e.g.:
>
> Signed-off-by: Your name/email here
> ---
>
> Changes since v2:
> - Some stuff
>
> Changes since v1:
> - Some other stuff
>
> Some more comments below.
And ideally cc the people that gave you notes/comments
on your previous patches too.
next prev parent reply other threads:[~2012-07-12 5:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-12 2:35 [PATCH v3] panel: Use pr_err(...) rather than printk(KERN_ERR ...) Toshiaki Yamane
2012-07-12 5:22 ` Ryan Mallon
2012-07-12 5:43 ` Joe Perches [this message]
2012-07-12 6:36 ` Toshiaki Yamane
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=1342071788.1970.18.camel@joe2Laptop \
--to=joe@perches.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rmallon@gmail.com \
--cc=willy@meta-x.org \
--cc=yamanetoshi@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.