linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Jan Kara <jack@suse.cz>
Cc: Li Jinlin <lijinlin3@huawei.com>,
	axboe@kernel.dk, linux-block@vger.kernel.org,
	linux-kernel@vger.kernel.org, linfeilong@huawei.com
Subject: Re: [PATCH] block/blk-rq-qos: delete useless enmu RQ_QOS_IOPRIO
Date: Mon, 19 Sep 2022 09:38:32 -0700	[thread overview]
Message-ID: <44b01c70-1b3c-36e6-cb59-6a7c27ae26f5@acm.org> (raw)
In-Reply-To: <20220916215824.kfxvesl3l6tjqciw@quack3>

On 9/16/22 14:58, Jan Kara wrote:
> On Fri 16-09-22 07:12:23, Bart Van Assche wrote:
>> Jan, please Cc me on future blk-ioprio patches - I just noticed that I was
>> not Cc-ed on commit 82b74cac2849 ("blk-ioprio: Convert from rqos policy to
>> direct call").
> 
> Well, you were on CC of the whole patchset which this patch was part of - see
> [1]. So maybe you've missed it among other patches.
> 
> [1] https://lore.kernel.org/all/20220623074450.30550-1-jack@suse.cz/

Hi Jan,

Hmm, you are right. Looking back at that patch series, what I remember 
is that I looked at the first two patches, noticed that these were 
outside my area of expertise and skipped the other patches. I will pay 
more attention in the future.

Bart.


  reply	other threads:[~2022-09-19 16:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-16  2:32 [PATCH] block/blk-rq-qos: delete useless enmu RQ_QOS_IOPRIO Li Jinlin
2022-09-16 14:12 ` Bart Van Assche
2022-09-16 21:58   ` Jan Kara
2022-09-19 16:38     ` Bart Van Assche [this message]
2022-09-17 16:30 ` Chaitanya Kulkarni
2022-09-22  1:51 ` Jens Axboe

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=44b01c70-1b3c-36e6-cb59-6a7c27ae26f5@acm.org \
    --to=bvanassche@acm.org \
    --cc=axboe@kernel.dk \
    --cc=jack@suse.cz \
    --cc=lijinlin3@huawei.com \
    --cc=linfeilong@huawei.com \
    --cc=linux-block@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).