linux-kernel - Re: [PATCH v1 0/7] auxdisplay: arm-charlcd: refactor with modern APIs

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: <CAHp75Vfkfuw9YYxfECpEKxq_godUMJbJeKNvUR2583dLkPKoKg@mail.gmail.com>
Date: Fri, 9 Jan 2026 18:15:32 +0200
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Linus Walleij <linusw@...nel.org>
Cc: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>, linux-kernel@...r.kernel.org, 
	Andy Shevchenko <andy@...nel.org>, Geert Uytterhoeven <geert@...ux-m68k.org>
Subject: Re: [PATCH v1 0/7] auxdisplay: arm-charlcd: refactor with modern APIs

On Fri, Jan 9, 2026 at 4:30 PM Linus Walleij <linusw@...nel.org> wrote:
> On Wed, Jan 7, 2026 at 10:08 PM Andy Shevchenko
> <andriy.shevchenko@...ux.intel.com> wrote:
> > On Wed, Jan 07, 2026 at 11:06:56PM +0200, Andy Shevchenko wrote:
> > > On Mon, Dec 29, 2025 at 02:52:33PM +0100, Andy Shevchenko wrote:
> > > > The whole series was induced by the Geert's report on one mistake
> > > > in the error path. I looked closely and found a room to refactor
> > > > the whole driver to use modern style and APIs.
> > >
> > > For so long I have got no CI reports and no comments, I'm going to push this
> > > series tomorrow to the repository. Feel free to tell if there is any problem
> > > with that.
> >
> > If I'm not mistaken, Linus might want to have a look... Cc'ing him.
>
> I haven't had time to look at it because it's not in my inbox, sorry.

No, it's me who should say "sorry". I have told you about the old
address (you are the author, if I'm not mistaken), but I forgot to Cc
you with a new one. Of course, you can use `b4 mbox $MSG_ID` to
retrieve this whole thread, but I admit a bit of inconvenience.

> On the other hand, I trust you more than most developers so I'm pretty
> sure I would just ACK it anyways.

Thanks!

-- 
With Best Regards,
Andy Shevchenko