mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Bert Wesarg" <bert.wesarg@googlemail.com>
To: "Adrian Bunk" <bunk@kernel.org>
Cc: "Mike Travis" <travis@sgi.com>, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] drivers/base/cpu.c: make code static
Date: Wed, 23 Apr 2008 14:58:21 +0200	[thread overview]
Message-ID: <36ca99e90804230558y7ad26b78t1375a67d85edd286@mail.gmail.com> (raw)
In-Reply-To: <20080423095233.GL28933@cs181133002.pp.htv.fi>

On Wed, Apr 23, 2008 at 11:52 AM, Adrian Bunk <bunk@kernel.org> wrote:
> This patch makes the following needlessly global code static:
>  - attr_online_map
>  - attr_possible_map
>  - attr_present_map
>
>  Signed-off-by: Adrian Bunk <bunk@kernel.org>
>
>  ---
>  8ab09fe4313384faa5e3577d99845cedccb245bc diff --git a/drivers/base/cpu.c b/drivers/base/cpu.c
>  index 6fe4174..da6f4ae 100644
>  --- a/drivers/base/cpu.c
>  +++ b/drivers/base/cpu.c
>  @@ -119,7 +119,7 @@ static ssize_t print_cpus_##type(struct sysdev_class *class, char *buf)     \
>   {                                                                      \
>         return print_cpus_map(buf, &cpu_##type##_map);                  \
>   }                                                                      \
>  -struct sysdev_class_attribute attr_##type##_map =                      \
>  +static struct sysdev_class_attribute attr_##type##_map =               \
>         _SYSDEV_CLASS_ATTR(type, 0444, print_cpus_##type, NULL)
>
>   print_cpus_func(online);
I think the cpu_state_attr array a few lines down should be static too.

Bert

  reply	other threads:[~2008-04-23 12:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-23  9:52 Adrian Bunk
2008-04-23 12:58 ` Bert Wesarg [this message]
2008-04-23 11:05 Mike Travis

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=36ca99e90804230558y7ad26b78t1375a67d85edd286@mail.gmail.com \
    --to=bert.wesarg@googlemail.com \
    --cc=bunk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=travis@sgi.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

Powered by JetHome