Thread (3 messages) 3 messages, 2 authors, 2025-09-11

Re: [GIT PULL] Immutable branch between the MFD and GPIO trees for v6.18-rc1

From: Bartosz Golaszewski <hidden>
Date: 2025-09-11 10:40:30
Also in: lkml

On Thu, Sep 11, 2025 at 12:31 PM Lee Jones [off-list ref] wrote:
On Thu, 04 Sep 2025, Bartosz Golaszewski wrote:
quoted
From: Bartosz Golaszewski <redacted>

Lee,

Please pull the following MFD changes that depend on commits I already
have in the GPIO tree for the next merge window.

Thanks,
Bartosz

The following changes since commit 8f5ae30d69d7543eee0d70083daf4de8fe15d585:

  Linux 6.17-rc1 (2025-08-10 19:41:16 +0300)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux.git tags/gpio/mfd-stmpe-for-v6.18-rc1

for you to fetch changes up to df6a44003953fb23ad67f82d299e439e7ff7150a:

  mfd: stmpe: Allow building as module (2025-09-04 15:00:53 +0200)

----------------------------------------------------------------
Immutable branch between the MFD and GPIO trees for v6.18-rc1

Allow building the MFD STMPE driver as module.

----------------------------------------------------------------
Alexander Stein (1):
      mfd: stmpe: Allow building as module

 drivers/mfd/Kconfig | 10 +++++-----
 drivers/mfd/stmpe.c |  6 ++++++
 2 files changed, 11 insertions(+), 5 deletions(-)
Pulled, thanks.
Now, on a second glance: this won't fix the linux-next situation
though, right? You would need the gpio patch as well in your tree
which is the prerequisite but I can no longer put it in an immutable
branch as it was literally the first patch I applied for this cycle
and I've merged several other branches into my tree since then. I
think this PR doesn't make much sense on my part. :(

Unless there's a conflict you should probably just ignore it.

Bartosz
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help