From: Christoph Hellwig <hch@infradead.org>
To: Coly Li <colyli@fnnas.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Stephen Zhang <starzhangzsd@gmail.com>,
kent.overstreet@linux.dev, axboe@kernel.dk, sashal@kernel.org,
linux-bcache@vger.kernel.org, linux-kernel@vger.kernel.org,
zhangshida@kylinos.cn
Subject: Re: [PATCH] bcache: fix double bio_endio completion in detached_dev_end_io
Date: Mon, 19 Jan 2026 00:29:48 -0800 [thread overview]
Message-ID: <aW3rfPoloviR1Rp9@infradead.org> (raw)
In-Reply-To: <aW3nzb2lOSVSbqQZ@studio.local>
On Mon, Jan 19, 2026 at 04:19:38PM +0800, Coly Li wrote:
> Before I work on it, I want to know the author already ran and tested the
> patch firstly. Normally I won't test any patches posted on mailing list.
Without a published test suite that can be used for that, that is a very
high demand. Maintainers of code that can't easily be tested by a
drive by contributor (or contributor to the parent subsystems for that
matter) need to help with testing, otherwise we would not get anything
done in the kernel.
next prev parent reply other threads:[~2026-01-19 8:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-15 7:48 [PATCH] bcache: fix double bio_endio completion in detached_dev_end_io zhangshida
2026-01-15 8:06 ` Stephen Zhang
2026-01-15 8:29 ` Christoph Hellwig
2026-01-18 11:49 ` Coly Li
2026-01-19 6:43 ` Christoph Hellwig
2026-01-19 8:19 ` Coly Li
2026-01-19 8:29 ` Christoph Hellwig [this message]
2026-01-19 8:51 ` Coly Li
2026-01-19 6:53 ` Stephen Zhang
2026-01-19 8:04 ` Christoph Hellwig
2026-01-15 8:59 ` Kent Overstreet
2026-01-15 9:17 ` Stephen Zhang
2026-01-15 9:28 ` Kent Overstreet
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=aW3rfPoloviR1Rp9@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-kernel@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=starzhangzsd@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.