From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: mm-commits@vger.kernel.org, terrelln@fb.com, nphamcs@gmail.com,
ngupta@vflare.org, minchan@kernel.org, senozhatsky@chromium.org
Subject: Re: + documentation-zram-add-documentation-for-algorithm-parameters.patch added to mm-unstable branch
Date: Thu, 29 Aug 2024 11:01:50 +0900 [thread overview]
Message-ID: <20240829020150.GA9738@google.com> (raw)
In-Reply-To: <20240724192716.657C5C32781@smtp.kernel.org>
On (24/07/24 12:27), Andrew Morton wrote:
> The patch titled
> Subject: Documentation/zram: add documentation for algorithm parameters
> has been added to the -mm mm-unstable branch. Its filename is
> documentation-zram-add-documentation-for-algorithm-parameters.patch
>
> This patch will shortly appear at
> https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/documentation-zram-add-documentation-for-algorithm-parameters.patch
>
> Document brief description of compression algorithms' parameters:
> compression level and pre-trained dictionary.
>
Hello Andrew,
Sorry to bother you, can you please drop this entire series? I will
send out a new version shortly. There aren't any serious changes,
I just don't like zram-extend-comp_algorithm-attr-write-handling
patch anymore and instead of changing behavior of an existing
device attribute I'd rather introduce a new one: algorithm_params.
Other than that the series is exactly the same, so we should be
fine landing it this coming merge window.
next prev parent reply other threads:[~2024-08-29 2:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-24 19:27 + documentation-zram-add-documentation-for-algorithm-parameters.patch added to mm-unstable branch Andrew Morton
2024-08-29 2:01 ` Sergey Senozhatsky [this message]
2024-08-30 18:07 ` Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2024-09-02 21:19 Andrew Morton
2024-05-22 22:32 Andrew Morton
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=20240829020150.GA9738@google.com \
--to=senozhatsky@chromium.org \
--cc=akpm@linux-foundation.org \
--cc=minchan@kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=ngupta@vflare.org \
--cc=nphamcs@gmail.com \
--cc=terrelln@fb.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 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.