From: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org, blktests-ci-bot@kernel.org
Subject: Re: [PATCH v2] block: Keep RPM_ACTIVE in blk_pre_runtime_resume() when already active
Date: Tue, 10 Nov 2026 10:00:18 +0900 [thread overview]
Message-ID: <avJne0hJsYHQtevc@shinmob> (raw)
In-Reply-To: <e33d5a5b-0fd9-403a-8a3c-36370660c0bf@kernel.dk>
On Nov 09, 2026 / 14:40, Jens Axboe wrote:
> On 11/8/26 4:59 AM, Shin'ichiro Kawasaki wrote:
> > Please ignore this report. It was sent unexpectedly by blktestes-ci
> > misconfiguration. Sorry for the noise.
>
> I would say this happens fairly regularly, but it's actually
> more than that these days. Can we improve on this? It's a
> lot of extra noise.
Sorry again for the noise. The blktests-ci system has been testing patches
posted to linux-block for the past few months. I enabled automated e-mail
reports to linux-block about a month ago because I did not see any false
positive reports by then. However, false positives have now been sent out. I
will disable the automated reports and keep monitoring for several more months
to confirm that no false positive are generated before enabling them again.
prev parent reply other threads:[~2026-11-10 1:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 11:27 [PATCH v2] block: Keep RPM_ACTIVE in blk_pre_runtime_resume() when already active Stanley Jhu
2026-11-04 14:34 ` Rafael J. Wysocki (Intel)
2026-11-04 18:34 ` Bart Van Assche
2026-11-08 10:11 ` shinichiro.kawasaki
2026-11-08 11:59 ` Shin'ichiro Kawasaki
2026-11-09 21:40 ` Jens Axboe
2026-11-10 1:00 ` Shin'ichiro Kawasaki [this message]
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=avJne0hJsYHQtevc@shinmob \
--to=shinichiro.kawasaki@wdc.com \
--cc=axboe@kernel.dk \
--cc=blktests-ci-bot@kernel.org \
--cc=linux-block@vger.kernel.org \
/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