[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aEuzgmClrimyc0RY@yury>
Date: Fri, 13 Jun 2025 01:13:38 -0400
From: Yury Norov <yury.norov@...il.com>
To: I Hsin Cheng <richard120310@...il.com>
Cc: John Stultz <jstultz@...gle.com>, tglx@...utronix.de, sboyd@...nel.org,
linux-kernel@...r.kernel.org, jserv@...s.ncku.edu.tw,
skhan@...uxfoundation.org, linux-kernel-mentees@...ts.linux.dev
Subject: Re: [PATCH] clocksource: Utilize cpumask_next_wrap() to shrink code
size
> > > > 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
Powered by blists - more mailing lists