From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Johan Hovold <johan@kernel.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 1/2] gpiolib: improve coding style for local variables
Date: Wed, 24 Nov 2021 15:42:16 +0100 [thread overview]
Message-ID: <CAMRc=McvXozXCWLU6W3W1DmaxRKOREyT_gbp2d3oWw54zPxFNA@mail.gmail.com> (raw)
In-Reply-To: <YZ5NvolYXei2qsBU@smile.fi.intel.com>
On Wed, Nov 24, 2021 at 3:35 PM Andy Shevchenko
<andriy.shevchenko@linux.intel.com> wrote:
>
> On Wed, Nov 24, 2021 at 01:28:49PM +0100, Bartosz Golaszewski wrote:
> > Drop unneeded whitespaces and put the variables of the same type
> > together for consistency with the rest of the code.
>
> I thought I gave my tag, nevermind, here we are
> Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
>
I removed it because the patch changed. Thanks!
Bart
prev parent reply other threads:[~2021-11-24 14:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-24 12:28 [PATCH v3 1/2] gpiolib: improve coding style for local variables Bartosz Golaszewski
2021-11-24 12:28 ` [PATCH v3 2/2] gpiolib: check the 'ngpios' property in core gpiolib code Bartosz Golaszewski
2021-11-24 14:46 ` Andy Shevchenko
2021-11-24 14:49 ` Andy Shevchenko
2021-11-25 10:10 ` Bartosz Golaszewski
2021-11-25 11:18 ` Andy Shevchenko
2021-12-02 10:26 ` Bartosz Golaszewski
2021-11-24 14:35 ` [PATCH v3 1/2] gpiolib: improve coding style for local variables Andy Shevchenko
2021-11-24 14:42 ` Bartosz Golaszewski [this message]
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=McvXozXCWLU6W3W1DmaxRKOREyT_gbp2d3oWw54zPxFNA@mail.gmail.com' \
--to=brgl@bgdev.pl \
--cc=andriy.shevchenko@linux.intel.com \
--cc=johan@kernel.org \
--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).