linux-kernel - Re: [GIT PULL] gpio updates for v6.18-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] [day] [month] [year] [list]

Message-ID: <CAMRc=MeFzn1CfjAaLJgFNyEybCudmaFfQ-9GQDCb6k5FureNsQ@mail.gmail.com>
Date: Wed, 1 Oct 2025 21:18:21 +0200
From: Bartosz Golaszewski <brgl@...ev.pl>
To: Linus Torvalds <torvalds@...ux-foundation.org>
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.18-rc1

On Wed, Oct 1, 2025 at 9:06 PM Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
>
> On Wed, 1 Oct 2025 at 11:36, Linus Torvalds
> <torvalds@...ux-foundation.org> wrote:
> >
> > It's trivial to fix, but I should not be in the situation where I have
> > to fix it, and I should not be getting pull requests that don't even
> > build under trivial configurations.
>
> I see that it got fixed in the MFD tree, but this is not how things
> should work. At all.
>
>                    Linus

Hi Linus,

Sorry for that. All the patches should have been a single series going
through the MFD tree but the GPIO patch was sent to me separately and
I applied which of course caused a build problem in next. I thought
the fix was to have just the core MFD patch in my tree which we did
with Lee and due to the order in which branches are merged into next,
the (unfixed) problem remained hidden. I'll pay more attention next
time to these MODULE_* macros.

Bartosz