From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Jiri Kosina <jikos@jikos.cz>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Jeremy Fitzhardinge <jeremy@goop.org>
Subject: linux-next: build failure after merge of the hid tree
Date: Tue, 29 Nov 2011 12:00:59 +1100 [thread overview]
Message-ID: <20111129120059.a1818d7eaf663546edc6dc34@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 801 bytes --]
Hi Jiri,
After merging the hid tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
drivers/hid/hid-input.c: In function 'hidinput_hid_event':
drivers/hid/hid-input.c:865:6: error: 'struct hid_device' has no member named 'battery_val'
drivers/hid/hid-input.c:866:3: error: 'struct hid_device' has no member named 'battery_min'
drivers/hid/hid-input.c:866:3: error: 'struct hid_device' has no member named 'battery_max'
Caused by commit 4f5ca836bef3 ("HID: hid-input: add support for HID
devices reporting Battery Strength"). Those members are only defined when
CONFIG_HID_BATTERY_STRENGTH is set.
I have used the hid tree from next-20111128 for today.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2011-11-29 1:01 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-29 1:00 Stephen Rothwell [this message]
2011-11-29 1:30 ` linux-next: build failure after merge of the hid tree Jeremy Fitzhardinge
-- 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
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-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=20111129120059.a1818d7eaf663546edc6dc34@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=jeremy@goop.org \
--cc=jikos@jikos.cz \
--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;
as well as URLs for NNTP newsgroup(s).