From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Jiri Kosina <jikos@kernel.org>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the hid tree
Date: Fri, 3 Dec 2021 09:09:39 +0100 [thread overview]
Message-ID: <YanQw3HVLzPud5gN@kroah.com> (raw)
In-Reply-To: <20211203180124.1721cbe4@canb.auug.org.au>
On Fri, Dec 03, 2021 at 06:01:24PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> After merging the hid tree, today's linux-next build (sparc defconfig)
> failed like this:
>
> hid-chicony.c:(.text+0x4): undefined reference to `usb_hid_driver'
> hid-chicony.c:(.text+0xc): undefined reference to `usb_hid_driver'
>
> Caused by commit
>
> 93020953d0fa ("HID: check for valid USB device for many HID drivers")
>
> I have marked CONFIG_HID_CHICONY as BROKEN for now.
Patch for this is at:
https://lore.kernel.org/r/20211203075927.2829218-1-gregkh@linuxfoundation.org
Looks like 0-day found another dependancy as well, in the prodikeys
hid driver, will send out a patch for that too...
thanks,
greg k-h
next prev parent reply other threads:[~2021-12-03 8:09 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-03 7:01 linux-next: build failure after merge of the hid tree Stephen Rothwell
2021-12-03 8:09 ` Greg Kroah-Hartman [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-03-02 13:56 Mark Brown
2026-03-02 15:58 ` Benjamin Tissoires
2026-03-02 17:52 ` Denis Benato
2025-02-09 23:43 Stephen Rothwell
2025-02-10 22:07 ` Jiri Kosina
2025-02-11 3:15 ` Kate Hsuan
2025-01-10 6:52 Stephen Rothwell
2024-07-01 8:51 Stephen Rothwell
2024-07-01 12:43 ` Benjamin Tissoires
2024-06-20 13:55 Mark Brown
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-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
2019-10-04 0:28 Stephen Rothwell
2019-10-04 6:55 ` Hans de Goede
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=YanQw3HVLzPud5gN@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=benjamin.tissoires@redhat.com \
--cc=jikos@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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 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.