From: Chao Yu <chao@kernel.org>
To: Yue Hu <zbestahu@gmail.com>,
xiang@kernel.org, linux-erofs@lists.ozlabs.org
Cc: huyue2@coolpad.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] erofs: avoid pcpubuf.c inclusion if CONFIG_EROFS_FS_ZIP is off
Date: Tue, 23 May 2023 14:19:46 +0800 [thread overview]
Message-ID: <b183ca8b-7292-7d6c-e267-0e10bd32ba8c@kernel.org> (raw)
In-Reply-To: <20230515095758.10391-1-zbestahu@gmail.com>
On 2023/5/15 17:57, Yue Hu wrote:
> From: Yue Hu <huyue2@coolpad.com>
>
> The function of pcpubuf.c is just for low-latency decompression
> algorithms (e.g. lz4).
>
> Signed-off-by: Yue Hu <huyue2@coolpad.com>
> Reviewed-by: Gao Xiang <hsiangkao@linux.alibaba.com>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
WARNING: multiple messages have this Message-ID (diff)
From: Chao Yu <chao@kernel.org>
To: Yue Hu <zbestahu@gmail.com>,
xiang@kernel.org, linux-erofs@lists.ozlabs.org
Cc: jefflexu@linux.alibaba.com, huyue2@coolpad.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] erofs: avoid pcpubuf.c inclusion if CONFIG_EROFS_FS_ZIP is off
Date: Tue, 23 May 2023 14:19:46 +0800 [thread overview]
Message-ID: <b183ca8b-7292-7d6c-e267-0e10bd32ba8c@kernel.org> (raw)
In-Reply-To: <20230515095758.10391-1-zbestahu@gmail.com>
On 2023/5/15 17:57, Yue Hu wrote:
> From: Yue Hu <huyue2@coolpad.com>
>
> The function of pcpubuf.c is just for low-latency decompression
> algorithms (e.g. lz4).
>
> Signed-off-by: Yue Hu <huyue2@coolpad.com>
> Reviewed-by: Gao Xiang <hsiangkao@linux.alibaba.com>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
next prev parent reply other threads:[~2023-05-23 6:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 9:57 [PATCH] erofs: avoid pcpubuf.c inclusion if CONFIG_EROFS_FS_ZIP is off Yue Hu
2023-05-15 9:57 ` Yue Hu
2023-05-23 6:19 ` Chao Yu [this message]
2023-05-23 6:19 ` Chao Yu
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=b183ca8b-7292-7d6c-e267-0e10bd32ba8c@kernel.org \
--to=chao@kernel.org \
--cc=huyue2@coolpad.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xiang@kernel.org \
--cc=zbestahu@gmail.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.