From: Aleksey Romanov <AVRomanov@sberdevices.ru>
To: "minchan@kernel.org" <minchan@kernel.org>,
"senozhatsky@chromium.org" <senozhatsky@chromium.org>,
"ngupta@vflare.org" <ngupta@vflare.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
kernel <kernel@sberdevices.ru>
Subject: Re: [PATCH v2 0/2] tidy up zsmalloc implementation
Date: Mon, 15 Aug 2022 14:56:23 +0000 [thread overview]
Message-ID: <20220815145709.qptdso5bcuhlfnmn@CAB-WSD-0003100.sigma.sbrf.ru> (raw)
In-Reply-To: <20220815123930.37736-1-avromanov@sberdevices.ru>
Hello!
I accidientally send v2 patchset instead of send a single change
from 1/2 patch based on linux-next tree. Please, ignore this patchset
and see the change I send in a separate email.
Sorry for the noise.
--
Thank you,
Alexey
prev parent reply other threads:[~2022-08-15 14:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-15 12:39 Alexey Romanov
2022-08-15 14:56 ` Aleksey Romanov [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=20220815145709.qptdso5bcuhlfnmn@CAB-WSD-0003100.sigma.sbrf.ru \
--to=avromanov@sberdevices.ru \
--cc=akpm@linux-foundation.org \
--cc=kernel@sberdevices.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=ngupta@vflare.org \
--cc=senozhatsky@chromium.org \
/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