linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Li Nan <linan666@huaweicloud.com>
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 v2] block/mq-deadline: Remove the redundant rb_entry_rq in the deadline_from_pos().
Date: Fri, 29 Aug 2025 14:16:04 +0800	[thread overview]
Message-ID: <d6702b7c-a674-6fb8-f326-acbd87b148bb@huaweicloud.com> (raw)
In-Reply-To: <20250829034505.95468-1-pilgrimtao@gmail.com>



在 2025/8/29 11:45, chengkaitao 写道:
> From: chengkaitao <chengkaitao@kylinos.cn>
> 
> In commit(fde02699c242), the "if (blk_rq_is_seq_zoned_write(rq))"
> was removed, but the "rb_entry_rq(node)" and some other code were
> inadvertently left behind. This patch fixed it.
> 
> Signed-off-by: chengkaitao <chengkaitao@kylinos.cn>
> ---
>   block/mq-deadline.c | 4 ----
>   1 file changed, 4 deletions(-)
> 
> diff --git a/block/mq-deadline.c b/block/mq-deadline.c
> index 1a031922c447..63145cc9825f 100644
> --- a/block/mq-deadline.c
> +++ b/block/mq-deadline.c
> @@ -133,10 +133,6 @@ static inline struct request *deadline_from_pos(struct dd_per_prio *per_prio,
>   	struct rb_node *node = per_prio->sort_list[data_dir].rb_node;
>   	struct request *rq, *res = NULL;
>   
> -	if (!node)
> -		return NULL;
> -
> -	rq = rb_entry_rq(node);
>   	while (node) {
>   		rq = rb_entry_rq(node);
>   		if (blk_rq_pos(rq) >= pos) {

LGTM

Reviewed-by: Li Nan <linan122@huawei.com>

-- 
Thanks,
Nan


      parent reply	other threads:[~2025-08-29  6:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-29  3:45 [PATCH v2] block/mq-deadline: Remove the redundant rb_entry_rq in the deadline_from_pos() chengkaitao
2025-08-29  4:32 ` Bart Van Assche
2025-08-29  6:16 ` Li Nan [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=d6702b7c-a674-6fb8-f326-acbd87b148bb@huaweicloud.com \
    --to=linan666@huaweicloud.com \
    --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;
as well as URLs for NNTP newsgroup(s).