linux-kernel - Re: [PATCH v2] extcon: gpio: Fix typo in comment (cosmetic)

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:	Tue, 29 Dec 2015 09:32:31 +0900
From:	Chanwoo Choi <cw00.choi@...sung.com>
To:	Moritz Fischer <moritz.fischer@...us.com>, myungjoo.ham@...sung.com
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] extcon: gpio: Fix typo in comment (cosmetic)

Hi Moritz,

On 2015년 12월 24일 14:34, Moritz Fischer wrote:
> Signed-off-by: Moritz Fischer <moritz.fischer@...us.com>
> ---
>  drivers/extcon/extcon-gpio.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/extcon/extcon-gpio.c b/drivers/extcon/extcon-gpio.c
> index 279ff8f..d023789 100644
> --- a/drivers/extcon/extcon-gpio.c
> +++ b/drivers/extcon/extcon-gpio.c
> @@ -126,7 +126,7 @@ static int gpio_extcon_probe(struct platform_device *pdev)
>  	INIT_DELAYED_WORK(&data->work, gpio_extcon_work);
>  
>  	/*
> -	 * Request the interrput of gpio to detect whether external connector
> +	 * Request the interrupt of gpio to detect whether external connector
>  	 * is attached or detached.
>  	 */
>  	ret = devm_request_any_context_irq(&pdev->dev, data->irq,
> 

Applied it.

I drop the '(cosmetic)' word from patch title
and add the simple patch description as following:

"
This patch fixes the typo in comment of extcon-gpio.c driver.
    - 'interrput' -> 'interrupt'
"

Thanks,
Chanwoo Choi

--
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/