[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <18D8841B-9C33-436A-9B8D-C81E2EA0DE69@fnnas.com>
Date: Mon, 19 Jan 2026 16:51:54 +0800
From: "Coly Li" <colyli@...as.com>
To: "Christoph Hellwig" <hch@...radead.org>
Cc: "Stephen Zhang" <starzhangzsd@...il.com>, <kent.overstreet@...ux.dev>,
<axboe@...nel.dk>, <sashal@...nel.org>, <linux-bcache@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <zhangshida@...inos.cn>
Subject: Re: [PATCH] bcache: fix double bio_endio completion in detached_dev_end_io
> 2026年1月19日 16:29,Christoph Hellwig <hch@...radead.org> 写道:
>
> 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.
>
OK, let me integrate Kent’s test cases and my scripts, and show it in git.kernel.org.
You ask this for times, I should handle it ASAP. But it won’t be the blocker of proceeding this fix.
Anyway, there is no conflict with asking “do you test your patch” from me.
Coly Li
Powered by blists - more mailing lists