Linux-RTC Archive on
 help / color / Atom feed
From: Randy Dunlap <>
To: Stephen Rothwell <>,
	Linux Next Mailing List <>
Cc: Linux Kernel Mailing List <>,,
	Alessandro Zummo <>,
	Alexandre Belloni <>,
	Scott Wood <>
Subject: Re: linux-next: Tree for Jul 17 (drivers/rtc/rtc-ds1374.o)
Date: Fri, 17 Jul 2020 09:49:05 -0700
Message-ID: <> (raw)
In-Reply-To: <>

On 7/17/20 4:40 AM, Stephen Rothwell wrote:
> Hi all,
> Changes since 20200716:
> New tree: init
> Changed tree: dmi (from quilt to git)
> My fixes tree contains:
>   dbf24e30ce2e ("device_cgroup: Fix RCU list debugging warning")
> I revreted 3 commits from the powerpc tree due to reported run time
> problems.
> The sound tree gained a semantic conflict against the dma-mapping tree.
> The security tree still had its build failure for which I applied a patch.
> The tip tree still had one build failure for which I reverted a commit.
> It also gained a conflict against the crypto tree
> The kvm tree gained a conflict and a semantic conflict against the
> tip tree.
> The dmaengine tree gained conflicts against the wireless-drivers-next
> and Linus' trees.
> The pinctrl tree gained a build failure so I used the version from
> next-20200716.
> The set_fs tree gained a conflict against the powerpc tree.
> The init tree gained a conflict against the block tre.
> The akpm-current tree gained conflicts against the crypto and tip trees.
> It also gained a build failure for which I applied a patch.
> Non-merge commits (relative to Linus' tree): 8001
>  8717 files changed, 441636 insertions(+), 169176 deletions(-)
> ----------------------------------------------------------------------------
> I have created today's linux-next tree at
> git://
> (patches at ).  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 325 trees (counting Linus' and 83 trees of bug
> fix patches pending for the current merge release).
> Stats about the size of the tree over time can be seen at
> .
> Status of my local build tests will be at
> .  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.

on x86_64:
# CONFIG_WATCHDOG is not set

ld: drivers/rtc/rtc-ds1374.o: in function `ds1374_probe':
rtc-ds1374.c:(.text+0x736): undefined reference to `watchdog_init_timeout'
ld: rtc-ds1374.c:(.text+0x77e): undefined reference to `devm_watchdog_register_device'

Reported-by: Randy Dunlap <>

       reply index

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2020-07-17 16:49 ` Randy Dunlap [this message]
2020-07-18  1:38   ` Stephen Rothwell
2020-07-20  3:46     ` Johnson CH Chen (陳昭勳)
2020-07-20  4:21       ` Stephen Rothwell
2020-07-20  8:12   ` Alexandre Belloni

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Linux-RTC Archive on

Archives are clonable:
	git clone --mirror linux-rtc/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-rtc linux-rtc/ \
	public-inbox-index linux-rtc

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone