From: Yury Norov <yury.norov@gmail.com>
To: I Hsin Cheng <richard120310@gmail.com>
Cc: John Stultz <jstultz@google.com>,
tglx@linutronix.de, sboyd@kernel.org,
linux-kernel@vger.kernel.org, jserv@ccns.ncku.edu.tw,
skhan@linuxfoundation.org, linux-kernel-mentees@lists.linux.dev
Subject: Re: [PATCH] clocksource: Utilize cpumask_next_wrap() to shrink code size
Date: Fri, 13 Jun 2025 01:13:38 -0400 [thread overview]
Message-ID: <aEuzgmClrimyc0RY@yury> (raw)
In-Reply-To: <aErzPhCYGLqOdlTe@yury>
> > > > I think Yury submitted the same change here recently:
> > > > https://lore.kernel.org/lkml/20250607141106.563924-3-yury.norov@gmail.com/
> > > >
> > > > Though, I think he has another iteration needed as Thomas had feedback
> > > > on the subject line.
> > > >
> > > > The bloat-o-meter data is a nice inclusion here!
> > > >
> > > > Yury: Would you be open to adapting I Hsin Cheng's commit message into
> > > > yours and adding them as co-author via the Co-developed-by: tag?
> > > > (Assuming I Hsin Cheng agrees - See
> > > > Documentation/process/submitting-patches.rst for how to do this
> > > > properly).
> > >
> > > Yeah, bloat-o-meter report is good enough to add co-developed-by tag.
> > > I Hsin, do you agree?
> >
> > Sure thing, so do I need to apply the tag myself or we'll follow Yury's
> > patch work?
>
> I'll send v2 and include your results.
John, FYI.
I Hsing submitted another patch that duplicates this series. You're in
CC, but just in case:
https://lore.kernel.org/all/20250613033447.3531709-1-richard120310@gmail.com/
I think it's pretty disgusting. I will not make him co-author, and
will not give any credit for this work.
Thanks,
Yury
next prev parent reply other threads:[~2025-06-13 5:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-11 10:45 [PATCH] clocksource: Utilize cpumask_next_wrap() to shrink code size I Hsin Cheng
2025-06-11 18:35 ` John Stultz
2025-06-11 19:04 ` Yury Norov
2025-06-12 7:45 ` I Hsin Cheng
2025-06-12 15:33 ` Yury Norov
2025-06-13 5:13 ` Yury Norov [this message]
2025-06-13 5:25 ` I Hsin Cheng
2025-06-13 5:29 ` I Hsin Cheng
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=aEuzgmClrimyc0RY@yury \
--to=yury.norov@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=richard120310@gmail.com \
--cc=sboyd@kernel.org \
--cc=skhan@linuxfoundation.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