linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bartosz Golaszewski <brgl@bgdev.pl>
To: sachin agarwal <asachin591@gmail.com>,
	Linus Walleij <linus.walleij@linaro.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
	andy@kernel.org
Subject: Re: [PATCH v2] gpio: ich: fix a typo
Date: Mon, 10 Feb 2020 10:54:37 +0100	[thread overview]
Message-ID: <CAMRc=Md9gsrm3OXcMgxd7DuiuZUovBB=Bcqfs7zCLApmgV6A8Q@mail.gmail.com> (raw)
In-Reply-To: <20200209111620.97423-1-sachinagarwal@sachins-MacBook-2.local>

niedz., 9 lut 2020 o 12:16 sachin agarwal <asachin591@gmail.com> napisał(a):
>
> From: sachin agarwal <asachin591@gmail.com>
>
> We had written "Mangagment" rather than "Management".
>
> Signed-off-by: Sachin Agarwal <asachin591@gmail.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

  reply	other threads:[~2020-02-10  9:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-09 11:16 [PATCH v2] gpio: ich: fix a typo sachin agarwal
2020-02-10  9:54 ` Bartosz Golaszewski [this message]
2020-02-10 10:13   ` Andy Shevchenko
2020-02-10 12:06   ` Linus Walleij

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='CAMRc=Md9gsrm3OXcMgxd7DuiuZUovBB=Bcqfs7zCLApmgV6A8Q@mail.gmail.com' \
    --to=brgl@bgdev.pl \
    --cc=andy@kernel.org \
    --cc=asachin591@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).