From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Colin Cross <ccross@android.com>, Olof Johansson <olof@lixom.net>,
Thierry Reding <treding@nvidia.com>
Cc: Dmitry Osipenko <digetx@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build warning after merge of the tegra tree
Date: Thu, 3 Jun 2021 10:35:07 +1000 [thread overview]
Message-ID: <20210603103507.304b7626@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 526 bytes --]
Hi all,
After merging the tegra tree, today's linux-next build (x86_64
allmodconfig) produced this warning:
WARNING: unmet direct dependencies detected for TEGRA210_EMC_TABLE
Depends on [n]: MEMORY [=y] && TEGRA_MC [=y] && ARCH_TEGRA_210_SOC [=n]
Selected by [m]:
- TEGRA210_EMC [=m] && MEMORY [=y] && TEGRA_MC [=y] && (ARCH_TEGRA_210_SOC [=n] || COMPILE_TEST [=y])
Probably introduced by commit
08decdd5b448 ("memory: tegra: Enable compile testing for all drivers")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2021-06-03 0:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-03 0:35 Stephen Rothwell [this message]
2021-06-03 2:01 ` linux-next: build warning after merge of the tegra tree Dmitry Osipenko
2021-06-03 12:18 ` Thierry Reding
2021-06-03 14:03 ` Dmitry Osipenko
2021-06-03 14:35 ` Thierry Reding
2021-06-03 14:37 ` Dmitry Osipenko
-- strict thread matches above, loose matches on Subject: below --
2023-07-21 3:07 Stephen Rothwell
2022-06-26 23:15 Stephen Rothwell
2022-06-27 11:53 ` Jon Hunter
2015-05-07 4:06 Stephen Rothwell
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=20210603103507.304b7626@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=ccross@android.com \
--cc=digetx@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=olof@lixom.net \
--cc=treding@nvidia.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