From: Lee Jones <lee@kernel.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: "Mark Brown" <broonie@kernel.org>,
"Krzysztof Kozlowski" <krzk@kernel.org>,
"Alexandre Belloni" <alexandre.belloni@bootlin.com>,
"André Draszik" <andre.draszik@linaro.org>,
tools@kernel.org, users@kernel.org,
"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: Re: [PATCH v2 0/3] Samsung mfd/rtc driver alarm IRQ simplification
Date: Wed, 21 Jan 2026 08:44:09 +0000 [thread overview]
Message-ID: <20260121084409.GA2367337@google.com> (raw)
In-Reply-To: <20260120-incredible-ladybug-of-psychology-605faf@lemur>
On Tue, 20 Jan 2026, Konstantin Ryabitsev wrote:
> On Tue, Jan 20, 2026 at 05:24:05PM +0000, Lee Jones 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?
>
> It doesn't actually know -- it just stores the retrieved series and then
> checks if it can find any of them in the tree in a commit with your
> authorship. Sometimes it breaks.
>
> My plan is to put in interactive mode where you can do a quick sanity check --
> currently it's all of nothing with "b4 ty -a".
Got it. Thanks for the explanation.
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2026-01-21 8:44 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 [this message]
2026-01-22 13:28 ` [GIT PULL] Immutable branch between MFD and RTC due for the v6.20 merge window Lee Jones
2026-01-22 13:29 ` 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=20260121084409.GA2367337@google.com \
--to=lee@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=andre.draszik@linaro.org \
--cc=broonie@kernel.org \
--cc=dianders@chromium.org \
--cc=jyescas@google.com \
--cc=kauschluss@disroot.org \
--cc=kernel-team@android.com \
--cc=konstantin@linuxfoundation.org \
--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=tools@kernel.org \
--cc=tudor.ambarus@linaro.org \
--cc=users@kernel.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