linux-kernel - Re: [PATCH v3 1/2] gpio: ts4900: Do not set DAT and OE together

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: <CAHp75VcQz+h45+7_j=QkNfo7L=q1EKRskDCULNwZYjcgwxz5ug@mail.gmail.com>
Date:   Fri, 11 Mar 2022 13:25:42 +0200
From:   Andy Shevchenko <andy.shevchenko@...il.com>
To:     Kris Bahnsen <kris@...eddedts.com>
Cc:     Bartosz Golaszewski <brgl@...ev.pl>,
        Linus Walleij <linus.walleij@...aro.org>,
        "open list:GPIO SUBSYSTEM" <linux-gpio@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Mark Featherston <mark@...eddedts.com>
Subject: Re: [PATCH v3 1/2] gpio: ts4900: Do not set DAT and OE together

On Thu, Mar 10, 2022 at 9:47 PM Kris Bahnsen <kris@...eddedts.com> wrote:
> On Thu, 2022-03-10 at 20:30 +0100, Bartosz Golaszewski wrote:
> > On Thu, Mar 10, 2022 at 6:36 PM Kris Bahnsen <kris@...eddedts.com> wrote:

...

> > Hey Kris,
> >
> > I already sent it out to Linus, please create a follow-up patch for that.

> Can you please clarify what that entails since Andy had requested changes to the
> commit message. Should I just create a new patch on top of the commit already on
> master to address the comment changes?

Address the comments.

> How would I address commit message changes,
> or is that not my responsibility at this point?

It's impossible.

-- 
With Best Regards,
Andy Shevchenko