On Wed, Jul 8, 2020 at 11:29 AM Dmitry Osipenko <digetx@xxxxxxxxx> wrote: > > Let's move the virq variable declaration to a top-level scope just to > make the code a bit more visually appealing. To me it sounds like unneeded churn, but it's up to maintainers. -- With Best Regards, Andy Shevchenko
Re: [PATCH v1 5/5] gpio: max77620: Move variable declaration
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [PATCH v1 5/5] gpio: max77620: Move variable declaration
- From: Andy Shevchenko <andy.shevchenko@xxxxxxxxx>
- Date: Wed, 8 Jul 2020 11:47:17 +0300
- In-reply-to: <20200708082634.30191-6-digetx@gmail.com>
- References: <20200708082634.30191-1-digetx@gmail.com> <20200708082634.30191-6-digetx@gmail.com>
- Follow-Ups:
- Re: [PATCH v1 5/5] gpio: max77620: Move variable declaration
- From: Dmitry Osipenko
- Re: [PATCH v1 5/5] gpio: max77620: Move variable declaration
- References:
- [PATCH v1 0/5] Improvements for MAX77620 GPIO driver
- From: Dmitry Osipenko
- [PATCH v1 5/5] gpio: max77620: Move variable declaration
- From: Dmitry Osipenko
- [PATCH v1 0/5] Improvements for MAX77620 GPIO driver
- Prev by Date: Re: chv-gpio interrupt storm on UMAX VisionBook 10Wi Pro
- Next by Date: Re: [PATCH v1 1/5] gpio: max77620: Initialize interrupts state
- Previous by thread: [PATCH v1 5/5] gpio: max77620: Move variable declaration
- Next by thread: Re: [PATCH v1 5/5] gpio: max77620: Move variable declaration
- Index(es):
 |