Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <44b01c70-1b3c-36e6-cb59-6a7c27ae26f5@acm.org>
Date:   Mon, 19 Sep 2022 09:38:32 -0700
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
 Thunderbird/91.13.0
Subject: Re: [PATCH] block/blk-rq-qos: delete useless enmu RQ_QOS_IOPRIO
Content-Language: en-US
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
References: <20220916023241.32926-1-lijinlin3@huawei.com>
 <f2b8a99d-f6bd-4581-c651-d5b62d6cff21@acm.org>
 <20220916215824.kfxvesl3l6tjqciw@quack3>
From:   Bart Van Assche <bvanassche@acm.org>
In-Reply-To: <20220916215824.kfxvesl3l6tjqciw@quack3>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk

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.