From: Thomas Gleixner <tglx@linutronix.de>
To: Yury Norov <yury.norov@gmail.com>
Cc: I Hsin Cheng <richard120310@gmail.com>,
linux@rasmusvillemoes.dk, jstultz@google.com, sboyd@kernel.org,
linux-kernel@vger.kernel.org, eleanor15x@gmail.com,
visitorckw@gmail.com, jserv@ccns.ncku.edu.tw,
skhan@linuxfoundation.org, linux-kernel-mentees@lists.linux.dev
Subject: Re: [RFC PATCH 2/2] clocksource: Use cpumask_first_but() in clocksource_verify_choose_cpus()
Date: Fri, 13 Jun 2025 18:56:01 +0200 [thread overview]
Message-ID: <87v7ozpom6.ffs@tglx> (raw)
In-Reply-To: <aExR9fLgCNHOaBMS@yury>
On Fri, Jun 13 2025 at 12:29, Yury Norov wrote:
> On Fri, Jun 13, 2025 at 12:48:43PM +0200, Thomas Gleixner wrote:
> At this point it looks more like a lack of professionalism rather than
> an evil will, and I hope he'll do better next time.
Indeed.
> This doesn't mean that I revoke my NAK, or willing to give him any
> credit for this work. But I will review and take his patches in case
> he'll send something valuable to me; with reasonable precautions.
Fair enough.
next prev parent reply other threads:[~2025-06-13 16:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-13 3:34 [RFC PATCH 0/2] Introduce cpumask_first_but() and use cases I Hsin Cheng
2025-06-13 3:34 ` [RFC PATCH 1/2] cpumask: Introduce cpumask_first_but() I Hsin Cheng
2025-06-13 5:55 ` Kuan-Wei Chiu
2025-06-13 3:34 ` [RFC PATCH 2/2] clocksource: Use cpumask_first_but() in clocksource_verify_choose_cpus() I Hsin Cheng
2025-06-13 5:02 ` Yury Norov
2025-06-13 5:22 ` I Hsin Cheng
2025-06-16 14:34 ` Shuah Khan
2025-06-13 5:41 ` I Hsin Cheng
2025-06-13 6:00 ` I Hsin Cheng
2025-06-13 10:48 ` Thomas Gleixner
2025-06-13 11:37 ` I Hsin Cheng
2025-06-13 16:29 ` Yury Norov
2025-06-13 16:56 ` Thomas Gleixner [this message]
2025-06-16 14:38 ` Shuah Khan
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=87v7ozpom6.ffs@tglx \
--to=tglx@linutronix.de \
--cc=eleanor15x@gmail.com \
--cc=jserv@ccns.ncku.edu.tw \
--cc=jstultz@google.com \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=richard120310@gmail.com \
--cc=sboyd@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=visitorckw@gmail.com \
--cc=yury.norov@gmail.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 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.