From: Finn Thain <fthain@linux-m68k.org>
To: Jens Axboe <axboe@kernel.dk>
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: Tue, 19 Oct 2021 09:51:40 +1100 (AEDT) [thread overview]
Message-ID: <97323ce2-4f5c-3af2-83ac-686edf672aea@linux-m68k.org> (raw)
In-Reply-To: <8d60483d-3cd6-5df7-8db6-7a8b9ce462e3@kernel.dk>
On Mon, 18 Oct 2021, Jens Axboe wrote:
> Was going to ask if this driver was used by anyone, since it's taken 3
> years for the breakage to be spotted...
A lack of bug reports never implied a lack of users (or potential users).
That falacy is really getting tiresome.
It is much more difficult to report regressions than it is to use a
workaround (i.e. boot a known good kernel). And I have plenty of sympathy
for end-users who may assume that the people and corporations who create
the breakage will take responsibility for fixing it.
Do maintainers really expect innocent end users to report and bisect
regressions, and also test a series of potential fixes until one of them
is finally found to both work and pass code review?
next prev parent reply other threads:[~2021-10-18 22:51 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 [this message]
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
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=97323ce2-4f5c-3af2-83ac-686edf672aea@linux-m68k.org \
--to=fthain@linux-m68k.org \
--cc=axboe@kernel.dk \
--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