From: Jens Axboe <axboe@kernel.dk>
To: Finn Thain <fthain@linux-m68k.org>
Cc: Michael Schmitz <schmitzmic@gmail.com>,
linux-m68k@vger.kernel.org, geert@linux-m68k.org,
linux-block@vger.kernel.org,
Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Subject: Re: [PATCH RFC] block - ataflop.c: fix breakage introduced at blk-mq refactoring
Date: Mon, 18 Oct 2021 18:41:37 -0600 [thread overview]
Message-ID: <3596239b-3637-6ea7-d7d5-fe81d0c7604f@kernel.dk> (raw)
In-Reply-To: <a4e827c-9163-9fff-dd20-cdd44432fda5@linux-m68k.org>
On 10/18/21 6:14 PM, Finn Thain wrote:
> On Mon, 18 Oct 2021, Jens Axboe wrote:
>
>>
>> Oh please, can we skip the empty words, this is tiresome and
>> unproductive. Since you apparently have a much better grasp on this than
>> I do, answer me this:
>>
>> 1) How many users of ataflop are there?
>>
>> 2) How big of a subset of that group are capable of figuring out where
>> to send a bug report?
>>
>
> Both good questions. Here are some more.
>
> 3) How many users is sufficient to justify the cost of keeping ataflop
> around?
>
> 4) How long is the user count allowed to remain below that threshold,
> before the code is removed?
I'm not interested in bot conversations. EOD.
--
Jens Axboe
next prev parent reply other threads:[~2021-10-19 0:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-18 22:21 [PATCH RFC] block - ataflop.c: fix breakage introduced at blk-mq refactoring Michael Schmitz
2021-10-18 22:30 ` Jens Axboe
2021-10-18 22:51 ` Finn Thain
2021-10-18 23:07 ` Jens Axboe
2021-10-18 23:17 ` Finn Thain
2021-10-18 23:28 ` Jens Axboe
2021-10-19 0:14 ` Finn Thain
2021-10-19 0:41 ` Jens Axboe [this message]
2021-10-18 23:35 ` Michael Schmitz
2021-10-18 23:40 ` Jens Axboe
2021-10-19 0:42 ` Michael Schmitz
2021-10-19 0:44 ` Jens Axboe
2021-10-18 23:55 ` Omar Sandoval
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=3596239b-3637-6ea7-d7d5-fe81d0c7604f@kernel.dk \
--to=axboe@kernel.dk \
--cc=fthain@linux-m68k.org \
--cc=geert@linux-m68k.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=schmitzmic@gmail.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