From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Sebastian Capella <sebastian.capella@linaro.org>
Subject: Re: linux-next: build warning after merge of the arm tree
Date: Tue, 22 Apr 2014 09:35:24 +0100 [thread overview]
Message-ID: <20140422083524.GQ24070@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20140422103223.f16654774d15a81410eaad22@canb.auug.org.au>
On Tue, Apr 22, 2014 at 10:32:23AM +1000, Stephen Rothwell wrote:
> 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").
Yes, it's a conflict between that patch and one I pushed during the
merge window. I've asked the Sebastian to validate with his version of
virt_to_pfn() removed, and I'm waiting for the results of that...
That's partly happened, but I'm waiting for the final results.
--
FTTC broadband for 0.8mile line: now at 9.7Mbps down 460kbps up... slowly
improving, and getting towards what was expected from it.
next prev parent reply other threads:[~2014-04-22 8:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-22 0:32 Stephen Rothwell
2014-04-22 0:59 ` Sebastian Capella
2014-04-22 8:35 ` Russell King - ARM Linux [this message]
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=20140422083524.GQ24070@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sebastian.capella@linaro.org \
--cc=sfr@canb.auug.org.au \
/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®