From: Geliang Tang <geliangtang@gmail.com>
To: Kees Cook <keescook@chromium.org>,
Anton Vorontsov <anton@enomsg.org>,
Colin Cross <ccross@android.com>, Tony Luck <tony.luck@intel.com>
Cc: Geliang Tang <geliangtang@gmail.com>, linux-kernel@vger.kernel.org
Subject: [PATCH] pstore: rename two compression functions
Date: Wed, 21 Mar 2018 20:29:32 +0800 [thread overview]
Message-ID: <67c9e6bce3d13c70954fec17def66fad0d7a822c.1521626569.git.geliangtang@gmail.com> (raw)
In-Reply-To: <9c9416b2dff19f05fb4c35879aaa83d11ff72c92.1521626182.git.geliangtang@gmail.com>
We have following five functions which deal with pstore compression.
This patch renamed two functions to make the names of those functions
consistent:
allocate_buf_for_compression -> pstore_init_compression
free_buf_for_compression -> pstore_free_compression
pstore_choose_compression pstore_choose_compression
pstore_compress pstore_compress
pstore_decompress pstore_decompress
Signed-off-by: Geliang Tang <geliangtang@gmail.com>
---
fs/pstore/platform.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/fs/pstore/platform.c b/fs/pstore/platform.c
index 1143ef351c58..03d16b6ed5ec 100644
--- a/fs/pstore/platform.c
+++ b/fs/pstore/platform.c
@@ -256,7 +256,7 @@ static int pstore_decompress(void *in, void *out,
return outlen;
}
-static void allocate_buf_for_compression(void)
+static void pstore_init_compression(void)
{
if (!zbackend)
return;
@@ -285,7 +285,7 @@ static void allocate_buf_for_compression(void)
}
}
-static void free_buf_for_compression(void)
+static void pstore_free_compression(void)
{
if (!IS_ERR_OR_NULL(tfm))
crypto_free_comp(tfm);
@@ -560,7 +560,7 @@ int pstore_register(struct pstore_info *psi)
return -EINVAL;
}
- allocate_buf_for_compression();
+ pstore_init_compression();
if (pstore_is_mounted())
pstore_get_records(0);
@@ -611,7 +611,7 @@ void pstore_unregister(struct pstore_info *psi)
if (psi->flags & PSTORE_FLAGS_DMESG)
pstore_unregister_kmsg();
- free_buf_for_compression();
+ pstore_free_compression();
psinfo = NULL;
backend = NULL;
--
2.14.1
next prev parent reply other threads:[~2018-03-21 12:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-21 12:29 [PATCH] pstore: add zstd compression support Geliang Tang
2018-03-21 12:29 ` Geliang Tang [this message]
2018-03-21 12:29 ` [PATCH] pstore: set PSTORE_842_COMPRESS tristate Geliang Tang
2018-04-23 8:03 ` [PATCH] pstore: add zstd compression support Geliang Tang
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=67c9e6bce3d13c70954fec17def66fad0d7a822c.1521626569.git.geliangtang@gmail.com \
--to=geliangtang@gmail.com \
--cc=anton@enomsg.org \
--cc=ccross@android.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.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®