All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bartosz Golaszewski <bgolaszewski@baylibre.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Abanoub Sameh <abanoubsameh8@gmail.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Abanoub Sameh <abanoubsameh@protonmail.com>
Subject: Re: [PATCH] gpio: gpio-crystalcove.c: changed every 'unsigned' to 'unsigned int'
Date: Wed, 19 Aug 2020 19:56:07 +0200	[thread overview]
Message-ID: <CAMpxmJVW0yXdVVxYYiNjHw5XsKx+cyb6hV7KTeOQBxgFJWWx4w@mail.gmail.com> (raw)
In-Reply-To: <CAHp75VdFvAYR+z8c6R2J9Q2JK-WpHS4LU_-cWvsOa2g8+Gfk9w@mail.gmail.com>

On Tue, Jul 21, 2020 at 6:05 PM Andy Shevchenko
<andy.shevchenko@gmail.com> wrote:
>
> On Tue, Jul 21, 2020 at 5:49 PM Abanoub Sameh <abanoubsameh8@gmail.com> wrote:
> >
> > Changed 'unsigned' to 'unsigned int'.
> > This makes the code more uniform, and compliant with the kernel coding style.
>
> In all patches you wrongly added 'gpio-' and '.c' parts. Also you
> missed the version of the patches (I have told you about) and
> changelog.
>
> No need to resend, I fixed that this time for you. Be careful in the future.
>
> --
> With Best Regards,
> Andy Shevchenko

Hi Andy,

I was going through pending patches and noticed those from Abanoub:
are you also the maintainer for gpio-crystalcove and gpio-msic? The
MAINTAINERS entry for Intel GPIO drivers doesn't include those - do
you want me to send a patch that adds them?

Bartosz

  reply	other threads:[~2020-08-19 17:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-21 14:48 [PATCH] gpio: gpio-crystalcove.c: changed every 'unsigned' to 'unsigned int' Abanoub Sameh
2020-07-21 16:05 ` Andy Shevchenko
2020-08-19 17:56   ` Bartosz Golaszewski [this message]
2020-08-19 18:50     ` Andy Shevchenko
2020-08-19 18:52       ` Bartosz Golaszewski

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=CAMpxmJVW0yXdVVxYYiNjHw5XsKx+cyb6hV7KTeOQBxgFJWWx4w@mail.gmail.com \
    --to=bgolaszewski@baylibre.com \
    --cc=abanoubsameh8@gmail.com \
    --cc=abanoubsameh@protonmail.com \
    --cc=andy.shevchenko@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.