public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Nam Cao <namcao@linutronix.de>,
	Anna-Maria Behnsen <anna-maria@linutronix.de>,
	Frederic Weisbecker <frederic@kernel.org>,
	linux-kernel@vger.kernel.org
Cc: "Nam Cao" <namcao@linutronix.de>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	"Alexandre Belloni" <alexandre.belloni@bootlin.com>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	"Linus Walleij" <linus.walleij@linaro.org>,
	"Sebastian Reichel" <sre@kernel.org>,
	"Will Deacon" <will@kernel.org>, "Jon Mason" <jdmason@kudzu.us>,
	"Jaehoon Chung" <jh80.chung@samsung.com>,
	"Hans Verkuil" <hverkuil-cisco@xs4all.nl>,
	"Jassi Brar" <jassisinghbrar@gmail.com>,
	"Pavel Machek" <pavel@ucw.cz>,
	"Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
	"Jonathan Cameron" <jic23@kernel.org>,
	"Andi Shyti" <andi.shyti@kernel.org>,
	"Alex Deucher" <alexander.deucher@amd.com>,
	"Jani Nikula" <jani.nikula@linux.intel.com>,
	"Rob Clark" <robdclark@gmail.com>,
	"Lucas De Marchi" <lucas.demarchi@intel.com>,
	"Zack Rusin" <zack.rusin@broadcom.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	"Jason Gunthorpe" <jgg@ziepe.ca>,
	"Uwe Kleine-König" <ukleinek@kernel.org>,
	"Takashi Iwai" <tiwai@suse.com>,
	alexander.shishkin@linux.intel.com
Subject: Re: [PATCH v2 00/45] Consolidate hrtimer initialization - Part 4
Date: Thu, 06 Feb 2025 17:32:20 +0100	[thread overview]
Message-ID: <87tt97m3u3.ffs@tglx> (raw)
In-Reply-To: <87ldujz9a7.fsf@ubik.fi.intel.com>

