Linux USB
 help / color / mirror / Atom feed
From: Hans de Goede <hansg@kernel.org>
To: Sakari Ailus <sakari.ailus@linux.intel.com>, linux-usb@vger.kernel.org
Cc: Lixu Zhang <lixu.zhang@intel.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH 1/2] usb: ljca: Order ACPI hardware IDs alphabetically
Date: Fri, 10 Oct 2025 15:42:19 +0200	[thread overview]
Message-ID: <c5813aef-a09c-401d-96fd-41da92beb9ec@kernel.org> (raw)
In-Reply-To: <20251010055625.4147844-1-sakari.ailus@linux.intel.com>

Hi,

On 10-Oct-25 7:56 AM, Sakari Ailus wrote:
> The driver has three lists of ACPI hardware IDs, for GPIO, I²C and SPI.
> Order them alphabetically.
> 
> Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>

Thanks, patch looks good to me:

Reviewed-by: Hans de Goede <hansg@kernel.org>

Note 1 remark to maybe be addressed in a separate patch
below.



> ---
>  drivers/usb/misc/usb-ljca.c | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/usb/misc/usb-ljca.c b/drivers/usb/misc/usb-ljca.c
> index c562630d862c..cf01cc727685 100644
> --- a/drivers/usb/misc/usb-ljca.c
> +++ b/drivers/usb/misc/usb-ljca.c
> @@ -165,26 +165,26 @@ struct ljca_match_ids_walk_data {
>  };
>  
>  static const struct acpi_device_id ljca_gpio_hids[] = {
> +	{ "INTC100B" },
>  	{ "INTC1074" },
>  	{ "INTC1096" },
> -	{ "INTC100B" },
> -	{ "INTC10D1" },
>  	{ "INTC10B5" },

This "INTC10B5" looks weird here, I don't think this actually
is in use. As can be seen by the matching "INTC10B6" HID
missing from ljca_i2c_hids[]. if we really needed "INTC10B5"
then I would expect "INTC10B6" to also be in the i2c list.

Regards,

Hans




> +	{ "INTC10D1" },
>  	{},
>  };
>  
>  static const struct acpi_device_id ljca_i2c_hids[] = {
> +	{ "INTC100C" },
>  	{ "INTC1075" },
>  	{ "INTC1097" },
> -	{ "INTC100C" },
>  	{ "INTC10D2" },
>  	{},
>  };
>  
>  static const struct acpi_device_id ljca_spi_hids[] = {
> +	{ "INTC100D" },
>  	{ "INTC1091" },
>  	{ "INTC1098" },
> -	{ "INTC100D" },
>  	{ "INTC10D3" },
>  	{},
>  };


  parent reply	other threads:[~2025-10-10 13:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-10  5:56 [PATCH 1/2] usb: ljca: Order ACPI hardware IDs alphabetically Sakari Ailus
2025-10-10  5:56 ` [PATCH 2/2] usb: ljca: Improve ACPI hardware ID documentation Sakari Ailus
2025-10-10 13:42   ` Hans de Goede
2025-10-10 13:42 ` Hans de Goede [this message]
2025-10-10 14:59 ` [PATCH 1/2] usb: ljca: Order ACPI hardware IDs alphabetically Alan Stern
2025-10-13  7:26 ` Greg Kroah-Hartman

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=c5813aef-a09c-401d-96fd-41da92beb9ec@kernel.org \
    --to=hansg@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=lixu.zhang@intel.com \
    --cc=sakari.ailus@linux.intel.com \
    /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