From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Jiri Kosina <jikos@kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
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: Thu, 27 May 2021 18:52:36 +0530 [thread overview]
Message-ID: <CA+G9fYtZxQKDjHQHAbcm9cG05WJtcuv2Ld+mVspe2QXed+r+PA@mail.gmail.com> (raw)
In-Reply-To: <e5ee42f7-b0eb-40c7-e54f-8e16e8b97b68@redhat.com>
FYI,
On Thu, 27 May 2021 at 13:56, Hans de Goede <hdegoede@redhat.com> wrote:
>
> Hi,
>
> On 5/27/21 10:14 AM, Jiri Kosina wrote:
> > On Thu, 27 May 2021, Stephen Rothwell wrote:
> >
> >> After merging the hid tree, today's linux-next build (x86_64
> >> modules_install (on an allmodconfig build)) failed like this:
> >>
> >> depmod: ERROR: Cycle detected: hid -> usbhid -> hid
> >> depmod: ERROR: Found 2 modules in dependency cycles!
LKFT build system also found two types of build errors while building for arm
on today's Linux next-20210527 tag.
1)
arm-linux-gnueabihf-ld: drivers/hid/hid-core.o: in function `hid_is_usb_device':
hid-core.c:(.text+0x1f4): undefined reference to `usb_hid_driver'
make[1]: *** [/builds/linux/Makefile:1252: vmlinux] Error 1
2)
INSTALL_MOD_PATH=/home/tuxbuild/.cache/tuxmake/builds/current/modinstall
depmod: ERROR: Cycle detected: hid -> usbhid -> hid
depmod: ERROR: Found 2 modules in dependency cycles!
make[1]: *** [/builds/linux/Makefile:1875: modules_install] Error 1
> >>
> >> I could not easily figure out what caused this (it may not be the hid
> >> tree, but probably is), so all I could do was leave it broken.
> >
> > This is caused by Hans' patches (CCed). I will be dropping those today, as
> > the proper fix needs a bit more of rework.
>
> Ack, sorry about the trouble these patches are causing.
Thanks for investigating the root cause.
- Naresh
next prev parent reply other threads:[~2021-05-27 13:22 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-27 5:26 linux-next: build failure after merge of the hid tree Stephen Rothwell
2021-05-27 8:14 ` Jiri Kosina
2021-05-27 8:25 ` Hans de Goede
2021-05-27 13:22 ` Naresh Kamboju [this message]
2021-05-27 13:42 ` Jiri Kosina
-- 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
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=CA+G9fYtZxQKDjHQHAbcm9cG05WJtcuv2Ld+mVspe2QXed+r+PA@mail.gmail.com \
--to=naresh.kamboju@linaro.org \
--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 \
--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).