LKML Archive on
help / color / mirror / Atom feed
From: Randy Dunlap <>
To: Stephen Rothwell <>,
	Linux Next Mailing List <>
Cc: Linux Kernel Mailing List <>,
	Dan Murphy <>,
Subject: Re: linux-next: Tree for May 24 (leds-lm3697)
Date: Fri, 24 May 2019 08:42:42 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 5/23/19 9:07 PM, Stephen Rothwell wrote:
> Hi all,
> News: there will be no linux-next release on Monday.
> Changes since 20190523:
> The input-current tree gained a build failure so I reverted a commit.
> The drm-fixes tree gained a build failure so I reverted a commit.
> The v4l-dvb tree gained a conflict against Linus' tree.
> Non-merge commits (relative to Linus' tree): 1814
>  1870 files changed, 61172 insertions(+), 32723 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 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 290 trees (counting Linus' and 70 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.

seen on i386:

ld: drivers/leds/leds-lm3697.o: in function `lm3697_probe':
leds-lm3697.c:(.text+0x451): undefined reference to `devm_of_led_classdev_register'


It looks to me like this is needed:

	depends on LEDS_CLASS && I2C && OF


  reply	other threads:[~2019-05-24 15:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-24  4:07 linux-next: Tree for May 24 Stephen Rothwell
2019-05-24 15:42 ` Randy Dunlap [this message]
2019-05-24 20:27   ` linux-next: Tree for May 24 (leds-lm3697) Jacek Anaszewski

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 \ \ \ \ \ \ \ \
    --subject='Re: linux-next: Tree for May 24 (leds-lm3697)' \

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

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).