mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Jiri Kosina <jikos@kernel.org>,
	Benjamin Tissoires <benjamin.tissoires@redhat.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build failure after merge of the hid tree
Date: Fri, 20 Nov 2026 14:55:26 +0000	[thread overview]
Message-ID: <awBfXhrj8dYTa53z@sirena.org.uk> (raw)

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

Hi all,

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

/tmp/next/build/drivers/hid/hid-logitech-hidpp.c:4714:4: error: call to undeclared function 'hidinput_disconnect'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
 4714 |                         hidinput_disconnect(hdev);
      |                         ^
/tmp/next/build/drivers/hid/hid-logitech-hidpp.c:4714:4: note: did you mean 'hid_disconnect'?
/tmp/next/build/include/linux/hid.h:1051:6: note: 'hid_disconnect' declared here
 1051 | void hid_disconnect(struct hid_device *hid);
      |      ^
1 error generated.

Caused by commit

   a9c54220eaab7 (HID: logitech-hidpp: disable works before stopping transport)

I have used the tree from next-20261119 instead.

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

             reply	other threads:[~2026-11-20 14:55 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-20 14:55 Mark Brown [this message]
2026-11-20 15:00 ` Jiri Kosina
  -- strict thread matches above, loose matches on Subject: below --
2026-10-16 12:17 Mark Brown
2026-10-16 12:32 ` Jiri Kosina
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-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
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=awBfXhrj8dYTa53z@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=benjamin.tissoires@redhat.com \
    --cc=dmitry.torokhov@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®