From: Chao Yu <chao@kernel.org>
To: Gao Xiang <hsiangkao@linux.alibaba.com>, linux-erofs@lists.ozlabs.org
Cc: Jonathan Corbet <corbet@lwn.net>,
LKML <linux-kernel@vger.kernel.org>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: erofs: add EROFS webpage
Date: Mon, 20 Nov 2023 11:31:01 +0800 [thread overview]
Message-ID: <43466ecc-7218-e813-7a4f-bcce30f9b3fb@kernel.org> (raw)
In-Reply-To: <056d09c0-eb0d-2092-0766-bf253a9d8751@linux.alibaba.com>
On 2023/11/20 11:23, Gao Xiang wrote:
>
>
> On 2023/11/20 11:18, Chao Yu wrote:
>> On 2023/11/17 16:53, Gao Xiang wrote:
>>> Add a new `W:` field of the EROFS entry points to the documentation
>>> site at <https://erofs.docs.kernel.org>.
>>>
>>> In addition, update the in-tree documentation and Kconfig too.
>>>
>>> Signed-off-by: Gao Xiang <hsiangkao@linux.alibaba.com>
>>
>> Nice work!
>>
>> Reviewed-by: Chao Yu <chao@kernel.org>
>
> Hi Chao,
>
> Thanks for the time and review! but I've already do a tag this morning
> for Linus later so it may not contain this tag, sorry about that.
Xiang,
No problem, it seems I replied a little bit late. :-P
Thanks,
>
> Thanks for the review again!
>
> Thanks,
> Gao Xiang
>
>>
>> Thanks,
>>
>>> ---
>>> Documentation/filesystems/erofs.rst | 4 ++++
>>> MAINTAINERS | 1 +
>>> fs/erofs/Kconfig | 2 +-
>>> 3 files changed, 6 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/Documentation/filesystems/erofs.rst b/Documentation/filesystems/erofs.rst
>>> index 57c6ae23b3fc..cc4626d6ee4f 100644
>>> --- a/Documentation/filesystems/erofs.rst
>>> +++ b/Documentation/filesystems/erofs.rst
>>> @@ -91,6 +91,10 @@ compatibility checking tool (fsck.erofs), and a debugging tool (dump.erofs):
>>> - git://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs-utils.git
>>> +For more information, please also refer to the documentation site:
>>> +
>>> +- https://erofs.docs.kernel.org
>>> +
>>> Bugs and patches are welcome, please kindly help us and send to the following
>>> linux-erofs mailing list:
>>> diff --git a/MAINTAINERS b/MAINTAINERS
>>> index 97f51d5ec1cf..cf39d16ad22a 100644
>>> --- a/MAINTAINERS
>>> +++ b/MAINTAINERS
>>> @@ -7855,6 +7855,7 @@ R: Yue Hu <huyue2@coolpad.com>
>>> R: Jeffle Xu <jefflexu@linux.alibaba.com>
>>> L: linux-erofs@lists.ozlabs.org
>>> S: Maintained
>>> +W: https://erofs.docs.kernel.org
>>> T: git git://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs.git
>>> F: Documentation/ABI/testing/sysfs-fs-erofs
>>> F: Documentation/filesystems/erofs.rst
>>> diff --git a/fs/erofs/Kconfig b/fs/erofs/Kconfig
>>> index e540648dedc2..1d318f85232d 100644
>>> --- a/fs/erofs/Kconfig
>>> +++ b/fs/erofs/Kconfig
>>> @@ -21,7 +21,7 @@ config EROFS_FS
>>> performance under extremely memory pressure without extra cost.
>>> See the documentation at <file:Documentation/filesystems/erofs.rst>
>>> - for more details.
>>> + and the web pages at <https://erofs.docs.kernel.org> for more details.
>>> If unsure, say N.
next prev parent reply other threads:[~2023-11-20 3:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-17 8:53 [PATCH] MAINTAINERS: erofs: add EROFS webpage Gao Xiang
2023-11-20 3:18 ` Chao Yu
2023-11-20 3:23 ` Gao Xiang
2023-11-20 3:31 ` Chao Yu [this message]
2023-11-20 3:32 ` Gao Xiang
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=43466ecc-7218-e813-7a4f-bcce30f9b3fb@kernel.org \
--to=chao@kernel.org \
--cc=corbet@lwn.net \
--cc=hsiangkao@linux.alibaba.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.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