From: Nick Warne <nick@linicks.net>
To: linux-kernel@vger.kernel.org
Subject: Still get build warnings - gcc-3.4.6 - 2.6.17.8
Date: Tue, 8 Aug 2006 21:48:11 +0100 [thread overview]
Message-ID: <200608082148.11433.nick@linicks.net> (raw)
Hi all,
I have had these warnings for ages:
kernel/power/pm.c:241: warning: `pm_register' is deprecated (declared at
kernel/power/pm.c:64)
kernel/power/pm.c:241: warning: `pm_register' is deprecated (declared at
kernel/power/pm.c:64)
kernel/power/pm.c:242: warning: `pm_unregister_all' is deprecated (declared at
kernel/power/pm.c:97)
kernel/power/pm.c:242: warning: `pm_unregister_all' is deprecated (declared at
kernel/power/pm.c:97)
kernel/power/pm.c:243: warning: `pm_send_all' is deprecated (declared at
kernel/power/pm.c:216)
kernel/power/pm.c:243: warning: `pm_send_all' is deprecated (declared at
kernel/power/pm.c:216)
and I think at one time there was a fix about that I applied, but it seems it
never made it into kernel.org.
Or is this my ggc problem?
Thanks,
Nick
--
Every program has two purposes:
one for which it was written and another for which it wasn't.
next reply other threads:[~2006-08-08 20:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-08 20:48 Nick Warne [this message]
2006-08-08 21:12 ` Still get build warnings - gcc-3.4.6 - 2.6.17.8 Randy.Dunlap
2006-08-08 22:15 ` Sam Ravnborg
2006-08-08 23:19 ` Greg KH
2006-08-09 17:38 ` Nick Warne
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=200608082148.11433.nick@linicks.net \
--to=nick@linicks.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox