linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hans de Goede <hansg@kernel.org>
To: kernel test robot <lkp@intel.com>, "Leo L. Schwab" <ewhac@ewhac.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	Kate Hsuan <hpa@redhat.com>, Jiri Kosina <jikos@kernel.org>,
	Benjamin Tissoires <bentiss@kernel.org>,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5] HID: lg-g15 - Add support for Logitech G13.
Date: Tue, 2 Sep 2025 22:47:48 +0200	[thread overview]
Message-ID: <9600871d-7a68-4e7e-8cc1-5280af554378@kernel.org> (raw)
In-Reply-To: <202509030200.ITZPZGmG-lkp@intel.com>

Hi,

On 2-Sep-25 21:46, kernel test robot wrote:
> Hi Leo,
> 
> kernel test robot noticed the following build errors:
> 
> [auto build test ERROR on hid/for-next]
> [also build test ERROR on linus/master v6.17-rc4 next-20250902]
> [If your patch is applied to the wrong git tree, kindly drop us a note.
> And when submitting patch, we suggest to use '--base' as documented in
> https://git-scm.com/docs/git-format-patch#_base_tree_information]
> 
> url:    https://github.com/intel-lab-lkp/linux/commits/Leo-L-Schwab/HID-lg-g15-Add-support-for-Logitech-G13/20250902-091504
> base:   https://git.kernel.org/pub/scm/linux/kernel/git/hid/hid.git for-next
> patch link:    https://lore.kernel.org/r/20250902003659.361934-2-ewhac%40ewhac.org
> patch subject: [PATCH v5] HID: lg-g15 - Add support for Logitech G13.
> config: i386-buildonly-randconfig-006-20250902 (https://download.01.org/0day-ci/archive/20250903/202509030200.ITZPZGmG-lkp@intel.com/config)
> compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250903/202509030200.ITZPZGmG-lkp@intel.com/reproduce)
> 
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202509030200.ITZPZGmG-lkp@intel.com/
> 
> All errors (new ones prefixed by >>):
> 
>>> drivers/hid/hid-lg-g15.c:692:30: error: no member named 'brightness_hw_changed' in 'struct led_classdev'
>      692 |                                            ^ (g15->leds[0].cdev.brightness_hw_changed > 0);
>          |                                               ~~~~~~~~~~~~~~~~~ ^
>    1 error generated.

Ah right, IS_ENABLED() only helps to avoid errors about references which
are resolved link-time and this is a compile-time issue.

But as discussed in the v3 thread we don't want to use 
cdev.brightness_hw_changed anyways.

Regards,

Hans


> 
> vim +692 drivers/hid/hid-lg-g15.c
> 
>    655	
>    656	static int lg_g13_event(struct lg_g15_data *g15, u8 const *data)
>    657	{
>    658		struct g13_input_report const * const rep = (struct g13_input_report *) data;
>    659		int i, val;
>    660	
>    661		/*
>    662		 * Main macropad and menu keys.
>    663		 * Emit key events defined for each bit position.
>    664		 */
>    665		for (i = 0; i < ARRAY_SIZE(g13_keys_for_bits); ++i) {
>    666			if (g13_keys_for_bits[i]) {
>    667				val = TEST_BIT(rep->keybits, i);
>    668				input_report_key(g15->input, g13_keys_for_bits[i], val);
>    669			}
>    670		}
>    671		input_sync(g15->input);
>    672	
>    673		/*
>    674		 * Joystick.
>    675		 * Emit button and deflection events.
>    676		 */
>    677		for (i = 0; i < ARRAY_SIZE(g13_keys_for_bits_js); ++i) {
>    678			val = TEST_BIT(rep->keybits, i + G13_JS_KEYBITS_OFFSET);
>    679			input_report_key(g15->input_js, g13_keys_for_bits_js[i], val);
>    680		}
>    681		input_report_abs(g15->input_js, ABS_X, rep->joy_x);
>    682		input_report_abs(g15->input_js, ABS_Y, rep->joy_y);
>    683		input_sync(g15->input_js);
>    684	
>    685		if (IS_ENABLED(CONFIG_LEDS_BRIGHTNESS_HW_CHANGED)) {
>    686			/*
>    687			 * Bit 23 of keybits[] reports the current backlight on/off
>    688			 * state.  If it has changed from the last cached value, apply
>    689			 * an update.
>    690			 */
>    691			bool hw_brightness_changed = (!!TEST_BIT(rep->keybits, 23))
>  > 692						   ^ (g15->leds[0].cdev.brightness_hw_changed > 0);
>    693			if (hw_brightness_changed)
>    694				led_classdev_notify_brightness_hw_changed(
>    695					&g15->leds[0].cdev,
>    696					TEST_BIT(rep->keybits, 23) ? LED_FULL : LED_OFF);
>    697		}
>    698	
>    699		return 0;
>    700	}
>    701	
> 


      reply	other threads:[~2025-09-02 20:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-02  0:36 [PATCH v5] HID: lg-g15 - Add support for Logitech G13 Leo L. Schwab
2025-09-02  9:14 ` Hans de Goede
2025-09-02 19:46 ` kernel test robot
2025-09-02 20:47   ` Hans de Goede [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=9600871d-7a68-4e7e-8cc1-5280af554378@kernel.org \
    --to=hansg@kernel.org \
    --cc=bentiss@kernel.org \
    --cc=ewhac@ewhac.org \
    --cc=hpa@redhat.com \
    --cc=jikos@kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    --cc=oe-kbuild-all@lists.linux.dev \
    /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).