From: Greg Ungerer <gerg@snapgear.com>
To: schwidefsky@de.ibm.com
Cc: Adrian Bunk <bunk@kernel.org>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: m68knommu compile error
Date: Mon, 11 Feb 2008 15:22:11 +1000 [thread overview]
Message-ID: <47AFDB83.2010209@snapgear.com> (raw)
In-Reply-To: <1202554715.8936.18.camel@localhost>
Martin Schwidefsky wrote:
> On Sat, 2008-02-09 at 11:21 +0100, Martin Schwidefsky wrote:
>> On Sat, 2008-02-09 at 00:25 +0200, Adrian Bunk wrote:
>>> Commit 2f569afd9ced9ebec9a6eb3dbf6f83429be0a7b4 breaks m68knommu:
>> Does the patch below fixes the problem? I tried to cross compile for
>> m68knommu but it seems like you need a special m68k compiler to get it
>> compile all the way through. With the patch it did fail with a different
>> error, so I assume it is fixed. The problem is that the pgtable_t is
>> simply missing for m68knommu, I must have overlooked a reject for one of
>> the constant regenerations of the patch to keep up with upstream. Sorry
>> about that.
>
> This is a problem for all nommu architectures. The patch fixed all four
> of them.
Confirmed, good for m68knommu.
Acked-by: Greg Ungerer <gerg@uclinux.org>
--
------------------------------------------------------------------------
Greg Ungerer -- Chief Software Dude EMAIL: gerg@snapgear.com
Secure Computing Corporation PHONE: +61 7 3435 2888
825 Stanley St, FAX: +61 7 3891 3630
Woolloongabba, QLD, 4102, Australia WEB: http://www.SnapGear.com
prev parent reply other threads:[~2008-02-11 5:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-08 22:25 m68knommu compile error Adrian Bunk
2008-02-09 10:21 ` Martin Schwidefsky
2008-02-09 10:53 ` Adrian Bunk
2008-02-09 10:58 ` Martin Schwidefsky
2008-02-09 17:59 ` Mike Frysinger
2008-02-11 5:22 ` Greg Ungerer [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=47AFDB83.2010209@snapgear.com \
--to=gerg@snapgear.com \
--cc=akpm@linux-foundation.org \
--cc=bunk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=schwidefsky@de.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.