From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Daniel Lezcano <daniel.lezcano@linaro•org>,
Thomas Gleixner <tglx@linutronix•de>,
Ingo Molnar <mingo@redhat•com>, "H. Peter Anvin" <hpa@zytor•com>,
Peter Zijlstra <peterz@infradead•org>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: duplicate patches in the clockevents tree
Date: Wed, 15 Feb 2023 15:29:07 +1100 [thread overview]
Message-ID: <20230215152907.238e0ba1@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1556 bytes --]
Hi all,
The following commits are also in the tip tree as different commits
(but the same patches):
e09903cea09e ("clocksource/drivers/riscv: Get rid of clocksource_arch_init() callback")
f243533b29c5 ("clocksource/drivers/sh_cmt: Mark driver as non-removable")
596846da9f03 ("clocksource/drivers/timer-microchip-pit64b: Drop obsolete dependency on COMPILE_TEST")
8e148217ffb9 ("clocksource/drivers/riscv: Increase the clock source rating")
969ec81d5a96 ("clocksource/drivers/timer-riscv: Set CLOCK_EVT_FEAT_C3STOP based on DT")
98ce3981716c ("dt-bindings: timer: Add bindings for the RISC-V timer device")
245fe5328dc7 ("RISC-V: time: initialize hrtimer based broadcast clock event device")
8cf50035875e ("dt-bindings: timer: rk-timer: Add rktimer for rv1126")
These are commits
3aff0403f814 ("clocksource/drivers/riscv: Get rid of clocksource_arch_init() callback")
c3daa4754f3c ("clocksource/drivers/sh_cmt: Mark driver as non-removable")
8d17aca90bcf ("clocksource/drivers/timer-microchip-pit64b: Drop obsolete dependency on COMPILE_TEST")
674402b0098b ("clocksource/drivers/riscv: Increase the clock source rating")
8932a9533a9c ("clocksource/drivers/timer-riscv: Set CLOCK_EVT_FEAT_C3STOP based on DT")
e2bcf2d876fd ("dt-bindings: timer: Add bindings for the RISC-V timer device")
8b3b8fbb4896 ("RISC-V: time: initialize hrtimer based broadcast clock event device")
b3cbfb792792 ("dt-bindings: timer: rk-timer: Add rktimer for rv1126")
in the tip tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2023-02-15 4:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-15 4:29 Stephen Rothwell [this message]
2023-02-15 8:02 ` linux-next: duplicate patches in the clockevents tree Daniel Lezcano
-- strict thread matches above, loose matches on Subject: below --
2023-05-08 0:58 Stephen Rothwell
2024-07-16 5:14 Stephen Rothwell
2024-07-16 7:21 ` Stephen Rothwell
2025-07-28 23:30 Stephen Rothwell
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=20230215152907.238e0ba1@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=daniel.lezcano@linaro$(echo .)org \
--cc=hpa@zytor$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mingo@redhat$(echo .)com \
--cc=peterz@infradead$(echo .)org \
--cc=tglx@linutronix$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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