From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Santosh Shilimkar <santosh.shilimkar@ti.com>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: linux-next: build warnings after merge of the keystone tree
Date: Thu, 7 Dec 2017 10:38:16 +1100 [thread overview]
Message-ID: <20171207103816.06a8d2d8@canb.auug.org.au> (raw)
Hi Santosh,
After merging the keystone tree, today's linux-next build (arm
multi_v7_defconfig) produced these warnings:
arch/arm/configs/multi_v7_defconfig:843:warning: override: reassigning to symbol ARCH_TEGRA_2x_SOC
arch/arm/configs/multi_v7_defconfig:844:warning: override: reassigning to symbol ARCH_TEGRA_3x_SOC
arch/arm/configs/multi_v7_defconfig:845:warning: override: reassigning to symbol ARCH_TEGRA_114_SOC
arch/arm/configs/multi_v7_defconfig:846:warning: override: reassigning to symbol ARCH_TEGRA_124_SOC
arch/arm/configs/multi_v7_defconfig:932:warning: override: reassigning to symbol KEYSTONE_IRQ
arch/arm/configs/multi_v7_defconfig:933:warning: override: reassigning to symbol HW_RANDOM
arch/arm/configs/multi_v7_defconfig:934:warning: override: reassigning to symbol HW_RANDOM_ST
arch/arm/configs/multi_v7_defconfig:962:warning: override: reassigning to symbol VIDEO_VIVID
arch/arm/configs/multi_v7_defconfig:964:warning: override: reassigning to symbol VIRTIO_PCI
arch/arm/configs/multi_v7_defconfig:966:warning: override: reassigning to symbol VIRTIO_MMIO
Introduced by commit
0d81df335462 ("ARM: config: sync multi-v7 config with keystone peripherals")
--
Cheers,
Stephen Rothwell
reply other threads:[~2017-12-06 23:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20171207103816.06a8d2d8@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=santosh.shilimkar@ti.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;
as well as URLs for NNTP newsgroup(s).