From: Bart Van Assche <bvanassche@acm.org>
To: chengkaitao <pilgrimtao@gmail.com>, axboe@kernel.dk
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
chengkaitao <chengkaitao@kylinos.cn>
Subject: Re: [PATCH RESEND] block/mq-deadline: Replace DD_PRIO_MAX with DD_PRIO_COUNT
Date: Mon, 15 Sep 2025 08:59:32 -0700 [thread overview]
Message-ID: <41ff57c2-19d4-495b-ae51-f30e555a74b4@acm.org> (raw)
In-Reply-To: <20250915130606.97949-1-pilgrimtao@gmail.com>
On 9/15/25 6:06 AM, chengkaitao wrote:
> Remove redundant DD_PRIO_MAX and enum types, Move DD_PRIO_COUNT
> into enum dd_prio{}, and similarly for DD_DIR_COUNT.
Why has this patch been reposted? Last time it was posted I explained in
detail that in my opinion all changes in this patch makes the code worse
instead of better. Additionally, when a new version of a patch is
posted, it should include a changelog. I don't see a changelog in this
patch. Please drop this patch.
Bart.
next prev parent reply other threads:[~2025-09-15 15:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-15 13:06 [PATCH RESEND] block/mq-deadline: Replace DD_PRIO_MAX with DD_PRIO_COUNT chengkaitao
2025-09-15 15:59 ` Bart Van Assche [this message]
2025-09-16 1:17 ` Tao pilgrim
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=41ff57c2-19d4-495b-ae51-f30e555a74b4@acm.org \
--to=bvanassche@acm.org \
--cc=axboe@kernel.dk \
--cc=chengkaitao@kylinos.cn \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pilgrimtao@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox