From: Bart Van Assche <bvanassche@acm.org>
To: Tang Yizhou <yizhou.tang@shopee.com>,
houtao1@huawei.com, jack@suse.cz, kch@nvidia.com
Cc: axboe@kernel.dk, tj@kernel.org, corbet@lwn.net,
linux-block@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, yingfu.zhou@shopee.com,
chunguang.xu@shopee.com
Subject: Re: [PATCH v2] doc: blk-ioprio: Bring the doc in line with the implementation
Date: Fri, 13 Oct 2023 13:21:15 -0700 [thread overview]
Message-ID: <2f4eb591-b275-42fd-900e-292d0f87dd9e@acm.org> (raw)
In-Reply-To: <20231012024228.2161283-1-yizhou.tang@shopee.com>
On 10/11/23 19:42, Tang Yizhou wrote:
> From: Tang Yizhou <yizhou.tang@shopee.com>
>
> Our system administrator have noted that the names 'rt-to-be' and
> 'all-to-idle' in the I/O priority policies table appeared without
> explanations, leading to confusion. Let's bring these names in line
> with the naming in the 'attribute' section.
>
> Additionally,
> 1. Correct the interface name to 'io.prio.class'.
> 2. Add a table entry of 'promote-to-rt' for consistency.
> 3. Fix a typo of 'priority'.
>
> Suggested-by: Yingfu Zhou <yingfu.zhou@shopee.com>
> Reviewed-by: Hou Tao <houtao1@huawei.com>
> Signed-off-by: Tang Yizhou <yizhou.tang@shopee.com>
> ---
> v2:
> Accept Bart's suggestion and rename the title of the patch.
> Pick up Tao's Reviewed-by tag.
Thank you for having changed the patch subject.
Reviewed-by: Bart Van Assche <bvanassche@acm.org>
next prev parent reply other threads:[~2023-10-13 20:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-12 2:42 Tang Yizhou
2023-10-13 20:21 ` Bart Van Assche [this message]
2023-10-26 17:33 ` Jonathan Corbet
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=2f4eb591-b275-42fd-900e-292d0f87dd9e@acm.org \
--to=bvanassche@acm.org \
--cc=axboe@kernel.dk \
--cc=chunguang.xu@shopee.com \
--cc=corbet@lwn.net \
--cc=houtao1@huawei.com \
--cc=jack@suse.cz \
--cc=kch@nvidia.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@kernel.org \
--cc=yingfu.zhou@shopee.com \
--cc=yizhou.tang@shopee.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®