From: Felipe Balbi <balbi@ti.com>
To: "Turquette, Mike" <mturquette@ti.com>
Cc: Rajendra Nayak <rnayak@ti.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] clk: constify parent name arrays in macros
Date: Fri, 27 Apr 2012 21:18:36 +0300 [thread overview]
Message-ID: <20120427181833.GA24587@arwen.pp.htv.fi> (raw)
In-Reply-To: <CAJOA=zNzkOvzdFSuSzC015ELZWE+Jtj=H5P9fbQSHW3HZdsZow@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1238 bytes --]
On Fri, Apr 27, 2012 at 10:55:50AM -0700, Turquette, Mike wrote:
> On Fri, Apr 27, 2012 at 5:28 AM, Rajendra Nayak <rnayak@ti.com> wrote:
> > parent name array is now expected to be const char *, make
> > the relevent changes in the clk macros which define
> > default clock types.
> >
> > Signed-off-by: Rajendra Nayak <rnayak@ti.com>
>
> Good catch Rajendra. I'll pull it into clk-next.
>
> Regards,
> Mike
>
> > ---
> > include/linux/clk-private.h | 6 +++---
> > 1 files changed, 3 insertions(+), 3 deletions(-)
> >
> > diff --git a/include/linux/clk-private.h b/include/linux/clk-private.h
> > index eeae7a3..6ebec83 100644
> > --- a/include/linux/clk-private.h
> > +++ b/include/linux/clk-private.h
> > @@ -70,7 +70,7 @@ struct clk {
> > #define DEFINE_CLK_FIXED_RATE(_name, _flags, _rate, \
> > _fixed_rate_flags) \
> > static struct clk _name; \
> > - static char *_name##_parent_names[] = {}; \
> > + static const char *_name##_parent_names[] = {}; \
does it make sense to have this as:
static const char * const _name##_parent_names[] = { }; ??
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-04-27 18:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-27 12:28 Rajendra Nayak
2012-04-27 17:55 ` Turquette, Mike
2012-04-27 18:18 ` Felipe Balbi [this message]
2012-05-01 22:18 ` Turquette, Mike
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=20120427181833.GA24587@arwen.pp.htv.fi \
--to=balbi@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@ti.com \
--cc=rnayak@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®