From: Pavel Begunkov <asml.silence@gmail.com>
To: Nam Cao <namcao@linutronix.de>,
Anna-Maria Behnsen <anna-maria@linutronix.de>,
Frederic Weisbecker <frederic@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Andreas Hindborg <a.hindborg@kernel.org>,
Alice Ryhl <aliceryhl@google.com>,
Miguel Ojeda <ojeda@kernel.org>, Kees Cook <kees@kernel.org>,
linux-kernel@vger.kernel.org, io-uring <io-uring@vger.kernel.org>
Cc: Jens Axboe <axboe@kernel.dk>
Subject: Re: [PATCH 16/31] io_uring/timeout: Switch to use hrtimer_setup()
Date: Fri, 2 May 2025 09:50:17 +0100 [thread overview]
Message-ID: <23dbf9ff-8542-43d0-8bc1-2584e5f88808@gmail.com> (raw)
In-Reply-To: <8bc0762e419b6fd1d0a0da31a187d19826d71187.1729864823.git.namcao@linutronix.de>
On 10/28/24 07:31, Nam Cao wrote:
> There is a newly introduced hrtimer_setup() which will replace
> hrtimer_init(). This new function is similar to the old one, except that it
> also sanity-checks and initializes the timer's callback function.
>
> Switch to use the new function.
>
> This new function is also used to initialize the callback function in
> .prep() (the callback function depends on whether it is IORING_OP_TIMEOUT
> or IORING_OP_LINK_TIMEOUT). Thus, callback function setup in io_timeout()
> and io_queue_linked_timeout() are now redundant, therefore remove them.
Next time do the basic courtesy of CC'ing io_uring mailing list if
you're sending io_uring patches, so that people don't have to guess
months later why there is an unknown patch in the tree and where the
hell did it came from.
--
Pavel Begunkov
next prev parent reply other threads:[~2025-05-02 8:49 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-28 7:31 [PATCH 00/31] hrtimers: Switch to new hrtimer interface functions (2/5) Nam Cao
2024-10-28 7:31 ` [PATCH 01/31] KVM: MIPS: Switch to use hrtimer_setup() Nam Cao
2024-10-28 7:31 ` [PATCH 02/31] KVM: PPC: " Nam Cao
2024-10-28 7:31 ` [PATCH 03/31] KVM: s390: " Nam Cao
2024-10-28 7:31 ` [PATCH 04/31] KVM: x86: " Nam Cao
2024-10-28 13:53 ` kernel test robot
2024-10-28 19:17 ` kernel test robot
2024-10-28 7:31 ` [PATCH 05/31] KVM: arm64: " Nam Cao
2024-10-28 10:56 ` Marc Zyngier
2024-10-28 7:31 ` [PATCH 06/31] LoongArch: KVM: " Nam Cao
2024-10-28 7:31 ` [PATCH 07/31] riscv: kvm: " Nam Cao
2024-10-28 7:31 ` [PATCH 08/31] ARM: imx: " Nam Cao
2024-10-28 7:31 ` [PATCH 09/31] ARM: 8611/1: l2x0: " Nam Cao
2024-10-28 7:31 ` [PATCH 10/31] powerpc/watchdog: " Nam Cao
2024-10-28 7:31 ` [PATCH 11/31] perf/x86: " Nam Cao
2024-10-28 7:31 ` [PATCH 12/31] s390/ap_bus: " Nam Cao
2024-10-28 7:31 ` [PATCH 13/31] sched: " Nam Cao
2024-10-28 12:51 ` kernel test robot
2024-10-28 7:31 ` [PATCH 14/31] rcu: " Nam Cao
2024-10-28 13:52 ` Paul E. McKenney
2024-10-28 7:31 ` [PATCH 15/31] lib: test_objpool: " Nam Cao
2024-10-28 7:31 ` [PATCH 16/31] io_uring/timeout: " Nam Cao
2025-05-02 8:50 ` Pavel Begunkov [this message]
2024-10-28 7:31 ` [PATCH 17/31] fork: " Nam Cao
2024-10-28 7:31 ` [PATCH 18/31] perf: " Nam Cao
2024-10-28 7:31 ` [PATCH 19/31] timerfd: " Nam Cao
2024-10-28 7:31 ` [PATCH 20/31] time: Switch to hrtimer_setup() Nam Cao
2024-10-28 7:31 ` [PATCH 21/31] bpf: Switch to use hrtimer_setup() Nam Cao
2024-10-28 7:31 ` [PATCH 22/31] ubifs: " Nam Cao
2024-10-28 7:31 ` [PATCH 23/31] watchdog: " Nam Cao
2024-10-28 7:31 ` [PATCH 24/31] tracing/osnoise: " Nam Cao
2024-10-28 7:52 ` Steven Rostedt
2024-10-28 7:31 ` [PATCH 25/31] block, bfq: " Nam Cao
2024-10-28 7:31 ` [PATCH 26/31] ata: pata_octeon_cf: " Nam Cao
2024-10-29 23:41 ` Damien Le Moal
2024-10-28 7:32 ` [PATCH 27/31] blk_iocost: " Nam Cao
2024-10-28 7:32 ` [PATCH 28/31] PM: runtime: " Nam Cao
2024-10-28 11:43 ` Rafael J. Wysocki
2024-10-28 7:32 ` [PATCH 29/31] PM / devfreq: rockchip-dfi: " Nam Cao
2024-12-08 12:39 ` Chanwoo Choi
2024-10-28 7:32 ` [PATCH 30/31] null_blk: " Nam Cao
2024-10-28 7:32 ` [PATCH 31/31] hwrng: timeriomem: " Nam Cao
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=23dbf9ff-8542-43d0-8bc1-2584e5f88808@gmail.com \
--to=asml.silence@gmail.com \
--cc=a.hindborg@kernel.org \
--cc=aliceryhl@google.com \
--cc=anna-maria@linutronix.de \
--cc=axboe@kernel.dk \
--cc=frederic@kernel.org \
--cc=io-uring@vger.kernel.org \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namcao@linutronix.de \
--cc=ojeda@kernel.org \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®