linux-kernel - Re: [PATCH v2 0/3] Samsung mfd/rtc driver alarm IRQ simplification

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: <20260120172405.GI1354723@google.com>
Date: Tue, 20 Jan 2026 17:24:05 +0000
From: Lee Jones <lee@...nel.org>
To: Mark Brown <broonie@...nel.org>
Cc: Krzysztof Kozlowski <krzk@...nel.org>,
	Alexandre Belloni <alexandre.belloni@...tlin.com>,
	André Draszik <andre.draszik@...aro.org>,
	tools@...nel.org, users@...nel.org,
	Peter Griffin <peter.griffin@...aro.org>,
	Tudor Ambarus <tudor.ambarus@...aro.org>,
	Will McVicker <willmcvicker@...gle.com>,
	Juan Yescas <jyescas@...gle.com>,
	Douglas Anderson <dianders@...omium.org>, kernel-team@...roid.com,
	Kaustabh Chakraborty <kauschluss@...root.org>,
	linux-kernel@...r.kernel.org, linux-samsung-soc@...r.kernel.org,
	linux-rtc@...r.kernel.org
Subject: Re: [PATCH v2 0/3] Samsung mfd/rtc driver alarm IRQ simplification

On Tue, 20 Jan 2026, Mark Brown wrote:

> On Tue, Jan 20, 2026 at 03:52:41PM +0000, Lee Jones wrote:
> > On Tue, 20 Jan 2026, Lee Jones wrote:
> 
> > > [1/3] mfd: sec: add rtc alarm IRQ as platform device resource
> > >       (no commit info)
> > > [2/3] rtc: s5m: query platform device IRQ resource for alarm IRQ
> > >       commit: c70aee3dd85482c67720eb642d59ebbb9433faa5
> > > [3/3] mfd: sec: drop now unused struct sec_pmic_dev::irq_data
> > >       (no commit info)
> 
> > Looks like b4 is having a bad day.
> 
> > I just applied v3, not this set.
> 
> If you fetch a series but don't delete it from the database then (with
> b4 ty -d) then b4 will remember it and if any commits in what gets
> applied match it'll generate a mail for b4 ty -a.  Usually that's when
> some commits didn't get changed.

The last attempt to apply this failed with conflicts.

I wonder why b4 stored that as a success?

-- 
Lee Jones [李琼斯]