From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-s390 <linux-s390@vger.kernel.org>
Subject: Re: linux-next: Tree for Apr 17
Date: Fri, 17 Apr 2020 09:27:25 +0200 [thread overview]
Message-ID: <20200417092725.4876a832@coco.lan> (raw)
In-Reply-To: <aeedbf33-2dc1-0577-301d-535f49ba287e@de.ibm.com>
Em Fri, 17 Apr 2020 09:19:58 +0200
Christian Borntraeger <borntraeger@de.ibm.com> escreveu:
> On 17.04.20 06:50, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20200416:
> >
> > My fixes tree contains:
> >
> > 6b038bdcd3d1 sh: mm: Fix build error
> >
> > The qcom tree still had its build failure for which I reverted a commit.
> >
> > The sound-asoc tree still has its failures so I used the version from
> > next-20200414.
> >
> > The crypto tree gained a build failure for which I reverted 5 commits.
> >
> > Non-merge commits (relative to Linus' tree): 2255
> > 3007 files changed, 64848 insertions(+), 29193 deletions(-)
> >
>
>
> This fails for s390 already in kconfig
>
> $ make defconfig
> *** Default configuration is based on 'defconfig'
> drivers/pci/Kconfig:16:error: recursive dependency detected!
> drivers/pci/Kconfig:16: symbol PCI is selected by CEC_SECO
> drivers/media/cec/platform/Kconfig:100: symbol CEC_SECO depends on MEDIA_CEC_SUPPORT
> drivers/media/cec/Kconfig:27: symbol MEDIA_CEC_SUPPORT default is visible depending on MEDIA_SUPPORT_FILTER
> drivers/media/Kconfig:25: symbol MEDIA_SUPPORT_FILTER depends on MEDIA_SUPPORT
> drivers/media/Kconfig:12: symbol MEDIA_SUPPORT depends on HAS_IOMEM
> arch/s390/Kconfig:722: symbol HAS_IOMEM default value contains PCI
> For a resolution refer to Documentation/kbuild/kconfig-language.rst
> subsection "Kconfig recursive dependency limitations"
Just pushed a patch addressing the reported Kconfig issues on media.
Sorry for the Kconfig noise. We did a major rework at media Kconfig, with
has a very complex dependency chain.
Thanks,
Mauro
next prev parent reply other threads:[~2020-04-17 7:27 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-17 4:50 linux-next: Tree for Apr 17 Stephen Rothwell
2020-04-17 6:16 ` linux-next: Tree for Apr 17 (pinctrl-mcp23s08) Randy Dunlap
2020-04-17 10:22 ` Linus Walleij
2020-04-17 7:19 ` linux-next: Tree for Apr 17 Christian Borntraeger
2020-04-17 7:27 ` Mauro Carvalho Chehab [this message]
2020-04-17 14:48 ` linux-next: Tree for Apr 17 (mmc/host/sdhci-of-at91.c) Randy Dunlap
2020-04-20 9:12 ` Ulf Hansson
2020-04-20 10:28 ` Adrian Hunter
2020-04-20 12:27 ` Masahiro Yamada
2020-04-20 13:45 ` Adrian Hunter
2020-04-22 10:15 ` Ulf Hansson
2020-04-22 10:54 ` Masahiro Yamada
2020-04-17 15:23 ` linux-next: Tree for Apr 17 (drivers/char/hw_random/cctrng.c) Randy Dunlap
2020-04-17 20:14 ` Hadar Gat
-- strict thread matches above, loose matches on Subject: below --
2025-04-17 7:41 linux-next: Tree for Apr 17 Stephen Rothwell
2024-04-17 5:38 Stephen Rothwell
2023-04-17 17:48 broonie
2019-04-17 7:31 Stephen Rothwell
2018-04-17 4:25 Stephen Rothwell
2014-04-17 7:35 Stephen Rothwell
2013-04-17 7:04 Stephen Rothwell
2012-04-17 4:42 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=20200417092725.4876a832@coco.lan \
--to=mchehab+huawei@kernel.org \
--cc=borntraeger@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-s390@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).