All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Jiri Kosina <jikos@kernel.org>,
	Benjamin Tissoires <benjamin.tissoires@redhat.com>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Hans de Goede <hdegoede@redhat.com>
Subject: linux-next: build failure after merge of the hid tree
Date: Fri, 4 Oct 2019 10:28:44 +1000	[thread overview]
Message-ID: <20191004102844.4864a9af@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 610 bytes --]

Hi all,

After merging the hid tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:

ld: drivers/hid/hid-lg-g15.o: in function `.lg_g15_probe':
hid-lg-g15.c:(.text+0x1a1c): undefined reference to `.devm_led_classdev_register_ext'
ld: hid-lg-g15.c:(.text+0x1c68): undefined reference to `.devm_led_classdev_register_ext'

Caused by commit

  3a0275384c27 ("HID: Add driver for Logitech gaming keyboards (G15, G15 v2)")

For this build, CONFIG_HID_LOGITECH=y and CONFIG_LEDS_CLASS=m.

I have used the hid tree from next-20191003 for today.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2019-10-04  0:28 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-04  0:28 Stephen Rothwell [this message]
2019-10-04  6:55 ` linux-next: build failure after merge of the hid tree Hans de Goede
  -- strict thread matches above, loose matches on Subject: below --
2024-05-07  1:06 Stephen Rothwell
2024-05-07  7:22 ` Kenny Levinsen
2024-04-11  0:51 Stephen Rothwell
2024-04-11  7:17 ` Benjamin Tissoires
2024-02-28  3:56 Stephen Rothwell
2022-07-25  0:40 Stephen Rothwell
2022-07-25  9:42 ` Jiri Kosina
2022-07-27  1:11   ` Stephen Rothwell
2021-12-03  7:01 Stephen Rothwell
2021-12-03  8:09 ` Greg Kroah-Hartman
2021-05-27  5:26 Stephen Rothwell
2021-05-27  8:14 ` Jiri Kosina
2021-05-27  8:25   ` Hans de Goede
2021-05-27 13:22     ` Naresh Kamboju
2021-05-27 13:42     ` Jiri Kosina
2016-12-11 23:59 Stephen Rothwell
2016-12-12  8:50 ` Jiri Kosina
2012-06-29  2:47 Stephen Rothwell
2012-06-29 13:03 ` Jiri Kosina
2011-12-19  1:34 Stephen Rothwell
2011-12-19  8:21 ` Jiri Kosina
2011-11-29  1:00 Stephen Rothwell
2011-11-29  1:30 ` Jeremy Fitzhardinge
2011-06-08  3:03 Stephen Rothwell
2011-06-08  7:26 ` Stefan Kriwanek
2011-06-08  7:50   ` Jiri Kosina
2011-04-07  1:06 Stephen Rothwell
2011-04-07 13:00 ` Alan Ott
2011-04-08 23:54 ` Jiri Kosina

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=20191004102844.4864a9af@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=benjamin.tissoires@redhat.com \
    --cc=hdegoede@redhat.com \
    --cc=jikos@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.