[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <ZiJz2KP8uNkwZ3vD@smile.fi.intel.com>
Date: Fri, 19 Apr 2024 16:38:32 +0300
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Linus Walleij <linus.walleij@...aro.org>
Cc: Bartosz Golaszewski <brgl@...ev.pl>, Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Bartosz Golaszewski <bartosz.golaszewski@...aro.org>,
Kent Gibson <warthog618@...il.com>, linux-gpio@...r.kernel.org,
linux-acpi@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-wireless@...r.kernel.org, brcm80211@...ts.linux.dev,
brcm80211-dev-list.pdl@...adcom.com,
Mika Westerberg <mika.westerberg@...ux.intel.com>,
Arend van Spriel <arend.vanspriel@...adcom.com>,
Kalle Valo <kvalo@...nel.org>,
Charles Keepax <ckeepax@...nsource.cirrus.com>
Subject: Re: [PATCH v2 1/2] gpiolib: Fix a mess with the GPIO_* flags
On Fri, Apr 19, 2024 at 03:29:13PM +0200, Linus Walleij wrote:
> On Wed, Apr 17, 2024 at 8:40 PM Bartosz Golaszewski <brgl@...ev.pl> wrote:
>
> > Unfortunately my TODO list runneth over. :(
>
> When in situations like this, patch the objective into
> drivers/gpio/TODO so others can pick it up, that's why
> I created the file, and it has actually helped a bit!
>
> IMO you don't even need to send edits to this file for
> review, it's just a work document. Just edit and commit
> it in your tree.
Btw, good point and thanks for the reminder, I believe I also can use it,
but in my case I probably need to send a formal patch :-)
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists