All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Uwe Kleine-König (The Capable Hub)" <u.kleine-koenig@baylibre.com>
To: Jiri Kosina <jikos@kernel.org>,  Benjamin Tissoires <bentiss@kernel.org>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] HID: Fix comment about header defining HID_GROUP_ANY
Date: Wed, 11 Nov 2026 19:24:12 +0100	[thread overview]
Message-ID: <avSynjK8ZIxQ3Wfs@monoceros> (raw)
In-Reply-To: <20260730204136.1606050-2-u.kleine-koenig@baylibre.com>

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

Hello,

On Thu, Jul 30, 2026 at 10:41:36PM +0200, Uwe Kleine-König (The Capable Hub) wrote:
> Since commit ad428f5811bd ("mod_devicetable.h: Split into per subsystem
> headers") HID_GROUP_ANY isn't defined in linux/mod_devicetable.h
> (directly) any more. Fix the comment accordingly.
> 
> Signed-off-by: Uwe Kleine-König (The Capable Hub) <u.kleine-koenig@baylibre.com>
> ---
>  include/linux/hid.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/include/linux/hid.h b/include/linux/hid.h
> index b240baa95ab5..56bd7f274387 100644
> --- a/include/linux/hid.h
> +++ b/include/linux/hid.h
> @@ -424,7 +424,7 @@ struct hid_item {
>  /*
>   * HID device groups
>   *
> - * Note: HID_GROUP_ANY is declared in linux/mod_devicetable.h
> + * Note: HID_GROUP_ANY is declared in <linux/device-id/hid.h>
>   * and has a value of 0x0000
>   */
>  #define HID_GROUP_GENERIC			0x0001
> 
> base-commit: 95d6a9ccef99117115e41e9adb271243bd5e985b

This patch still applies to next-20261110. Is it still on someone's
radar?

Best regards
Uwe

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

      reply	other threads:[~2026-11-11 18:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-30 20:41 [PATCH] HID: Fix comment about header defining HID_GROUP_ANY Uwe Kleine-König (The Capable Hub)
2026-11-11 18:24 ` Uwe Kleine-König (The Capable Hub) [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=avSynjK8ZIxQ3Wfs@monoceros \
    --to=u.kleine-koenig@baylibre.com \
    --cc=bentiss@kernel.org \
    --cc=jikos@kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.