From: Thomas Gleixner <tglx@linutronix.de>
To: Christian Brauner <brauner@kernel.org>,
Peter Zijlstra <peterz@infradead.org>
Cc: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>,
"Alexander Viro" <viro@zeniv.linux.org.uk>,
"Jan Kara" <jack@suse.cz>, "Ingo Molnar" <mingo@redhat.com>,
"Darren Hart" <dvhart@infradead.org>,
"Davidlohr Bueso" <dave@stgolabs.net>,
"André Almeida" <andrealmeid@igalia.com>,
"Anna-Maria Behnsen" <anna-maria@linutronix.de>,
"Frederic Weisbecker" <frederic@kernel.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] restart_block: simplify expiration timestamps
Date: Fri, 14 Nov 2025 16:29:33 +0100 [thread overview]
Message-ID: <87wm3sbpk2.ffs@tglx> (raw)
In-Reply-To: <20251111-formel-seufzen-bdf2c97c735a@brauner>
On Tue, Nov 11 2025 at 10:48, Christian Brauner wrote:
> On Mon, Nov 10, 2025 at 10:38:50AM +0100, Thomas Weißschuh wrote:
>> Various expiration timestamps are stored in the restart block as
>> different types than their respective subsystem is using.
>>
>> Align the types.
>>
>> Signed-off-by: Thomas Weißschuh <thomas.weissschuh@linutronix.de>
>> ---
>
> @Thomas, @Peter, do the timer/futex changes look fine to you?
I take them through tip as they are not conflicting with the poll part.
Thanks,
tglx
prev parent reply other threads:[~2025-11-14 15:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-10 9:38 [PATCH 0/3] restart_block: simplify expiration timestamps Thomas Weißschuh
2025-11-10 9:38 ` [PATCH 1/3] select: store end_time as timespec64 in restart block Thomas Weißschuh
2025-11-10 11:07 ` Jan Kara
2025-11-10 9:38 ` [PATCH 2/3] futex: Store time as ktime_t " Thomas Weißschuh
2025-11-10 11:09 ` Jan Kara
2025-11-14 15:33 ` [tip: locking/futex] " tip-bot2 for Thomas Weißschuh
2025-11-10 9:38 ` [PATCH 3/3] hrtimer: " Thomas Weißschuh
2025-11-14 15:33 ` [tip: timers/core] " tip-bot2 for Thomas Weißschuh
2025-11-11 9:48 ` [PATCH 0/3] restart_block: simplify expiration timestamps Christian Brauner
2025-11-11 9:57 ` Peter Zijlstra
2025-11-14 15:29 ` Thomas Gleixner [this message]
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=87wm3sbpk2.ffs@tglx \
--to=tglx@linutronix.de \
--cc=andrealmeid@igalia.com \
--cc=anna-maria@linutronix.de \
--cc=brauner@kernel.org \
--cc=dave@stgolabs.net \
--cc=dvhart@infradead.org \
--cc=frederic@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=thomas.weissschuh@linutronix.de \
--cc=viro@zeniv.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.