From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Kent Gibson <warthog618@gmail.com>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: Re: [PATCH 1/2] gpiolib: drop tabs from local variable declarations
Date: Wed, 20 Dec 2023 16:09:11 +0200 [thread overview]
Message-ID: <ZYL1hybEfHxGVQrr@smile.fi.intel.com> (raw)
In-Reply-To: <CAMRc=MfqYAYsjdPNrc2u7NDuUVdaA4NcE3vMevhSUmZOtc14CQ@mail.gmail.com>
On Tue, Dec 19, 2023 at 08:59:12PM +0100, Bartosz Golaszewski wrote:
> On Tue, Dec 19, 2023 at 4:06 PM Andy Shevchenko
> <andriy.shevchenko@linux.intel.com> wrote:
> > On Tue, Dec 19, 2023 at 03:23:22PM +0100, Bartosz Golaszewski wrote:
...
> > > + struct gpio_chip *gc = desc->gdev->chip;
> > > + int ret;
> > > + unsigned long flags;
> > > + unsigned int offset;
> >
> > I'm wondering if you can make it reversed xmas tree order.
> > This will make it even more consistent between functions.
>
> Sure but we'd have to update all functions across gpiolib.c. Let's
> take it one thing at a time.
The point is to do this for the lines you modified to avoid additional churn
and burden for backport. At least these two things (removing TABs and shuffling
the order) are kinda of the same family of the logical changes. I do not see
the problem doing this in one patch for the lines you modified. Yet, for the
rest it might be another patch, but I don't think it worth doing it.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2023-12-20 14:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-19 14:23 [PATCH 1/2] gpiolib: drop tabs from local variable declarations Bartosz Golaszewski
2023-12-19 14:23 ` [PATCH 2/2] gpio: sysfs: " Bartosz Golaszewski
2023-12-19 15:07 ` Andy Shevchenko
2023-12-19 20:06 ` Bartosz Golaszewski
2023-12-19 15:06 ` [PATCH 1/2] gpiolib: " Andy Shevchenko
2023-12-19 19:59 ` Bartosz Golaszewski
2023-12-20 14:09 ` Andy Shevchenko [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=ZYL1hybEfHxGVQrr@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=bartosz.golaszewski@linaro.org \
--cc=brgl@bgdev.pl \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=warthog618@gmail.com \
/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