From: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
To: David Sterba <dsterba@suse.com>
Cc: Chris Mason <clm@fb.com>, Josef Bacik <josef@toxicpanda.com>,
Nick Terrell <terrelln@fb.com>,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
Ira Weiny <ira.weiny@intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
Matthew Wilcox <willy@infradead.org>,
Kees Cook <keescook@chromium.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
"James E . J . Bottomley" <James.Bottomley@HansenPartnership.com>,
Helge Deller <deller@gmx.de>,
John David Anglin <dave.anglin@bell.net>,
linux-parisc@vger.kernel.org,
"Fabio M. De Francesco" <fmdefrancesco@gmail.com>
Subject: [RESEND PATCH v4 0/2] btrfs: Replace kmap() with kmap_local_page() in zstd.c
Date: Thu, 16 Jun 2022 23:00:34 +0200 [thread overview]
Message-ID: <20220616210037.7060-1-fmdefrancesco@gmail.com> (raw)
This is a little series which serves the purpose to replace kmap() with
kmap_local_page() in btrfs/zstd.c. Actually this task is only
accomplished in patch 2/2.
Instead patch 1/2 is a pre-requisite for the above-mentioned replacement,
but, above all else, it has the purpose to conform the prototypes of
__kunmap_{local,atomic}() to their own correct semantic. Since those
functions don't make changes to the memory pointed by their arguments,
change the type of those arguments to become pointers to const void.
This little series has version number 4, despite it's the first time the
two component patches have been re-united in a series. This may be a
questionable choice, however patch 1/2 should be at its v4 and patch 2/2
should be at its v3. I've tried to preserve the logs of version changes.
v4 is due to the fact that, when I sent v3, I forgot to Cc several people
and mailing lists. Furthermore, Andrew M. made me notice that I've made
confusion with the tree structure: this is why now I have to send this
series again.
I want to apologize for the noise to people who have received these two
patches more times than it should have been.
Fabio M. De Francesco (2):
highmem: Make __kunmap_{local,atomic}() take "const void *"
btrfs: Replace kmap() with kmap_local_page() in zstd.c
arch/parisc/include/asm/cacheflush.h | 6 ++--
arch/parisc/kernel/cache.c | 2 +-
fs/btrfs/zstd.c | 42 +++++++++++++++-------------
include/linux/highmem-internal.h | 10 +++----
mm/highmem.c | 2 +-
5 files changed, 33 insertions(+), 29 deletions(-)
--
2.36.1
next reply other threads:[~2022-06-16 21:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 21:00 Fabio M. De Francesco [this message]
2022-06-16 21:00 ` [RESEND PATCH v4 1/2] highmem: Make __kunmap_{local,atomic}() take "const void *" Fabio M. De Francesco
2022-06-27 17:02 ` Fabio M. De Francesco
2022-06-27 18:19 ` Andrew Morton
2022-06-28 14:46 ` Fabio M. De Francesco
2022-07-01 17:08 ` Ira Weiny
2022-06-16 21:00 ` [RESEND PATCH v4 2/2] btrfs: Replace kmap() with kmap_local_page() in zstd.c Fabio M. De Francesco
2022-07-01 17:19 ` Ira Weiny
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=20220616210037.7060-1-fmdefrancesco@gmail.com \
--to=fmdefrancesco@gmail.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=akpm@linux-foundation.org \
--cc=bigeasy@linutronix.de \
--cc=clm@fb.com \
--cc=dave.anglin@bell.net \
--cc=deller@gmx.de \
--cc=dsterba@suse.com \
--cc=ira.weiny@intel.com \
--cc=josef@toxicpanda.com \
--cc=keescook@chromium.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=terrelln@fb.com \
--cc=willy@infradead.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
all inboxes | Powered by JetHome®