From: 廖威雄 <liaoweixiong@allwinnertech.com>
To: gmpy.liaowx@gmail.com
Cc: Tony Luck <tony.luck@intel.com>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] pstore: fix crypto dependencies of 842/zstd compression
Date: Fri, 14 Dec 2018 09:47:28 +0800 [thread overview]
Message-ID: <653367a2-3aae-4b76-8375-186833d34277@allwinnertech.com> (raw)
In-Reply-To: <CAGXu5j+nTVoD=AMvOcn2bvA4C0mw=LKDbVnDWhUkL3c6mJye_g@mail.gmail.com>
在 2018年12月13日 02:43, Kees Cook 写道:
> On Wed, Dec 12, 2018 at 12:24 AM liaoweixiong
> <liaoweixiong@allwinnertech.com> wrote:
>>
>> Reference to commit 58eb5b670747 ("pstore: fix crypto dependencies"),
>> which fixed crypto dependencies of deflate, lzo, lz4 and lz4hc
>> compression, but omitted 842 and newer compression zstd from
>> commit 1021bcf44d0e ("pstore: add zstd compression support")
>>
>> Signed-off-by: liaoweixiong <liaoweixiong@allwinnertech.com>
>
> Were you seeing build or config failures without this patch?
>
testsdfsdf
> -Kees
>
>> ---
>> fs/pstore/Kconfig | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/fs/pstore/Kconfig b/fs/pstore/Kconfig
>> index 0d19d19..7068f45 100644
>> --- a/fs/pstore/Kconfig
>> +++ b/fs/pstore/Kconfig
>> @@ -44,14 +44,14 @@ config PSTORE_LZ4HC_COMPRESS
>> This option enables LZ4HC (high compression) mode algorithm.
>>
>> config PSTORE_842_COMPRESS
>> - bool "842 compression"
>> + tristate "842 compression"
>> depends on PSTORE
>> select CRYPTO_842
>> help
>> This option enables 842 compression algorithm support.
>>
>> config PSTORE_ZSTD_COMPRESS
>> - bool "zstd compression"
>> + tristate "zstd compression"
>> depends on PSTORE
>> select CRYPTO_ZSTD
>> help
>> --
>> 1.9.1
>>
>
>
next prev parent reply other threads:[~2018-12-14 1:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-12 8:23 liaoweixiong
2018-12-12 18:43 ` Kees Cook
2018-12-13 4:39 ` 廖威雄
2018-12-14 1:47 ` 廖威雄 [this message]
2018-12-17 8:16 ` kbuild test robot
2018-12-18 8:04 ` 廖威雄
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=653367a2-3aae-4b76-8375-186833d34277@allwinnertech.com \
--to=liaoweixiong@allwinnertech.com \
--cc=gmpy.liaowx@gmail.com \
--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®