linux-kernel - Re: [PATCH v3] gpiolib: split character device into gpiolib-cdev

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] [day] [month] [year] [list]

Message-ID: <20200616094017.GA5118@sol>
Date:   Tue, 16 Jun 2020 17:40:17 +0800
From:   Kent Gibson <warthog618@...il.com>
To:     Linus Walleij <linus.walleij@...aro.org>
Cc:     "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "open list:GPIO SUBSYSTEM" <linux-gpio@...r.kernel.org>,
        Bartosz Golaszewski <bgolaszewski@...libre.com>
Subject: Re: [PATCH v3] gpiolib: split character device into gpiolib-cdev

On Tue, Jun 16, 2020 at 10:37:32AM +0200, Linus Walleij wrote:
> On Wed, Jun 10, 2020 at 1:52 AM Kent Gibson <warthog618@...il.com> wrote:
> 
> > Split the cdev specific functionality out of gpiolib.c and into
> > gpiolib-cdev.c. This improves the readability and maintainability of both
> > the cdev and core gpiolib code.
> >
> > Suggested-by: Bartosz Golaszewski <bgolaszewski@...libre.com>
> > Signed-off-by: Kent Gibson <warthog618@...il.com>
> >
> > ---
> >
> > Changes in v3:
> >  - updated the gpiolib-cdev.c file comment.
> >  - rebased to latest gpio/devel (no changes impacted this patch)
> >  - dropped the patch commentary as the points mentioned are mostly
> >   resolved - there still remain a couple of commits in gpio/fixes that will
> >   conflict...
> 
> I rebased my GPIO tree on v5.8-rc1 and the old version of the patch did
> not apply and neither did this, could you rebase this patch so I can
> apply it? Sorry for the moving target, the merge window times are
> a bit bumpy. :/
> 

No problem - I was expecting a rebase to be in that patch's future from
the beginning.

Give v4 a try.

Cheers,
Kent.