mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ulf Hansson <ulf.hansson@linaro.org>
To: Yu Kuai <yukuai1@huaweicloud.com>
Cc: Jens Axboe <axboe@kernel.dk>,
	linux-block@vger.kernel.org,
	 Linus Walleij <linus.walleij@linaro.org>,
	Bart Van Assche <bvanassche@acm.org>, Jan Kara <jack@suse.cz>,
	 linux-kernel@vger.kernel.org,
	Paolo Valente <paolo.valente@unimore.it>,
	 "yukuai (C)" <yukuai3@huawei.com>
Subject: Re: [PATCH] MAINTAINERS: Move the BFQ io scheduler to Odd Fixes state
Date: Fri, 6 Sep 2024 11:05:43 +0200	[thread overview]
Message-ID: <CAPDyKFrpbgWmHyk2HPP11dA5To9PTwdBLVLyHTVfUOVKYzTUeQ@mail.gmail.com> (raw)
In-Reply-To: <2f2bd13d-933b-da9d-7ea0-5f875dec574b@huaweicloud.com>

On Fri, 6 Sept 2024 at 03:15, Yu Kuai <yukuai1@huaweicloud.com> wrote:
>
> Hi,
>
> 在 2024/09/06 0:56, Ulf Hansson 写道:
> > On Thu, 5 Sept 2024 at 18:49, Jens Axboe <axboe@kernel.dk> wrote:
> >>
> >> On 9/5/24 10:43 AM, Ulf Hansson wrote:
> >>> To not give up entirely on maintenance of BFQ, add myself and Linus Walleij
> >>> as maintainers for BFQ. Although, as both of us has limited bandwidth for
> >>> this, let's reflect that by changing the state to Odd Fixes. If there are
> >>> anybody else that would be interested to help with maintenance of BFQ,
> >>> please let us know.
> >>
> >> We don't add maintainers that haven't actually worked on the code. As it
> >> so happens, we already have a good candidate for this, who knows the
> >> block layer code and does many fixes there, Yu Kuai. And they recently
> >> sent in real fixes too. So that's likely the way the needle will swing.
> >
> > I would certainly appreciate it if Yu Kuai could step in and help,
> > that's why I cced him too.
> >
> > Although, me and Linus were thinking that helping with "Odd Fixes" is
> > better than nothing. Ohh, well, let's see what Yu Kuai thinks, then.
>
> I appreciate the opportunity and am willing to help with maintaining
> BFQ.
>
> Thank you for considering me for this role.
> Kuai

That's really great news! Looking forward to seeing a patch from you
to MAINTAINERS and I will do my best as a community citizen to support
you!

Kind regards
Uffe

      reply	other threads:[~2024-09-06  9:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-05 16:43 Ulf Hansson
2024-09-05 16:49 ` Jens Axboe
2024-09-05 16:56   ` Ulf Hansson
2024-09-06  1:15     ` Yu Kuai
2024-09-06  9:05       ` Ulf Hansson [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=CAPDyKFrpbgWmHyk2HPP11dA5To9PTwdBLVLyHTVfUOVKYzTUeQ@mail.gmail.com \
    --to=ulf.hansson@linaro.org \
    --cc=axboe@kernel.dk \
    --cc=bvanassche@acm.org \
    --cc=jack@suse.cz \
    --cc=linus.walleij@linaro.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paolo.valente@unimore.it \
    --cc=yukuai1@huaweicloud.com \
    --cc=yukuai3@huawei.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

all inboxes | Powered by JetHome®