On Thu, Feb 06 2025 at 11:56, Alexander Shishkin wrote:
> Nam Cao <namcao@linutronix.de> writes:
>
>> hrtimers is initialized with hrtimer_init(), and after that the timer's
>> callback function is setup separately. This separate initialization is
>> error prone and awkward to use.
>>
>> hrtimer_setup() combines the initialization and is simpler to use.
>>
>> Switch to use the new setup function. Most conversions were done with
>> Coccinelle, see the sematic patch below.
>>
>> This series is intended to be applied to the tip tree
>>
>> v1 -> v2 https://lore.kernel.org/lkml/cover.1729865485.git.namcao@linutronix.de
>>   - rebase onto v6.14-rc1
>
> Link to v2 of part 1 is missing. It's also somehow not in my notmuch
> datadase (looked for "hrtimers: Switch to new hrtimer interface
> functions" -- took a guess based on v1) and is not googleable. It's kind
> of important for reviewing this one. v1 did have the links to the other
> parts, at least.

It's archived and searchable on lore:

  https://lore.kernel.org/all/?q=hrtimers%3A+Consolidate+hrtimer+initialization+-+Part+1

and the third google result points to:

https://patchwork.kernel.org/project/linux-wireless/patch/20241031-hrtimer_setup_p1_v2-v2-0-23400656575a@linutronix.de/

That part 1 series has been applied and is in mainline already.

Thanks,

        tglx

  reply	other threads:[~2025-02-06 16:32 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-05 10:45 [PATCH v2 00/45] Consolidate hrtimer initialization - Part 4 Nam Cao
2025-02-05 10:45 ` [PATCH v2 01/45] USB: chipidea: Switch to use hrtimer_setup() Nam Cao
2025-02-05 10:45 ` [PATCH v2 02/45] usb: dwc2: " Nam Cao
2025-02-05 10:45 ` [PATCH v2 03/45] usb: fotg210-hcd: " Nam Cao
2025-02-05 10:45 ` [PATCH v2 04/45] usb: gadget: " Nam Cao
2025-02-05 10:45 ` [PATCH v2 05/45] usb: ehci: " Nam Cao
2025-02-05 10:45 ` [PATCH v2 06/45] usb: musb: cppi41: " Nam Cao
2025-02-05 10:45 ` [PATCH v2 07/45] usb: typec: tcpm: " Nam Cao
2025-02-05 10:45 ` [PATCH v2 08/45] serial: 8250: " Nam Cao
2025-02-05 10:45 ` [PATCH v2 09/45] serial: amba-pl011: " Nam Cao
2025-02-05 10:45 ` [PATCH v2 10/45] serial: imx: " Nam Cao
2025-02-05 10:45 ` [PATCH v2 11/45] serial: sh-sci: " Nam Cao
2025-02-05 10:46 ` [PATCH v2 12/45] serial: xilinx_uartps: " Nam Cao
2025-02-05 10:46 ` [PATCH v2 13/45] scsi: " Nam Cao
2025-02-05 10:46 ` [PATCH v2 14/45] rtc: class: " Nam Cao
2025-02-05 11:36   ` Alexandre Belloni
2025-02-05 10:46 ` [PATCH v2 15/45] pps: generators: pps_gen_parport: " Nam Cao
2025-02-05 10:46 ` [PATCH v2 16/45] powercap: " Nam Cao
2025-02-05 10:46 ` [PATCH v2 17/45] power: supply: ab8500_chargalg: " Nam Cao
2025-02-08 17:42   ` Sebastian Reichel
2025-02-05 10:46 ` [PATCH v2 18/45] power: reset: ltc2952-poweroff: " Nam Cao
2025-02-08 17:42   ` Sebastian Reichel
2025-02-05 10:46 ` [PATCH v2 19/45] drivers: perf: " Nam Cao
2025-02-05 10:46 ` [PATCH v2 20/45] ntb: ntb_pingpong: " Nam Cao
2025-02-05 10:46 ` [PATCH v2 21/45] mmc: dw_mmc: " Nam Cao
2025-02-05 10:46 ` [PATCH v2 22/45] misc: vcpu_stall_detector: " Nam Cao
2025-02-05 10:46 ` [PATCH v2 23/45] media: " Nam Cao
2025-02-05 10:46 ` [PATCH v2 24/45] mailbox: " Nam Cao
2025-03-01 16:43   ` Jassi Brar
2025-02-05 10:46 ` [PATCH v2 25/45] leds: trigger: pattern: " Nam Cao
2025-02-05 10:46 ` [PATCH v2 26/45] Input: " Nam Cao
2025-02-05 15:30   ` Dmitry Torokhov
2025-02-05 10:46 ` [PATCH v2 27/45] iio: " Nam Cao
2025-02-05 16:21   ` Jonathan Cameron
2025-02-05 10:46 ` [PATCH v2 28/45] i2c: " Nam Cao
2025-02-05 10:46 ` [PATCH v2 29/45] stm class: heartbeat: " Nam Cao
2025-02-05 10:46 ` [PATCH v2 30/45] drm/amdgpu: " Nam Cao
2025-02-05 10:46 ` [PATCH v2 31/45] drm/i915/huc: " Nam Cao
2025-02-05 10:46 ` [PATCH v2 32/45] drm/i915/gvt: " Nam Cao
2025-02-05 10:46 ` [PATCH v2 33/45] drm/i915/perf: " Nam Cao
2025-02-05 10:46 ` [PATCH v2 34/45] drm/i915/pmu: " Nam Cao
2025-02-05 10:46 ` [PATCH v2 35/45] drm/i915/uncore: " Nam Cao
2025-02-05 10:46 ` [PATCH v2 36/45] drm/i915/request: " Nam Cao
2025-02-05 10:46 ` [PATCH v2 37/45] drm/msm: " Nam Cao
2025-02-05 10:46 ` [PATCH v2 38/45] drm/vkms: " Nam Cao
2025-02-05 10:46 ` [PATCH v2 39/45] drm/xe/oa: " Nam Cao
2025-02-05 10:46 ` [PATCH v2 40/45] drm/vmwgfx: " Nam Cao
2025-02-05 10:46 ` [PATCH v2 41/45] virtio: mem: " Nam Cao
2025-02-05 10:46 ` [PATCH v2 42/45] RDMA: " Nam Cao
2025-02-05 10:46 ` [PATCH v2 43/45] pwm: gpio: " Nam Cao
2025-02-07 15:44   ` Uwe Kleine-König
2025-02-05 10:46 ` [PATCH v2 44/45] ASoC: fsl: imx-pcm-fiq: " Nam Cao
2025-02-10  8:28   ` Takashi Iwai
2025-02-05 10:46 ` [PATCH v2 45/45] ALSA: " Nam Cao
2025-02-10  8:29   ` Takashi Iwai
2025-02-06  9:56 ` [PATCH v2 00/45] Consolidate hrtimer initialization - Part 4 Alexander Shishkin
2025-02-06 16:32   ` Thomas Gleixner [this message]
2025-02-07 11:08     ` Alexander Shishkin
2025-02-07 12:58       ` Thomas Gleixner
2025-02-07 13:13         ` Alexander Shishkin

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=87tt97m3u3.ffs@tglx \
    --to=tglx@linutronix.de \
    --cc=alexander.deucher@amd.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=andi.shyti@kernel.org \
    --cc=anna-maria@linutronix.de \
    --cc=dmitry.torokhov@gmail.com \
    --cc=frederic@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hverkuil-cisco@xs4all.nl \
    --cc=jani.nikula@linux.intel.com \
    --cc=jassisinghbrar@gmail.com \
    --cc=jdmason@kudzu.us \
    --cc=jgg@ziepe.ca \
    --cc=jh80.chung@samsung.com \
    --cc=jic23@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lucas.demarchi@intel.com \
    --cc=martin.petersen@oracle.com \
    --cc=mst@redhat.com \
    --cc=namcao@linutronix.de \
    --cc=pavel@ucw.cz \
    --cc=rafael@kernel.org \
    --cc=robdclark@gmail.com \
    --cc=sre@kernel.org \
    --cc=tiwai@suse.com \
    --cc=ukleinek@kernel.org \
    --cc=will@kernel.org \
    --cc=zack.rusin@broadcom.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