linux-kernel - Re: [GIT PULL] gpio updates for v6.17-rc1

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]

Message-ID: <CAHk-=wieQsg76--QpUw8M01t-EYzUifZ5SyOekS3Negd5sRO5A@mail.gmail.com>
Date: Mon, 28 Jul 2025 22:05:21 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Bartosz Golaszewski <brgl@...ev.pl>
Cc: Linus Walleij <linus.walleij@...aro.org>, linux-gpio@...r.kernel.org, 
	linux-kernel@...r.kernel.org, 
	Bartosz Golaszewski <bartosz.golaszewski@...aro.org>
Subject: Re: [GIT PULL] gpio updates for v6.17-rc1

On Mon, 28 Jul 2025 at 03:17, Bartosz Golaszewski <brgl@...ev.pl> wrote:
>
> On that note: the commit I mentioned above is already on the list[1]. I
> have a second one that also renames the new callbacks back to their
> original name[2]. This is a result of a simple sed over all source files
> and a skim over the changes to make sure everything looks ok and to
> adjust the formatting. I don't think it makes sense to send 4300+ lines
> of diff to the mailing list, Cc'ing 200+ maintainers if all it does is
> a simple treewide rename, so would you be willing to accept this commit
> too as part of my second PR in order to avoid hundreds of small renaming
> patches over the course of the next releases?

Yes, that sounds sane.  We do those big renames every once in a while,
and while it can be a bit painful for silly conflicts, I assume this
one isn't likely to conflict with many other things.

                Linus