From: Lee Jones <lee@kernel.org>
To: "André Draszik" <andre.draszik@linaro.org>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Peter Griffin <peter.griffin@linaro.org>,
Tudor Ambarus <tudor.ambarus@linaro.org>,
Will McVicker <willmcvicker@google.com>,
Juan Yescas <jyescas@google.com>,
Douglas Anderson <dianders@chromium.org>,
kernel-team@android.com,
Kaustabh Chakraborty <kauschluss@disroot.org>,
linux-kernel@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
linux-rtc@vger.kernel.org
Subject: [GIT PULL] Immutable branch between MFD and RTC due for the v6.20 merge window
Date: Thu, 22 Jan 2026 13:28:04 +0000 [thread overview]
Message-ID: <20260122132804.GH3831112@google.com> (raw)
In-Reply-To: <20251120-s5m-alarm-v2-0-cc15f0e32161@linaro.org>
Enjoy!
The following changes since commit 8f0b4cce4481fb22653697cced8d0d04027cb1e8:
Linux 6.19-rc1 (2025-12-14 16:05:07 +1200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git ib-mfd-rtc-v6.20
for you to fetch changes up to b31583a1a9ab32923734ceb5fc95e536dfacccf7:
mfd: sec: Drop now unused struct sec_pmic_dev::irq_data (2026-01-20 15:37:48 +0000)
----------------------------------------------------------------
Immutable branch between MFD and RTC due for the v6.20 merge window
----------------------------------------------------------------
André Draszik (3):
mfd: sec: Add rtc alarm IRQ as platform device resource
rtc: s5m: query platform device IRQ resource for alarm IRQ
mfd: sec: Drop now unused struct sec_pmic_dev::irq_data
drivers/mfd/sec-common.c | 45 ++++++++++++++++++++--------
drivers/mfd/sec-core.h | 2 +-
drivers/mfd/sec-irq.c | 64 ++++++++++++++++++----------------------
drivers/rtc/rtc-s5m.c | 21 +++++--------
include/linux/mfd/samsung/core.h | 1 -
5 files changed, 71 insertions(+), 62 deletions(-)
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2026-01-22 13:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-20 14:38 [PATCH v2 0/3] Samsung mfd/rtc driver alarm IRQ simplification André Draszik
2025-11-20 14:38 ` [PATCH v2 1/3] mfd: sec: add rtc alarm IRQ as platform device resource André Draszik
2025-11-20 14:38 ` [PATCH v2 2/3] rtc: s5m: query platform device IRQ resource for alarm IRQ André Draszik
2025-11-20 14:38 ` [PATCH v2 3/3] mfd: sec: drop now unused struct sec_pmic_dev::irq_data André Draszik
2025-11-26 11:29 ` [PATCH v2 0/3] Samsung mfd/rtc driver alarm IRQ simplification Lee Jones
2025-11-26 12:30 ` André Draszik
2025-11-26 14:04 ` Lee Jones
2025-12-16 16:20 ` Lee Jones
2026-01-20 15:49 ` Lee Jones
2026-01-20 15:52 ` Lee Jones
2026-01-20 15:58 ` Mark Brown
2026-01-20 17:24 ` Lee Jones
2026-01-20 17:28 ` Mark Brown
2026-01-21 8:48 ` Lee Jones
2026-01-21 3:23 ` Konstantin Ryabitsev
2026-01-21 8:44 ` Lee Jones
2026-01-22 13:28 ` Lee Jones [this message]
2026-01-22 13:29 ` [GIT PULL] Immutable branch between MFD and RTC due for the v6.20 merge window Lee Jones
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260122132804.GH3831112@google.com \
--to=lee@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=andre.draszik@linaro.org \
--cc=dianders@chromium.org \
--cc=jyescas@google.com \
--cc=kauschluss@disroot.org \
--cc=kernel-team@android.com \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=peter.griffin@linaro.org \
--cc=tudor.ambarus@linaro.org \
--cc=willmcvicker@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox