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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20260121084853.GB2367337@google.com>
Date: Wed, 21 Jan 2026 08:48:53 +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 05:24:05PM +0000, Lee Jones wrote:
> > On Tue, 20 Jan 2026, Mark Brown wrote:
> 
> > > 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?
> 
> Are you using b4 shazam?  I wonder if under the hood it's a mailbox
> fetch then an apply.  I download a mailbox then script my own
> application after the fact so it's not so surprising that it happens for
> me, b4 knows nothing about the patches actually being applied until I
> tell it to go look to send thanks.

Not using shazam.  This is my abbreviated workflow:

 b4.sh am -3 -slt ${PATCHES} -o - ${id} > ${MBOX}
 cat ${MBOX} | formail -ds ./scripts/checkpatch.pl || true
 cat ${MBOX} | git am -3 --reject
 kitty -o font_size=12 git rebase -i HEAD~${NOPATCHES}
 b4.sh ty -aS --me-too --since=1.day

-- 
Lee Jones [李琼斯]