From: Thomas Gleixner <tglx@linutronix.de>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: John Stultz <johnstul@us.ibm.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Make clocksource name const
Date: Sat, 2 Apr 2011 21:08:13 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.00.1104022107520.5929@localhost6.localdomain6> (raw)
In-Reply-To: <20110402141134.GA23324@n2100.arm.linux.org.uk>
On Sat, 2 Apr 2011, Russell King - ARM Linux wrote:
> Has this patch been rejected?
No, I think it just got lost. Will pick it up.
> On Sat, Feb 19, 2011 at 03:34:50PM +0000, Russell King - ARM Linux wrote:
> > As nothing should be writing to the clocksource name string, make the
> > clocksource name pointer const. Build-tested on ARM Versatile Express.
> >
> > Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
> > ---
> > include/linux/clocksource.h | 2 +-
> > 1 files changed, 1 insertions(+), 1 deletions(-)
> >
> > diff --git a/include/linux/clocksource.h b/include/linux/clocksource.h
> > index c37b21a..94c1f38 100644
> > --- a/include/linux/clocksource.h
> > +++ b/include/linux/clocksource.h
> > @@ -161,7 +161,7 @@ struct clocksource {
> > /*
> > * First part of structure is read mostly
> > */
> > - char *name;
> > + const char *name;
> > struct list_head list;
> > int rating;
> > cycle_t (*read)(struct clocksource *cs);
>
next prev parent reply other threads:[~2011-04-02 19:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-19 15:34 [PATCH] Make clocksource name const Russell King - ARM Linux
2011-02-21 18:51 ` john stultz
2011-04-02 14:11 ` Russell King - ARM Linux
2011-04-02 19:08 ` Thomas Gleixner [this message]
2011-04-02 19:31 ` Thomas Gleixner
2011-04-04 17:42 ` john stultz
2011-04-04 17:44 ` Thomas Gleixner
2011-04-04 18:22 ` john stultz
2011-04-04 19:07 ` Thomas Gleixner
2011-04-04 20:25 ` [PATCH] Make clocksource name const... RTC: Fix early irqs caused by calling rtc_set_alarm too early Konrad Rzeszutek Wilk
2011-04-04 21:07 ` john stultz
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=alpine.LFD.2.00.1104022107520.5929@localhost6.localdomain6 \
--to=tglx@linutronix.de \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
/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