public inbox for linux-doc@vger.kernel.org
 help / color / mirror / Atom feed
From: Gao Xiang <hsiangkao@linux.alibaba.com>
To: Chao Yu <chao@kernel.org>, 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:32:51 +0800	[thread overview]
Message-ID: <06eb8c00-3ee8-7004-ce2c-cb84cf03e970@linux.alibaba.com> (raw)
In-Reply-To: <43466ecc-7218-e813-7a4f-bcce30f9b3fb@kernel.org>



On 2023/11/20 11:31, Chao Yu wrote:
> 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

Yeah, since all commits in principle need to be in -next.  Thanks again!

Thanks,
Gao Xiang

      reply	other threads:[~2023-11-20  3:32 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
2023-11-20  3:32       ` Gao Xiang [this message]

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=06eb8c00-3ee8-7004-ce2c-cb84cf03e970@linux.alibaba.com \
    --to=hsiangkao@linux.alibaba.com \
    --cc=chao@kernel.org \
    --cc=corbet@lwn.net \
    --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