From: "Miles Lane" <miles.lane@gmail.com>
To: "Andrew Morton" <akpm@linux-foundation.org>
Cc: "Peter Zijlstra" <peterz@infradead.org>,
"Paul Menage" <menage@google.com>,
LKML <linux-kernel@vger.kernel.org>,
"Ingo Molnar" <mingo@elte.hu>
Subject: Re: 2.6.25-rc8-mm2 -- kernel/sched.c:8294: error: unknown field ‘read_uint’ specified in initializer
Date: Mon, 14 Apr 2008 23:55:32 -0400 [thread overview]
Message-ID: <a44ae5cd0804142055tb955431ne904862043a01d6d@mail.gmail.com> (raw)
In-Reply-To: <20080414193855.74ea0d88.akpm@linux-foundation.org>
On Mon, Apr 14, 2008 at 10:38 PM, Andrew Morton
<akpm@linux-foundation.org> wrote:
> On Mon, 14 Apr 2008 22:28:27 -0400 "Miles Lane" <miles.lane@gmail.com> wrote:
>
> > Hmm. This is showing up in 2.6.25-rc9 and looks related to the
> > problem in 2.6.25-rc9-mm2:
> >
> > CC kernel/sched.o
> > kernel/sched.c:7988: error: unknown field 'read_u64' specified in initializer
> > kernel/sched.c:7988: error: 'cpu_shares_read_u64' undeclared here (not
> > in a function)
> > kernel/sched.c:7989: error: unknown field 'write_u64' specified in initializer
> > kernel/sched.c:7989: error: 'cpu_shares_write_u64' undeclared here
> > (not in a function)
> > kernel/sched.c:7995: error: unknown field 'read_s64' specified in initializer
> > kernel/sched.c:7995: warning: initialization makes integer from
> > pointer without a cast
> > kernel/sched.c:7996: error: unknown field 'write_s64' specified in initializer
> > kernel/sched.c:7996: warning: initialization from incompatible pointer type
> > kernel/sched.c:8000: error: 'cpu_rt_period_read_uint' undeclared here
> > (not in a function)
> > kernel/sched.c:8001: error: 'cpu_rt_period_write_uint' undeclared here
> > (not in a function)
>
> I'm suspecting that you applied the -mm patch, then you applied
> cgroup-api-files-rename-read-write_uint-methods-to-read_write_u64-fix.patch,
> then you reverted the -mm patch but didn't revert
> cgroup-api-files-rename-read-write_uint-methods-to-read_write_u64-fix.patch.
>
Hmm. Bizarro. I have no recollection of applying such a patch, but maybe
I need to get some more sleep. I just downloaded the whole 2.6.25-rc9
tarball and lo and behold, it worked.
Sorry for the noise,
Miles
prev parent reply other threads:[~2008-04-15 3:55 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
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 [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=a44ae5cd0804142055tb955431ne904862043a01d6d@mail.gmail.com \
--to=miles.lane@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=menage@google.com \
--cc=mingo@elte.hu \
--cc=peterz@infradead.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