From: sgr.m.pdy@gmail.com (Sagar Padhye)
To: kernelnewbies@lists.kernelnewbies.org
Subject: [PATCH] FIXED sparse warning : drivers/cpuidle/cpuidle.c:27:1: warning: symbol 'cpuidle_dev' was not declared. Should it be static?
Date: Thu, 3 Oct 2013 12:04:40 +0530 [thread overview]
Message-ID: <20131003063439.GA31795@gmail.com> (raw)
In-Reply-To: <20131002192423.GX6192@mwanda>
> > I checked that cpuidle_devices is only being used in cpuidle.c - hence
> > thought that it can be made static and be removed from header.
>
> "cpuidle_devices" is actually used in drivers/cpuidle/coupled.c as well
> so this breaks the build.
Darn! I forgot 'clean build' part. sorry.
> Even for "cpuidle_dev" the patch isn't right. It doesn't fix the
> warning, for me. The DEFINE_PER_CPU() macro defines several variables
> actually. Per CPU variables are a bit complicated and they have to have
> globally unique names. So just ignore the Sparse warning for per CPU
> variables.
>
Ok, let me look at my sparse log once again, will pick some other problem (any suggestions?)
> There are several other "process" problems with the patch submission.
>
> 1) Incorrect subject. It should be:
> [PATCH] cpuidle: make a variable static
>
> This is based on `git log --oneline drivers/cpuidle/cpuidle.c`
> output.
>
> 2) No blank line between subject and body of commit message.
> 3) Line wrap the body of the email at 72 characters.
> 4) No Signed-off-by line.
>
Ok, will keep this in mind
Thanks and Regards,
Sagar
next parent reply other threads:[~2013-10-03 6:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1380739624-17257-1-git-send-email-sgr.m.pdy@gmail.com>
[not found] ` <20131002192423.GX6192@mwanda>
2013-10-03 6:34 ` Sagar Padhye [this message]
2013-10-02 18:56 [PATCH] FIXED sparse warning : drivers/cpuidle/cpuidle.c:27:1: warning: symbol 'cpuidle_dev' was not declared. Should it be static? Sagar Padhye
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=20131003063439.GA31795@gmail.com \
--to=sgr.m.pdy@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).