Linux block layer
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: [PATCH] MAINTAINERS: move the BFQ io scheduler to orphan state
Date: Wed, 4 Sep 2024 07:47:07 -0600	[thread overview]
Message-ID: <d8d1758d-b653-41e3-9d98-d3e6619a85e9@kernel.dk> (raw)
In-Reply-To: <CAPDyKFoo1m5VXd529cGbAHY24w8hXpA6C9zYh-WU2m2RYXjyYw@mail.gmail.com>

On 9/4/24 7:27 AM, Ulf Hansson wrote:
> On Tue, 3 Sept 2024 at 17:54, Jens Axboe <axboe@kernel.dk> wrote:
>>
>> Nobody is maintaining this code, and it just falls under the umbrella
>> of block layer code. But at least mark it as such, in case anyone wants
>> to care more deeply about it and assume the responsibility of doing so.
>>
>> Signed-off-by: Jens Axboe <axboe@kernel.dk>
> 
> I haven't spoken to Paolo recently (just dropped him an email), but I
> was under the impression that he intended to keep an eye on the BFQ
> scheduler.

But he hasn't, it's been a long time since he was involved. I've been
applying patches on an as-needed basis, but effectively nobody has
been maintaining it for probably 2 years at this point.

> BTW, why didn't you cc him?

That was an oversight, I think because I haven't seen anything from
him in a long time to assumed he was awol.

-- 
Jens Axboe



  reply	other threads:[~2024-09-04 13:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-03 15:53 [PATCH] MAINTAINERS: move the BFQ io scheduler to orphan state Jens Axboe
2024-09-03 17:20 ` Bart Van Assche
2024-09-03 20:06 ` Bart Van Assche
2024-09-04 13:27 ` Ulf Hansson
2024-09-04 13:47   ` Jens Axboe [this message]
2024-09-04 13:59     ` Ulf Hansson
2024-09-04 14:05       ` Jens Axboe
2024-09-05 13:03         ` Linus Walleij
2024-09-05 14:57           ` Jens Axboe
2024-09-05 18:05             ` Linus Walleij
2024-09-05 18:18               ` Bart Van Assche
2024-09-05 18:34               ` 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=d8d1758d-b653-41e3-9d98-d3e6619a85e9@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=linux-block@vger.kernel.org \
    --cc=ulf.hansson@linaro.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