All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frederic Weisbecker <fweisbec@gmail.com>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: linux-kernel@vger.kernel.org, cmetcalf@ezchip.com
Subject: Re: [PATCH 2/3] nohz: mark tick_nohz_init_all() as __init
Date: Thu, 24 Sep 2015 16:33:57 +0200	[thread overview]
Message-ID: <20150924143356.GA8569@lerouge> (raw)
In-Reply-To: <1441915107-2000-3-git-send-email-lcapitulino@redhat.com>

On Thu, Sep 10, 2015 at 03:58:26PM -0400, Luiz Capitulino wrote:
> It's only called by tick_nohz_init().
> 
> Signed-off-by: Luiz Capitulino <lcapitulino@redhat.com>
> ---
>  kernel/time/tick-sched.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/kernel/time/tick-sched.c b/kernel/time/tick-sched.c
> index 8d45638..4cc6df03 100644
> --- a/kernel/time/tick-sched.c
> +++ b/kernel/time/tick-sched.c
> @@ -308,7 +308,7 @@ static int tick_nohz_cpu_down_callback(struct notifier_block *nfb,
>  	return NOTIFY_OK;
>  }
>  
> -static int tick_nohz_init_all(void)
> +static int __init tick_nohz_init_all(void)
>  {
>  	int err = -1;

For some reasons I thought sections don't apply to static functions. Well I still don't know
but I guess it works as long as the function doesn't get inlined. Or likely it prevents it from
being inlined.

Anyway, I think we can take the patch.

Thanks.


>  
> -- 
> 2.1.0
> 

  reply	other threads:[~2015-09-24 14:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-10 19:58 [PATCH 0/3] nohz: minor cleanups Luiz Capitulino
2015-09-10 19:58 ` [PATCH 1/3] nohz: mark tick_nohz_full_running as __read_mostly Luiz Capitulino
2015-09-10 19:58 ` [PATCH 2/3] nohz: mark tick_nohz_init_all() as __init Luiz Capitulino
2015-09-24 14:33   ` Frederic Weisbecker [this message]
2015-09-10 19:58 ` [PATCH 3/3] sched: add_nr_running(): drop tick_nohz_full_cpu() check Luiz Capitulino
2015-09-24 14:44   ` Frederic Weisbecker
2015-09-24 14:54     ` Luiz Capitulino

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=20150924143356.GA8569@lerouge \
    --to=fweisbec@gmail.com \
    --cc=cmetcalf@ezchip.com \
    --cc=lcapitulino@redhat.com \
    --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 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.