mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Mark-PK Tsai (蔡沛剛)" <Mark-PK.Tsai@mediatek.com>
To: "senozhatsky@chromium.org" <senozhatsky@chromium.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
	"linux-mediatek@lists.infradead.org"
	<linux-mediatek@lists.infradead.org>,
	"axboe@kernel.dk" <axboe@kernel.dk>,
	"minchan@kernel.org" <minchan@kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"YJ Chiang (江英杰)" <yj.chiang@mediatek.com>,
	"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
	"angelogioacchino.delregno@collabora.com"
	<angelogioacchino.delregno@collabora.com>
Subject: Re: [PATCH] zram: use copy_page for full page copy
Date: Mon, 5 Feb 2024 06:43:35 +0000	[thread overview]
Message-ID: <99a493e1e906637a179a80b1f27a4b6bd2a0a671.camel@mediatek.com> (raw)
In-Reply-To: <20231008043855.GA2738554@google.com>

On Sun, 2023-10-08 at 13:38 +0900, Sergey Senozhatsky wrote:
>  	 
> External email : Please do not click links or open attachments until
> you have verified the sender or the content.
>  On (23/10/07 15:05), Mark-PK Tsai wrote:
> > 
> > Some architectures, such as arm, have implemented
> > optimized copy_page for full page copying.
> > 
> > Replace the full page memcpy with copy_page to
> > take advantage of the optimization.
> > 
> > Signed-off-by: Mark-PK Tsai <mark-pk.tsai@mediatek.com>
> 
> Reviewed-by: Sergey Senozhatsky <senozhatsky@chromium.org>

I guess this patch may have been overlooked.
Could someone please help to review it?

Thanks,
Mark

  reply	other threads:[~2024-02-05  6:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-07  7:05 Mark-PK Tsai
2023-10-08  4:38 ` Sergey Senozhatsky
2024-02-05  6:43   ` Mark-PK Tsai (蔡沛剛) [this message]
2024-02-05  6:48     ` Sergey Senozhatsky
2024-02-05  6:50 ` Sergey Senozhatsky
2024-06-13  0:04 Jisheng Zhang
2024-06-13  3:17 ` Sergey Senozhatsky
2024-06-13 12:58   ` Jisheng Zhang
2024-06-14  5:25 ` Christoph Hellwig
2024-06-14  5:31   ` Sergey Senozhatsky

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=99a493e1e906637a179a80b1f27a4b6bd2a0a671.camel@mediatek.com \
    --to=mark-pk.tsai@mediatek.com \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=axboe@kernel.dk \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=matthias.bgg@gmail.com \
    --cc=minchan@kernel.org \
    --cc=senozhatsky@chromium.org \
    --cc=yj.chiang@mediatek.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®