mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Greg KH <greg@kroah.com>
Cc: Subrata Modak <subrata@linux.vnet.ibm.com>,
	Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>,
	Michael Ellerman <michael@ellerman.id.au>,
	Sachin P Sant <sachinp@linux.vnet.ibm.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux-Next <linux-next@vger.kernel.org>,
	Linux-Kernel <linux-kernel@vger.kernel.org>,
	Linuxppc-dev <Linuxppc-dev@ozlabs.org>
Subject: Re: [BUILD FAILURE 01/04] Next June 04:PPC64 randconfig  [drivers/staging/comedi/drivers.o]
Date: Thu, 4 Jun 2009 22:40:47 +0200	[thread overview]
Message-ID: <10f740e80906041340x4f51b5f0ra542b60d758a4b54@mail.gmail.com> (raw)
In-Reply-To: <20090604180736.GA24902@kroah.com>

On Thu, Jun 4, 2009 at 20:07, Greg KH <greg@kroah.com> wrote:
> On Thu, Jun 04, 2009 at 07:01:32PM +0530, Subrata Modak wrote:
>> CC [M]  drivers/staging/comedi/drivers.o
>> drivers/staging/comedi/drivers.c: In function ‘comedi_buf_alloc’:
>> drivers/staging/comedi/drivers.c:496: error: ‘PAGE_KERNEL_NOCACHE’ undeclared (first use in this function)
>> drivers/staging/comedi/drivers.c:496: error: (Each undeclared identifier is reported only once
>> drivers/staging/comedi/drivers.c:496: error: for each function it appears in.)
>> make[3]: *** [drivers/staging/comedi/drivers.o] Error 1
>> make[2]: *** [drivers/staging/comedi] Error 2
>> make[1]: *** [drivers/staging] Error 2
>> make: *** [drivers] Error 2
>>
>> Is it still normal to expect this failure ?
>
> No.
>
>> I reported them long back during April:
>> http://www.gossamer-threads.com/lists/linux/kernel/1065227,
>
> Yes, and I took some patches that were supposed to fix this.  I can't
> duplicate this here, care to send a patch that would fix it?

PAGE_KERNEL_NOCACHE is defined on a few architectures only, namely
frv, m32r, mn10300, sh, and x86[*]. On all others, it will fail.

[*] Interestingly, sparc refers to it in one of its include files,
without providing a
    definition, Probably that code is unused.

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds

  reply	other threads:[~2009-06-04 20:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-04 13:31 Subrata Modak
2009-06-04 18:07 ` Greg KH
2009-06-04 20:40   ` Geert Uytterhoeven [this message]
2009-06-05 18:26 Subrata Modak
2009-06-05 18:26 ` Greg KH
2009-06-05 23:31   ` Benjamin Herrenschmidt
2009-06-05 23:32 ` Benjamin Herrenschmidt
2009-06-06  0:56   ` David Miller
2009-06-06  4:16     ` Benjamin Herrenschmidt
2009-06-06  5:51       ` Greg KH
2009-06-06 13:36         ` Frank Mori Hess
2009-06-07 14:36           ` Subrata Modak
2009-06-09  3:50             ` Benjamin Herrenschmidt
2009-06-09 18:34               ` Subrata Modak
2009-06-09 18:54                 ` Geert Uytterhoeven
2009-06-09 22:34                 ` Benjamin Herrenschmidt

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=10f740e80906041340x4f51b5f0ra542b60d758a4b54@mail.gmail.com \
    --to=geert@linux-m68k.org \
    --cc=Geert.Uytterhoeven@sonycom.com \
    --cc=Linuxppc-dev@ozlabs.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=michael@ellerman.id.au \
    --cc=sachinp@linux.vnet.ibm.com \
    --cc=sfr@canb.auug.org.au \
    --cc=subrata@linux.vnet.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®