All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Christoph Hellwig <hch@lst.de>,
	Dimitri Sivanich <sivanich@hpe.com>,
	Mike Travis <mike.travis@hpe.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] kernel: mark all struct k_clock instances const
Date: Fri, 26 May 2017 09:09:42 -0700	[thread overview]
Message-ID: <1495814982.29207.35.camel@perches.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1705261232250.1902@nanos>

On Fri, 2017-05-26 at 12:32 +0200, Thomas Gleixner wrote:
> On Fri, 26 May 2017, Joe Perches wrote:
> > On Fri, 2017-05-26 at 12:03 +0300, Christoph Hellwig wrote:
> > > And initialize the array statically at compile time.   Originally
> > > based on changes in the Grsecurity patch set, but redone for mainline
> > > to be slightly cleaner, and take the SGI mmtimer removal into account,
> > > which allows for a completely static initialization.
> > 
> > Maybe add k_clock to scripts/const_structs.checkpatch
> Care to send a proper patch with changelog?

After Christoph's patch is in -next so I can reference
the proper commit SHA1.

  reply	other threads:[~2017-05-26 16:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-26  9:03 constify struct k_clock Christoph Hellwig
2017-05-26  9:03 ` [PATCH 1/2] remove the SGI SN2 mmtimer driver Christoph Hellwig
2017-05-26 10:58   ` [tip:timers/core] mmtimer: Remove " tip-bot for Christoph Hellwig
2017-05-26 14:43     ` Joe Perches
2017-05-26  9:03 ` [PATCH 2/2] kernel: mark all struct k_clock instances const Christoph Hellwig
2017-05-26  9:35   ` Joe Perches
2017-05-26 10:32     ` Thomas Gleixner
2017-05-26 16:09       ` Joe Perches [this message]
2017-05-26 10:58   ` [tip:timers/core] posix-timers: Make posix_clocks immutable tip-bot for Christoph Hellwig
2017-05-26 12:39   ` tip-bot for Christoph Hellwig
2017-05-26 12:40   ` tip-bot for Christoph Hellwig
2017-05-27  7:52   ` tip-bot for Christoph Hellwig

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=1495814982.29207.35.camel@perches.com \
    --to=joe@perches.com \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mike.travis@hpe.com \
    --cc=sivanich@hpe.com \
    --cc=tglx@linutronix.de \
    /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.