From: Laura Abbott <lauraa@codeaurora.org>
To: kbuild test robot <fengguang.wu@intel.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Linux Memory Management List <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
kbuild-all@01.org
Subject: Re: [next:master 103/113] arch/powerpc/platforms/52xx/efika.c:210:2: error: 'ISA_DMA_THRESHOLD' undeclared
Date: Wed, 16 Apr 2014 09:28:57 -0700 [thread overview]
Message-ID: <534EAFC9.8010702@codeaurora.org> (raw)
In-Reply-To: <534e3806.dEDbrOl+B+miaF+8%fengguang.wu@intel.com>
On 4/16/2014 12:57 AM, kbuild test robot wrote:
> tree: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: 2db08cc65391d73dc8cbcaefdb55c42a774d9e1a
> commit: ff35bd54456e18878c361a8a2deeb41c9688458f [103/113] lib/scatterlist: make ARCH_HAS_SG_CHAIN an actual Kconfig
> config: make ARCH=powerpc ppc6xx_defconfig
>
> All error/warnings:
>
> arch/powerpc/platforms/52xx/efika.c: In function 'efika_probe':
>>> arch/powerpc/platforms/52xx/efika.c:210:2: error: 'ISA_DMA_THRESHOLD' undeclared (first use in this function)
> ISA_DMA_THRESHOLD = ~0L;
> ^
> arch/powerpc/platforms/52xx/efika.c:210:2: note: each undeclared identifier is reported only once for each function it appears in
>>> arch/powerpc/platforms/52xx/efika.c:211:2: error: 'DMA_MODE_READ' undeclared (first use in this function)
> DMA_MODE_READ = 0x44;
> ^
>>> arch/powerpc/platforms/52xx/efika.c:212:2: error: 'DMA_MODE_WRITE' undeclared (first use in this function)
> DMA_MODE_WRITE = 0x48;
> ^
Another fixup needed (should cover errors from other generated config as well)
---- 8< ----
prev parent reply other threads:[~2014-04-16 16:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-16 7:57 [next:master 103/113] arch/powerpc/platforms/52xx/efika.c:210:2: error: 'ISA_DMA_THRESHOLD' undeclared kbuild test robot
2014-04-16 16:28 ` Laura Abbott [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=534EAFC9.8010702@codeaurora.org \
--to=lauraa@codeaurora.org \
--cc=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.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 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.