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>
Subject: Re: linux-next: build failures after merge of the hid tree
Date: Tue, 23 Jun 2020 10:37:36 +1000 [thread overview]
Message-ID: <20200623103736.25f67de5@canb.auug.org.au> (raw)
In-Reply-To: <20200621140421.7f4552df@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 1084 bytes --]
Hi all,
On Sun, 21 Jun 2020 14:04:21 +1000 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>
> After merging the hid tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
>
> drivers/hid/intel-ish-hid/ipc/ipc.c:12:10: fatal error: client.h: No such file or directory
> 12 | #include "client.h"
> | ^~~~~~~~~~
> drivers/hid/intel-ish-hid/ipc/pci-ish.c:22:10: fatal error: ishtp-dev.h: No such file or directory
> 22 | #include "ishtp-dev.h"
> | ^~~~~~~~~~~~~
>
> I don't know what caused it, but commit
>
> 470376737e88 ("HID: allow building hid.ko as an external module")
>
> did not fix it. BTW, I build with "make O=...".
>
> I have used the hid tree from next-20200618 for today.
>
> BTW, the hid tree really needs cleaning up, it contains merge commits dating
> back to April 2018 :-(
>
> $ git rev-list --count origin/master..hid/for-next
> 301
> $ git rev-list --no-merges --count origin/master..hid/for-next
> 12
I am still getting this failure.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-06-23 0:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-21 4:04 linux-next: build failures after merge of the hid tree Stephen Rothwell
2020-06-23 0:37 ` Stephen Rothwell [this message]
2020-06-23 14:24 ` Benjamin Tissoires
2020-06-23 22:13 ` Jiri Kosina
2020-06-24 2:27 ` Nathan Chancellor
2020-06-24 7:30 ` Jiri Kosina
2020-06-24 8:01 ` Cristian Klein
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=20200623103736.25f67de5@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=benjamin.tissoires@redhat$(echo .)com \
--cc=jikos@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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