From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Russell King <linux@arm.linux.org.uk>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Sebastian Capella <sebastian.capella@linaro.org>
Subject: linux-next: build warning after merge of the arm tree
Date: Tue, 22 Apr 2014 10:32:23 +1000 [thread overview]
Message-ID: <20140422103223.f16654774d15a81410eaad22@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 927 bytes --]
Hi Russell,
After merging the arm tree, today's linux-next build (arm
multi_v7_defconfig) produced this warning:
In file included from /scratch/sfr/next/arch/arm/include/asm/page.h:163:0,
from /scratch/sfr/next/include/linux/mmzone.h:20,
from /scratch/sfr/next/include/linux/gfp.h:5,
from /scratch/sfr/next/include/linux/kmod.h:22,
from /scratch/sfr/next/include/linux/module.h:13,
from /scratch/sfr/next/init/version.c:10:
/scratch/sfr/next/arch/arm/include/asm/memory.h:297:0: warning: "virt_to_pfn" redefined [enabled by default]
/scratch/sfr/next/arch/arm/include/asm/memory.h:194:0: note: this is the location of the previous definition
Lots of these ...
Introduced by commit e2b5c192c4a6 ("ARM: 8011/1: ARM hibernation /
suspend-to-disk").
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2014-04-22 0:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-22 0:32 Stephen Rothwell [this message]
2014-04-22 0:59 ` linux-next: build warning after merge of the arm tree Sebastian Capella
2014-04-22 8:35 ` Russell King - ARM Linux
2014-04-23 16:43 ` Sebastian Capella
2014-11-18 8:25 Stephen Rothwell
2014-11-18 18:57 ` Stephen Boyd
2014-11-18 19:21 ` Russell King - ARM Linux
2014-11-18 19:43 ` Stephen Boyd
2017-11-28 23:16 Stephen Rothwell
2017-11-28 23:19 ` Russell King
2017-11-28 23:38 ` Stephen Rothwell
2017-11-28 23:41 ` Russell King
2017-11-29 6:58 ` Nicolas Pitre
2017-11-28 23:31 ` Russell King
2017-11-28 23:38 ` Nicolas Pitre
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=20140422103223.f16654774d15a81410eaad22@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=sebastian.capella@linaro.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;
as well as URLs for NNTP newsgroup(s).