From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Geert Uytterhoeven <geert@linux-m68k•org>
Cc: linux-next@vger•kernel.org, linux-m68k@lists•linux-m68k.org,
michael@ellerman•id.au
Subject: Re: m68k: kernel/up.c:16: error: dereferencing pointer to incomplete type
Date: Fri, 13 Mar 2009 14:20:33 +1100 [thread overview]
Message-ID: <20090313142033.d69d9d2e.sfr@canb.auug.org.au> (raw)
In-Reply-To: <10f740e80903120608v314be360u30911fa003ab5ebc@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 874 bytes --]
Hi Geert,
On Thu, 12 Mar 2009 14:08:57 +0100 Geert Uytterhoeven <geert@linux-m68k•org> wrote:
>
> I can't seem to reproduce the compile failure of kernel/up.c on m68k,
> as shown on
> http://kisskb.ellerman.id.au/kisskb/buildresult/186066/:
>
> | kernel/up.c:16: error: dereferencing pointer to incomplete type
When kisskb gets an error in building a kernel, it tries to bisect the
problem starting from a known good kernel. The above error occurs
during the bisection process not when building the original kernel. I
guess we need to be a bit more careful when reporting the errors. Sorry
about that.
It was actually building commit
"[ad33ea3a8d2ec324dc0f46b6ae404d824d2b349b] bnx2x: Missing mask when
calculating flow control", I think.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-03-13 3:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-12 13:08 m68k: kernel/up.c:16: error: dereferencing pointer to incomplete type Geert Uytterhoeven
2009-03-13 3:20 ` Stephen Rothwell [this message]
2009-03-13 7:59 ` Geert Uytterhoeven
2009-03-15 9:53 ` Stephen Rothwell
2009-03-13 10:18 ` Michael Ellerman
2009-03-15 10:08 ` Stephen Rothwell
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=20090313142033.d69d9d2e.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=geert@linux-m68k$(echo .)org \
--cc=linux-m68k@lists$(echo .)linux-m68k.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=michael@ellerman$(echo .)id.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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