linux-kernel - Re: [PATCH v1 2/2] gpiolib: Introduce gpio_device_get() and gpio_device

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Tue, 29 Nov 2022 16:47:45 +0200
From:   Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To:     Bartosz Golaszewski <brgl@...ev.pl>
Cc:     linux-gpio@...r.kernel.org, linux-kernel@...r.kernel.org,
        Linus Walleij <linus.walleij@...aro.org>
Subject: Re: [PATCH v1 2/2] gpiolib: Introduce gpio_device_get() and
 gpio_device_put()

On Tue, Nov 29, 2022 at 02:54:10PM +0100, Bartosz Golaszewski wrote:
> On Fri, Nov 25, 2022 at 7:11 PM Andy Shevchenko
> <andriy.shevchenko@...ux.intel.com> wrote:
> >
> > Introduce gpio_device_get() and gpio_device_put() helpers
> > and convert existing users.

> This doesn't apply to my for-next branch, can you rebase and resend
> (just this one, the other is applied).

The problem is that you don't merge or cherry-pick fixes into your
for-next branch and they are getting diverged.

In PDx86 subsystem we decided to cherry-pick the fixes into for-next.
Some other subsystems are doing back-merges (but I remember that Linus
T. complained about back merges, although I dunno if it's still
the case). Some subsystems merges their fixes into for-next, dunno
if it's the best practice either.

That said, this can be submitted after v6.2-rc1 is out.

-- 
With Best Regards,
Andy Shevchenko