From: John Cherry <cherry@osdl.org>
To: Greg KH <greg@kroah.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: IA32 (2.6.8.1 - 2004-08-22.21.30) - 3 New warnings (gcc 3.2.2)
Date: Mon, 23 Aug 2004 16:02:20 -0700 [thread overview]
Message-ID: <1093302139.12874.143.camel@cherrybomb.pdx.osdl.net> (raw)
In-Reply-To: <20040823213431.GA4371@kroah.com>
Greg,
Yes, these are valid warnings (as most warning are). I am just flagging
these since they are NEW to the build. These particular warnings are
likely to go away soon after Jan 1, which is good information to know.
These warning will not show up again as NEW warnings.
BTW, Linus flagged these warning cases as part of changeset 1.1803.1.58.
John
On Mon, 2004-08-23 at 14:34, Greg KH wrote:
> On Mon, Aug 23, 2004 at 05:51:19AM -0700, John Cherry wrote:
> > drivers/cpufreq/cpufreq_userspace.c:157:2: warning: #warning The /proc/sys/cpu/ and sysctl interface to cpufreq will be removed from the 2.6. kernel series soon after 2005-01-01
> > drivers/cpufreq/proc_intf.c:15:2: warning: #warning This module will be removed from the 2.6. kernel series soon after 2005-01-01
>
> Um, these look like valid warnings to me, you might want to review these
> by hand before sending them out.
>
> thanks,
>
> greg k-h
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2004-08-23 23:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-23 12:51 John Cherry
2004-08-23 21:34 ` Greg KH
2004-08-23 23:02 ` John Cherry [this message]
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=1093302139.12874.143.camel@cherrybomb.pdx.osdl.net \
--to=cherry@osdl.org \
--cc=greg@kroah.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®