All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-riscv@kernel.org
To: <ye.xingchen@zte.com.cn>
Cc: linux-riscv@lists.infradead.org, paul.walmsley@sifive.com,
	palmer@dabbelt.com, aou@eecs.berkeley.edu, guoren@kernel.org,
	sergey.matyukevich@syntacore.com, dylan@andestech.com,
	ajones@ventanamicro.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] riscv: mm: use bitmap_zero() API
Date: Wed, 30 Aug 2023 13:20:34 +0000	[thread overview]
Message-ID: <169340163459.19859.10905358770015380538.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <202305061711417142802@zte.com.cn>

Hello:

This patch was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:

On Sat, 6 May 2023 17:11:41 +0800 (CST) you wrote:
> From: Ye Xingchen <ye.xingchen@zte.com.cn>
> 
> bitmap_zero() is faster than bitmap_clear(), so use bitmap_zero()
> instead of bitmap_clear().
> 
> Signed-off-by: Ye Xingchen <ye.xingchen@zte.com.cn>
> 
> [...]

Here is the summary with links:
  - riscv: mm: use bitmap_zero() API
    https://git.kernel.org/riscv/c/88ba8c83bead

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+linux-riscv@kernel.org
To: <ye.xingchen@zte.com.cn>
Cc: linux-riscv@lists.infradead.org, paul.walmsley@sifive.com,
	palmer@dabbelt.com, aou@eecs.berkeley.edu, guoren@kernel.org,
	sergey.matyukevich@syntacore.com, dylan@andestech.com,
	ajones@ventanamicro.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] riscv: mm: use bitmap_zero() API
Date: Wed, 30 Aug 2023 13:20:34 +0000	[thread overview]
Message-ID: <169340163459.19859.10905358770015380538.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <202305061711417142802@zte.com.cn>

Hello:

This patch was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:

On Sat, 6 May 2023 17:11:41 +0800 (CST) you wrote:
> From: Ye Xingchen <ye.xingchen@zte.com.cn>
> 
> bitmap_zero() is faster than bitmap_clear(), so use bitmap_zero()
> instead of bitmap_clear().
> 
> Signed-off-by: Ye Xingchen <ye.xingchen@zte.com.cn>
> 
> [...]

Here is the summary with links:
  - riscv: mm: use bitmap_zero() API
    https://git.kernel.org/riscv/c/88ba8c83bead

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



  parent reply	other threads:[~2023-08-30 13:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-06  9:11 [PATCH] riscv: mm: use bitmap_zero() API ye.xingchen
2023-05-06  9:11 ` ye.xingchen
2023-05-07 15:39 ` Anup Patel
2023-05-07 15:39   ` Anup Patel
2023-08-30 13:20 ` patchwork-bot+linux-riscv [this message]
2023-08-30 13:20   ` patchwork-bot+linux-riscv

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=169340163459.19859.10905358770015380538.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-riscv@kernel.org \
    --cc=ajones@ventanamicro.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=dylan@andestech.com \
    --cc=guoren@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=sergey.matyukevich@syntacore.com \
    --cc=ye.xingchen@zte.com.cn \
    /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.