From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: Samuel Thibault <samuel.thibault@ens-lyon.org>,
kbuild-all@01.org, linux-input@vger.kernel.org
Subject: Re: [input:next 1215/1216] drivers/tty/vt/keyboard.c:994:2: warning: (near initialization for 'kbd_led_triggers[0].trigger')
Date: Tue, 16 Jun 2015 15:03:23 -0700 [thread overview]
Message-ID: <20150616220323.GA17610@dtor-ws> (raw)
In-Reply-To: <201506170453.xHm7stex%fengguang.wu@intel.com>
On Wed, Jun 17, 2015 at 04:02:55AM +0800, kbuild test robot wrote:
> tree: git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git next
> head: f3de1613abd5085b1f36eb6007e3484708719590
> commit: 17155b6144843281a199ef626fe294a752fd3ff5 [1215/1216] tty/vt/keyboard: define LED triggers for VT LED states
> config: x86_64-randconfig-i0-201524 (attached as .config)
> reproduce:
> git checkout 17155b6144843281a199ef626fe294a752fd3ff5
> # save the attached .config to linux build tree
> make ARCH=x86_64
>
> All warnings (new ones prefixed by >>):
>
> In file included from include/linux/list.h:8:0,
> from include/linux/module.h:9,
> from drivers/tty/vt/keyboard.c:28:
> drivers/tty/vt/keyboard.c: In function 'kbd_led_trigger_activate':
> drivers/tty/vt/keyboard.c:975:20: error: 'struct led_classdev' has no member named 'trigger'
> container_of(cdev->trigger, struct kbd_led_trigger, trigger);
I fixed it up by adding "&& IS_ENABLED(CONFIG_LEDS_TRIGGERS)" to the
ifdef block.
Thanks.
--
Dmitry
prev parent reply other threads:[~2015-06-16 22:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-16 20:02 [input:next 1215/1216] drivers/tty/vt/keyboard.c:994:2: warning: (near initialization for 'kbd_led_triggers[0].trigger') kbuild test robot
2015-06-16 22:01 ` Samuel Thibault
2015-06-16 22:03 ` Dmitry Torokhov [this message]
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=20150616220323.GA17610@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-input@vger.kernel.org \
--cc=samuel.thibault@ens-lyon.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).