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]
Date:   Mon, 10 Feb 2020 10:54:37 +0100
From:   Bartosz Golaszewski <brgl@...ev.pl>
To:     sachin agarwal <asachin591@...il.com>,
        Linus Walleij <linus.walleij@...aro.org>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        "open list:GPIO SUBSYSTEM" <linux-gpio@...r.kernel.org>,
        andy@...nel.org
Subject: Re: [PATCH v2] gpio: ich: fix a typo

niedz., 9 lut 2020 o 12:16 sachin agarwal <asachin591@...il.com> napisaƂ(a):
>
> From: sachin agarwal <asachin591@...il.com>
>
> We had written "Mangagment" rather than "Management".
>
> Signed-off-by: Sachin Agarwal <asachin591@...il.com>
> ---
>  drivers/gpio/gpio-ich.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpio/gpio-ich.c b/drivers/gpio/gpio-ich.c
> index 2f086d0aa1f4..9960bb8b0f5b 100644
> --- a/drivers/gpio/gpio-ich.c
> +++ b/drivers/gpio/gpio-ich.c
> @@ -89,7 +89,7 @@ static struct {
>         struct device *dev;
>         struct gpio_chip chip;
>         struct resource *gpio_base;     /* GPIO IO base */
> -       struct resource *pm_base;       /* Power Mangagment IO base */
> +       struct resource *pm_base;       /* Power Management IO base */
>         struct ichx_desc *desc; /* Pointer to chipset-specific description */
>         u32 orig_gpio_ctrl;     /* Orig CTRL value, used to restore on exit */
>         u8 use_gpio;            /* Which GPIO groups are usable */
> --
> 2.24.1
>

I'm seeing that you have been sending a lot of these single typo
fixes. This is polluting the history and I'm not a fan of that.

Linus: what is your policy on this?

Bartosz

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