From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Thorsten Leemhuis <regressions@leemhuis.info>,
Keith Busch <kbusch@kernel.org>, Christoph Hellwig <hch@lst.de>,
shenlinghai@163.com, Jens Axboe <axboe@fb.com>,
Sagi Grimberg <sagi@grimberg.me>,
dwmw2@infradead.org
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Regressions <regressions@lists.linux.dev>,
Linux NVMe <linux-nvme@lists.infradead.org>
Subject: Re: Fwd: Ubuntu 22.04, "nvme list" will hang for 60 seconds after "nvme subsystem-reset"
Date: Sat, 9 Sep 2023 12:36:14 +0700 [thread overview]
Message-ID: <ZPwETorRO60QGen6@debian.me> (raw)
In-Reply-To: <d7290782-bf72-3a65-26fa-b58e75bcae2c@leemhuis.info>
[-- Attachment #1: Type: text/plain, Size: 621 bytes --]
On Mon, Aug 07, 2023 at 12:30:30PM +0200, Thorsten Leemhuis wrote:
> >> root:~# uname -a
> >> Linux dapu-Star-Lake 5.19.0-46-generic #47~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Wed Jun 21 15:35:31 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
>
> Bagas, please don't forward reports to the developers (and also don't
> add them to the regression tracking) if the report is about a problem
> with a vendor kernel that is known or likely to be patched[1].
> Developers otherwise will just start to ignore your mails, as you are
> wasting their time.
OK, thanks!
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-09-09 5:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-02 11:41 Fwd: Ubuntu 22.04, "nvme list" will hang for 60 seconds after "nvme subsystem-reset" Bagas Sanjaya
2023-08-07 10:30 ` Thorsten Leemhuis
2023-09-09 5:36 ` Bagas Sanjaya [this message]
2023-09-09 5:37 ` Bagas Sanjaya
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=ZPwETorRO60QGen6@debian.me \
--to=bagasdotme@gmail.com \
--cc=axboe@fb.com \
--cc=dwmw2@infradead.org \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=sagi@grimberg.me \
--cc=shenlinghai@163.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;
as well as URLs for NNTP newsgroup(s).