All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <regressions@leemhuis.info>
To: regressions@lists.linux.dev
Cc: stable@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: [REGRESSION] introduced in 5.10.140 causes drives to drop from LSI SAS controller (Bisected to 6d17a112e9a63ff6a5edffd1676b99e0ffbcd269) #forregzbot
Date: Wed, 26 Oct 2022 14:20:47 +0200	[thread overview]
Message-ID: <63294047-20e7-6ff2-01b8-a267b0ecb4af@leemhuis.info> (raw)
In-Reply-To: <ddec1a2f-1d55-ac42-9877-0d7119d087cd@leemhuis.info>

[Note: this mail is primarily send for documentation purposes and/or for
regzbot, my Linux kernel regression tracking bot. That's why I removed
most or all folks from the list of recipients, but left any that looked
like a mailing lists. These mails usually contain '#forregzbot' in the
subject, to make them easy to spot and filter out.]

On 22.09.22 13:38, Thorsten Leemhuis wrote:
>
> Hmm, nothing happened here for a week. :-/ That's not how this should be
> when it comes to regressions...
> 
> Jason, any news on this? 

#regzbot invalid: reporter MIA

  reply	other threads:[~2022-10-26 12:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-15  2:21 [REGRESSION] introduced in 5.10.140 causes drives to drop from LSI SAS controller (Bisected to 6d17a112e9a63ff6a5edffd1676b99e0ffbcd269) Jason Wittlin-Cohen
2022-09-15  2:48 ` Bart Van Assche
2022-09-22 11:38   ` Thorsten Leemhuis
2022-10-26 12:20     ` Thorsten Leemhuis [this message]
2022-09-15  7:25 ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2022-09-15  2:13 Jason Wittlin-Cohen
2022-09-15 16:41 ` [REGRESSION] introduced in 5.10.140 causes drives to drop from LSI SAS controller (Bisected to 6d17a112e9a63ff6a5edffd1676b99e0ffbcd269) #forregzbot Thorsten Leemhuis

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=63294047-20e7-6ff2-01b8-a267b0ecb4af@leemhuis.info \
    --to=regressions@leemhuis.info \
    --cc=linux-scsi@vger.kernel.org \
    --cc=regressions@lists.linux.dev \
    --cc=stable@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 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.