From: Michael Ellerman <michael@ellerman.id.au>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
linux-next@vger.kernel.org, linux-m68k@lists.linux-m68k.org
Subject: Re: m68k: kernel/up.c:16: error: dereferencing pointer to incomplete type
Date: Fri, 13 Mar 2009 21:18:20 +1100 [thread overview]
Message-ID: <1236939500.11012.1.camel@localhost> (raw)
In-Reply-To: <20090313142033.d69d9d2e.sfr@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 1031 bytes --]
On Fri, 2009-03-13 at 14:20 +1100, Stephen Rothwell wrote:
> 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.
Yeah sorry that is confusing.
Should be fixed now.
cheers
--
Michael Ellerman
OzLabs, IBM Australia Development Lab
wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)
We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-03-13 10:18 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
2009-03-13 7:59 ` Geert Uytterhoeven
2009-03-15 9:53 ` Stephen Rothwell
2009-03-13 10:18 ` Michael Ellerman [this message]
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=1236939500.11012.1.camel@localhost \
--to=michael@ellerman.id.au \
--cc=geert@linux-m68k.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).