linux-kernel - Re: [PATCH -next] MAINTAINERS: Move the BFQ io scheduler to Odd Fixes state

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <172562967474.167099.17476472709323596580.b4-ty@kernel.dk>
Date: Fri, 06 Sep 2024 07:34:34 -0600
From: Jens Axboe <axboe@...nel.dk>
To: linux-block@...r.kernel.org, Yu Kuai <yukuai1@...weicloud.com>
Cc: jack@...e.cz, ming.lei@...hat.com, bvanassche@....org, 
 paolo.valente@...more.it, ulf.hansson@...aro.org, 
 linux-kernel@...r.kernel.org, yukuai3@...wei.com, yi.zhang@...wei.com, 
 yangerkun@...wei.com
Subject: Re: [PATCH -next] MAINTAINERS: Move the BFQ io scheduler to Odd
 Fixes state


On Fri, 06 Sep 2024 18:21:53 +0800, Yu Kuai wrote:
> BFQ has been lacking active maintenance for approximately two years, and it
> was recently transitioned to the Orphan state. However, there are still
> many users, I have decided to step forward and assume the role of
> maintainer to ensure continued support and development.
> 
> While I may not be the one with the most extensive knowledge of BFQ's
> internals, I have been actively involved in its development since 2021.
> Moreover, our team continues to rigorously test BFQ in downstream kernels,
> ensuring it's stability and performance. Despite my confidence to maintain
> BFQ, I believe it is prudent to classify its state as "Odd Fixes" to
> accurately reflect my relatively new position as the maintainer.
> 
> [...]

Applied, thanks!

[1/1] MAINTAINERS: Move the BFQ io scheduler to Odd Fixes state
      commit: f55d3b82ac2fe8e12fe784702a7a39ab36b7d4e1

Best regards,
-- 
Jens Axboe