linux-kernel - Re: [PATCH v4 17/17] fsi: scom: Update compatible string to match documentation

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <c722d3d6-2acb-4669-b541-eebaf71b3a04@kernel.org>
Date: Tue, 30 Apr 2024 09:37:30 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Eddie James <eajames@...ux.ibm.com>, linux-aspeed@...ts.ozlabs.org
Cc: devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
 linux-fsi@...ts.ozlabs.org, linux-spi@...r.kernel.org,
 linux-i2c@...r.kernel.org, lakshmiy@...ibm.com, robh@...nel.org,
 krzk+dt@...nel.org, conor+dt@...nel.org, joel@....id.au,
 andrew@...econstruct.com.au, andi.shyti@...nel.org
Subject: Re: [PATCH v4 17/17] fsi: scom: Update compatible string to match
 documentation

On 29/04/2024 23:01, Eddie James wrote:
> Use p9-scom instead of fsi2pib.

Why? Commits must *always* say why you are doing it. What is easy to see.

> 
> Signed-off-by: Eddie James <eajames@...ux.ibm.com>
> ---
>  drivers/fsi/fsi-scom.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/fsi/fsi-scom.c b/drivers/fsi/fsi-scom.c
> index 61dbda9dbe2b..18ca213fdc7e 100644
> --- a/drivers/fsi/fsi-scom.c
> +++ b/drivers/fsi/fsi-scom.c
> @@ -589,7 +589,7 @@ static int scom_remove(struct device *dev)
>  }
>  
>  static const struct of_device_id scom_of_ids[] = {
> -	{ .compatible = "ibm,fsi2pib" },
> +	{ .compatible = "ibm,p9-scom" },

This breaks all users without any explanation in the commit!

Best regards,
Krzysztof