From: "Michał Nazarewicz" <mina86@mina86.com>
To: Yury Norov <yury.norov@gmail.com>, Yi Sun <yi.sun@unisoc.com>
Cc: yury.norov@gmail.com, akpm@linux-foundation.org,
akinobu.mita@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/2] Improve the performance of bitmap_find_next_zero_area_off()
Date: Thu, 11 Jun 2026 12:56:57 +0200 [thread overview]
Message-ID: <tu7c48k68lunh5cifw9l7vyd@mina86.com> (raw)
In-Reply-To: <aic6DPHDOOny_56B@yury>
> On Mon, Jun 01, 2026 at 05:42:32PM +0800, Yi Sun wrote:
>> v3: https://lore.kernel.org/all/20260514090607.231387-1-yi.sun@unisoc.com
>> - Based on Michał Nazarewicz's suggestion,
>> code optimization was performed on PATCH v1.
> On Mon, Jun 08 2026, Yury Norov wrote:
> We've got a special tag for it: Suggested-by. If the optimization is
> still there, please use the tag. Can you point to that suggestion?
It was part of a review of the previous version of the patch. I think
‘Acked-by: Michał Nazarewicz <mina86@mina86.com>’ on the 1/2 patch is
sufficient here. I’ve looked at the v4 1/2 and it still looks good to
me.
--
Best regards
ミハウ “𝓶𝓲𝓷𝓪86” ナザレヴィツ
«If at first you don’t succeed, give up skydiving»
prev parent reply other threads:[~2026-06-11 10:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-01 9:42 Yi Sun
2026-06-01 9:42 ` [PATCH v4 1/2] lib: bitmap: reduce the number of goto again in bitmap_find_next_zero_area_off() Yi Sun
2026-06-08 22:15 ` Yury Norov
2026-06-17 8:55 ` 答复: " 孙毅 (Yi Sun)
2026-06-01 9:42 ` [PATCH v4 2/2] lib/bitmap: add tests for bitmap_find_next_zero_area_off() Yi Sun
2026-06-08 19:14 ` Yury Norov
2026-06-08 19:24 ` Yury Norov
2026-06-08 7:44 ` 答复: [PATCH v4 0/2] Improve the performance of bitmap_find_next_zero_area_off() 孙毅 (Yi Sun)
2026-06-08 21:54 ` Yury Norov
2026-06-09 1:06 ` Yury Norov
2026-06-09 2:09 ` John Stultz
2026-06-17 9:00 ` 答复: " 孙毅 (Yi Sun)
2026-06-11 10:56 ` Michał Nazarewicz [this message]
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=tu7c48k68lunh5cifw9l7vyd@mina86.com \
--to=mina86@mina86.com \
--cc=akinobu.mita@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yi.sun@unisoc.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 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®