From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "Ken O'Brien" <kernel@kenobrien.org>
Cc: ian@opensource.wolfsonmicro.com, dp@opensource.wolfsonmicro.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] power: Fixed function return type
Date: Mon, 30 May 2011 10:57:22 +0800 [thread overview]
Message-ID: <20110530025720.GA4130@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1306693112-31609-1-git-send-email-kernel@kenobrien.org>
On Sun, May 29, 2011 at 07:18:32PM +0100, Ken O'Brien wrote:
> Applied coding convention to fix "WARNING: static const char * array should probably be static const char * const"
>
> Signed-off-by: Ken O'Brien <kernel@kenobrien.org>
Acked-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
but note that your commit log doesn't describe the change (you're fixing
a data structure, not a function) and please word wrap within paragraphs
in your commit message for legibility.
parent reply other threads:[~2011-05-30 2:57 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1306693112-31609-1-git-send-email-kernel@kenobrien.org>]
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=20110530025720.GA4130@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=dp@opensource.wolfsonmicro.com \
--cc=ian@opensource.wolfsonmicro.com \
--cc=kernel@kenobrien.org \
--cc=linux-kernel@vger.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