From: Christoph Hellwig <hch@infradead.org>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: Christoph Hellwig <hch@infradead.org>,
colyli@fnnas.com, axboe@kernel.dk, linux-block@vger.kernel.org,
linux-bcache@vger.kernel.org, Shida Zhang <zhangshida@kylinos.cn>
Subject: Re: [PATCH] Revert "bcache: fix improper use of bi_end_io"
Date: Tue, 13 Jan 2026 07:00:03 -0800 [thread overview]
Message-ID: <aWZd8xCPXV7Djx7J@infradead.org> (raw)
In-Reply-To: <aWYL9x5s1nB_B1Ho@moria.home.lan>
On Tue, Jan 13, 2026 at 04:27:19AM -0500, Kent Overstreet wrote:
> It's not being a dick to tell someone they need to slow down and be more
> careful when they're doing something broken and arguing over the revert.
Yes, you are. I did not actually do anything here but point out that
bcache is broken. If that fix made things worse it would be useful
if one of the maintainers or a CI system spots it. You need to do your
job as maintainer instead of constantly attacking others.
Start with that, and then just try being a little nice to people. Most
folks will respond nicely to questions, but less so when you start out
with an attack. And until you learn that I have absolutely no interest
in wasting any further time on arguing with you in any form.
next prev parent reply other threads:[~2026-01-13 15:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-13 6:09 [PATCH] Revert "bcache: fix improper use of bi_end_io" colyli
2026-01-13 8:07 ` Christoph Hellwig
2026-01-13 8:30 ` Kent Overstreet
2026-01-13 8:34 ` Christoph Hellwig
2026-01-13 8:39 ` Kent Overstreet
2026-01-13 8:58 ` Christoph Hellwig
2026-01-13 9:27 ` Kent Overstreet
2026-01-13 15:00 ` Christoph Hellwig [this message]
2026-01-13 15:30 ` Kent Overstreet
2026-01-13 16:18 ` Coly Li
2026-01-13 16:26 ` Christoph Hellwig
2026-01-13 16:34 ` Kent Overstreet
2026-01-19 9:51 ` Daniel Wagner
2026-01-19 10:18 ` Kent Overstreet
2026-01-19 10:34 ` Daniel Wagner
2026-01-19 15:57 ` Daniel Wagner
2026-01-13 16:22 ` Coly Li
2026-01-13 16:25 ` Christoph Hellwig
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=aWZd8xCPXV7Djx7J@infradead.org \
--to=hch@infradead.org \
--cc=axboe@kernel.dk \
--cc=colyli@fnnas.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=zhangshida@kylinos.cn \
/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