linux-kernel - Re: [PATCH 2/2] input: s3c2410_ts: Constify platform_device

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] [day] [month] [year] [list]

Date:	Wed, 6 May 2015 16:55:47 -0700
From:	Dmitry Torokhov <dmitry.torokhov@...il.com>
To:	Krzysztof Kozlowski <k.kozlowski.k@...il.com>
Cc:	Kukjin Kim <kgene@...nel.org>, linux-input@...r.kernel.org,
	linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
	linux-samsung-soc@...r.kernel.org
Subject: Re: [PATCH 2/2] input: s3c2410_ts: Constify platform_device_id

On Sat, May 02, 2015 at 12:53:07AM +0900, Krzysztof Kozlowski wrote:
> The platform_device_id is not modified by the driver and core uses it as
> const.
> 
> Signed-off-by: Krzysztof Kozlowski <k.kozlowski.k@...il.com>
> ---
>  drivers/input/touchscreen/s3c2410_ts.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/input/touchscreen/s3c2410_ts.c b/drivers/input/touchscreen/s3c2410_ts.c
> index bdfa27dc097b..a4a103e1d11b 100644
> --- a/drivers/input/touchscreen/s3c2410_ts.c
> +++ b/drivers/input/touchscreen/s3c2410_ts.c
> @@ -411,7 +411,7 @@ static const struct dev_pm_ops s3c_ts_pmops = {
>  };
>  #endif
>  
> -static struct platform_device_id s3cts_driver_ids[] = {
> +static const struct platform_device_id s3cts_driver_ids[] = {
>  	{ "s3c2410-ts", 0 },
>  	{ "s3c2440-ts", 0 },
>  	{ "s3c64xx-ts", FEAT_PEN_IRQ },
> -- 
> 2.1.4
> 

Applied both, thank you.

-- 
Dmitry
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/