From: Ingo Molnar <mingo@elte.hu>
To: Miles Lane <miles.lane@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.25-rc8-mm2 -- kernel/sched.c:8294: error: unknown field ‘read_uint’ specified in initializer
Date: Fri, 11 Apr 2008 15:55:55 +0200 [thread overview]
Message-ID: <20080411135555.GA14342@elte.hu> (raw)
In-Reply-To: <a44ae5cd0804110648g3256805fob917f31eeff4f6db@mail.gmail.com>
* Miles Lane <miles.lane@gmail.com> wrote:
> CC kernel/sched.o
> kernel/sched.c:8294: error: unknown field 'read_uint' specified in initializer
> kernel/sched.c:8294: warning: initialization makes integer from
> pointer without a cast
> kernel/sched.c:8295: error: unknown field 'write_uint' specified in initializer
> kernel/sched.c:8295: warning: initialization from incompatible pointer type
cannot reproduce it in sched-devel/for-akpm (which -mm is based off) nor
in sched-devel/latest, using your config. Could you check sched-devel
via:
http://people.redhat.com/mingo/sched-devel.git/README
or maybe it's some other sched.c change in -mm? That line is around the
control groups code and maybe that got changed in -mm?
meanwhile i built and successfully booted your config on a testsystem on
sched-devel/latest. So if sched-devel/latest still fails for you then
it's some build environment related detail that triggers the bug. If not
then it's other changes in -mm.
Ingo
next prev parent reply other threads:[~2008-04-11 13:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-11 13:48 2.6.25-rc8-mm2 -- kernel/sched.c:8294: error: unknown field ‘read_uint’ specified in initializer Miles Lane
2008-04-11 13:55 ` Ingo Molnar [this message]
2008-04-11 15:29 ` Miles Lane
2008-04-11 15:47 ` Miles Lane
2008-04-11 16:55 ` Peter Zijlstra
2008-04-11 18:46 ` Paul Menage
2008-04-11 18:55 ` Peter Zijlstra
2008-04-12 4:24 ` Andrew Morton
2008-04-15 2:28 ` Miles Lane
2008-04-15 2:38 ` Andrew Morton
2008-04-15 3:55 ` Miles Lane
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=20080411135555.GA14342@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miles.lane@gmail.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