public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Ungerer <gregungerer@westnet.com.au>
To: Richard Cochran <richardcochran@gmail.com>
Cc: linux-kernel@vger.kernel.org,
	uClinux development list <uclinux-dev@uclinux.org>,
	Greg Ungerer <gerg@uclinux.org>
Subject: Re: m68k nommu: build failure in v3.8-rc2
Date: Mon, 07 Jan 2013 11:11:43 +1000	[thread overview]
Message-ID: <50EA20CF.7050601@westnet.com.au> (raw)
In-Reply-To: <20130106122626.GA15524@netboy.at.omicron.at>

Hi Richard,

On 01/06/2013 10:26 PM, Richard Cochran wrote:
> I see the following error, using the .config inline, below.
>
> arch/m68k/mm/init.c: In function 'print_memmap':
> arch/m68k/mm/init.c:139:2: error: 'KMAP_START' undeclared (first use in this function)
> arch/m68k/mm/init.c:139:2: note: each undeclared identifier is reported only once for each function it appears in
> arch/m68k/mm/init.c:139:2: error: 'KMAP_END' undeclared (first use in this function)
>
> Looks to me like KMAP_START is only meant for the MMU case. This error
> was possibly caused by one of these two patches.
>
> $ pr v3.7.. -- arch/m68k/mm/init.c
> f50bf88 m68k: move to a single instance of free_initmem()
> dd1cb3a m68k: merge MMU and non-MMU versions of mm/init.c
>
> What is the right fix for this?

This is the planned fix:

http://marc.info/?l=linux-m68k&m=135088484810474&w=2

Well actually it was meant to go in before the above changes. I
have it queued to go to Linus soon. Just awaiting another fix
for non-mmu 68000 build issues so I can send them all together.

Regards
Greg


> ---
> #
> # Automatically generated file; DO NOT EDIT.
> # Linux/m68k 3.8.0-rc2 Kernel Configuration
> #
> CONFIG_M68K=y
> CONFIG_RWSEM_GENERIC_SPINLOCK=y
> CONFIG_GENERIC_GPIO=y
> CONFIG_GENERIC_HWEIGHT=y
> CONFIG_GENERIC_CALIBRATE_DELAY=y
> CONFIG_GENERIC_CSUM=y
> CONFIG_TIME_LOW_RES=y
> CONFIG_NO_IOPORT=y
> # CONFIG_NO_DMA is not set
> CONFIG_ZONE_DMA=y
> CONFIG_HZ=100
> CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"
>
> #
> # General setup
> #
> CONFIG_EXPERIMENTAL=y
> CONFIG_BROKEN_ON_SMP=y
> CONFIG_INIT_ENV_ARG_LIMIT=32
> CONFIG_CROSS_COMPILE=""
> CONFIG_LOCALVERSION=""
> CONFIG_LOCALVERSION_AUTO=y
> CONFIG_DEFAULT_HOSTNAME="(none)"
> # CONFIG_SYSVIPC is not set
> # CONFIG_POSIX_MQUEUE is not set
> # CONFIG_FHANDLE is not set
> # CONFIG_AUDIT is not set
> CONFIG_HAVE_GENERIC_HARDIRQS=y
>



      reply	other threads:[~2013-01-07  1:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-06 12:26 m68k nommu: build failure in v3.8-rc2 Richard Cochran
2013-01-07  1:11 ` 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=50EA20CF.7050601@westnet.com.au \
    --to=gregungerer@westnet.com.au \
    --cc=gerg@uclinux.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=richardcochran@gmail.com \
    --cc=uclinux-dev@uclinux.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