From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <peterz@infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patches in the clockevents tree
Date: Tue, 16 Jul 2024 17:21:08 +1000 [thread overview]
Message-ID: <20240716172108.43041186@canb.auug.org.au> (raw)
In-Reply-To: <20240716151404.0383b72a@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 1199 bytes --]
Hi all,
On Tue, 16 Jul 2024 15:14:04 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> The following commits are also in the tip tree as different commits
> (but the same patches):
>
> 0d8d1bd925c8 ("dt-bindings: timer: renesas,tmu: Add R-Car Gen2 support")
> 4f2fd59b7d26 ("dt-bindings: timer: Add SOPHGO SG2002 clint")
> 8b77f4b8dc81 ("clocksource/drivers/realtek: Add timer driver for rtl-otto platforms")
> 9957722a200c ("dt-bindings: timer: renesas,tmu: Add RZ/G1 support")
> b24868b81231 ("dt-bindings: timer: renesas,tmu: Add R-Mobile APE6 support")
> ba39e42e9acd ("clocksource/driver/arm_global_timer: Remove unnecessary ‘0’ values from err")
> cd6d60a0faa6 ("clocksource/drivers/mips-gic-timer: Correct sched_clock width")
> d9a7f85412a9 ("clocksource/drivers/arm_arch_timer: Remove unnecessary ‘0’ values from irq")
> e207ae12f08e ("dt-bindings: timer: Add schema for realtek,otto-timer")
> ec601554e3eb ("clocksource/drivers/sh_cmt: Address race condition for clock events")
> fa957fbdf44c ("clocksource/drivers/mips-gic-timer: Refine rating computation")
And now they are in Linus' tree :-)
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-07-16 7:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-16 5:14 Stephen Rothwell
2024-07-16 7:21 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-07-28 23:30 Stephen Rothwell
2023-05-08 0:58 Stephen Rothwell
2023-02-15 4:29 Stephen Rothwell
2023-02-15 8:02 ` Daniel Lezcano
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=20240716172108.43041186@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=daniel.lezcano@linaro.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.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®