linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
	linux-s390 <linux-s390@vger.kernel.org>
Subject: Re: linux-next: Tree for Apr 17
Date: Fri, 17 Apr 2020 09:19:58 +0200	[thread overview]
Message-ID: <aeedbf33-2dc1-0577-301d-535f49ba287e@de.ibm.com> (raw)
In-Reply-To: <20200417145017.3932443d@canb.auug.org.au>



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"


bisect points to

commit 4be5e8648b0c287aefc6ac3f3a0b12c696054f43
Author: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Date:   Wed Apr 15 11:03:40 2020 +0200

    media: move CEC platform drivers to a separate directory



> ----------------------------------------------------------------------------
> 
> I have created today's linux-next tree at
> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> (patches at http://www.kernel.org/pub/linux/kernel/next/ ).  If you
> are tracking the linux-next tree using git, you should not use "git pull"
> to do so as that will try to merge the new linux-next release with the
> old one.  You should use "git fetch" and checkout or reset to the new
> master.
> 
> You can see which trees have been included by looking in the Next/Trees
> file in the source.  There are also quilt-import.log and merge.log
> files in the Next directory.  Between each merge, the tree was built
> with a ppc64_defconfig for powerpc, an allmodconfig for x86_64, a
> multi_v7_defconfig for arm and a native build of tools/perf. After
> the final fixups (if any), I do an x86_64 modules_install followed by
> builds for x86_64 allnoconfig, powerpc allnoconfig (32 and 64 bit),
> ppc44x_defconfig, allyesconfig and pseries_le_defconfig and i386, sparc
> and sparc64 defconfig and htmldocs. And finally, a simple boot test
> of the powerpc pseries_le_defconfig kernel in qemu (with and without
> kvm enabled).
> 
> Below is a summary of the state of the merge.
> 
> I am currently merging 318 trees (counting Linus' and 78 trees of bug
> fix patches pending for the current merge release).
> 
> Stats about the size of the tree over time can be seen at
> http://neuling.org/linux-next-size.html .
> 
> Status of my local build tests will be at
> http://kisskb.ellerman.id.au/linux-next .  If maintainers want to give
> advice about cross compilers/configs that work, we are always open to add
> more builds.
> 
> Thanks to Randy Dunlap for doing many randconfig builds.  And to Paul
> Gortmaker for triage and bug fixes.
> 


  parent reply	other threads:[~2020-04-17  7:20 UTC|newest]

Thread overview: 21+ 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 ` Christian Borntraeger [this message]
2020-04-17  7:27   ` linux-next: Tree for Apr 17 Mauro Carvalho Chehab
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 --
2024-04-17  5:38 linux-next: Tree for Apr 17 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=aeedbf33-2dc1-0577-301d-535f49ba287e@de.ibm.com \
    --to=borntraeger@de.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=mchehab+huawei@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).