From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clk: wm831x: fix checkpatch issue for static const char * array
Date: Wed, 4 Jul 2012 11:19:36 +0100 [thread overview]
Message-ID: <20120704101936.GD4111@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1341395680-14142-1-git-send-email-Barry.Song@csr.com>
On Wed, Jul 04, 2012 at 05:54:40PM +0800, Barry Song wrote:
> From: Barry Song <Baohua.Song@csr.com>
>
> static const char * array should probably be static const char * const
We need some additional clock API patches to get merged before this is
OK, last time I checked the API wasn't const correct enough for it.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120704/dc221aa9/attachment.sig>
next prev parent reply other threads:[~2012-07-04 10:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-04 9:54 [PATCH] clk: wm831x: fix checkpatch issue for static const char * array Barry Song
2012-07-04 10:19 ` Mark Brown [this message]
2012-07-06 2:37 ` Barry Song
2012-07-06 11:08 ` Mark Brown
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=20120704101936.GD4111@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).