linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <regressions@leemhuis.info>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	linux-scsi@vger.kernel.org,
	"regressions@lists.linux.dev" <regressions@lists.linux.dev>
Subject: Re: [Bisected] Disconnecting pendrive with opened files causes trouble on 6.0.0-rc3 #forregzbot
Date: Wed, 7 Sep 2022 17:50:10 +0200	[thread overview]
Message-ID: <8ec8f04c-d93b-c482-6d96-98607e5bad4e@leemhuis.info> (raw)
In-Reply-To: <59c57de8-580e-a761-e69c-7b1bdbfb8dd4@leemhuis.info>

On 05.09.22 12:27, Thorsten Leemhuis wrote:
>
> [TLDR: I'm adding this regression report to the list of tracked
> regressions; all text from me you find below is based on a few templates
> paragraphs you might have encountered already already in similar form.]

#regzbot fixed-by: f782201ebc2b5f6

For details see Bart's reply to the reporter.

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)

P.S.: As the Linux kernel's regression tracker I deal with a lot of
reports and sometimes miss something important when writing mails like
this. If that's the case here, don't hesitate to tell me in a public
reply, it's in everyone's interest to set the public record straight.

  reply	other threads:[~2022-09-07 15:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-04 18:28 [Bisected] Disconnecting pendrive with opened files causes trouble on 6.0.0-rc3 Mateusz Jończyk
2022-09-05 10:27 ` [Bisected] Disconnecting pendrive with opened files causes trouble on 6.0.0-rc3 #forregzbot Thorsten Leemhuis
2022-09-07 15:50   ` Thorsten Leemhuis [this message]
2022-09-06 14:18 ` [Bisected] Disconnecting pendrive with opened files causes trouble on 6.0.0-rc3 Bart Van Assche

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=8ec8f04c-d93b-c482-6d96-98607e5bad4e@leemhuis.info \
    --to=regressions@leemhuis.info \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=regressions@lists.linux.dev \
    /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).