From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Niklas Cassel <Niklas.Cassel@wdc.com>
Cc: "James E.J. Bottomley" <jejb@linux.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Damien Le Moal <dlemoal@kernel.org>, Song Liu <song@kernel.org>,
Timo Gurr <timo.gurr@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Regressions <regressions@lists.linux.dev>,
Linux SCSI <linux-scsi@vger.kernel.org>,
Linux IDE and libata <linux-ide@vger.kernel.org>,
Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: Fwd: Marvell RAID Controller issues since 6.5.x
Date: Tue, 19 Sep 2023 13:53:55 +0700 [thread overview]
Message-ID: <ZQlFg4GsULu633P1@debian.me> (raw)
In-Reply-To: <ZQgCoJ17UioOtdOJ@debian.me>
[-- Attachment #1: Type: text/plain, Size: 812 bytes --]
On Mon, Sep 18, 2023 at 02:56:16PM +0700, Bagas Sanjaya wrote:
> On Mon, Sep 18, 2023 at 07:34:50AM +0000, Niklas Cassel wrote:
> > On Mon, Sep 18, 2023 at 07:18:28AM +0700, Bagas Sanjaya wrote:
> >
> > Hello Bagas,
> >
> > This is a duplicate of:
> > https://bugzilla.kernel.org/show_bug.cgi?id=217902
> >
> > Problem is solved by:
> > https://lore.kernel.org/linux-scsi/20230915022034.678121-1-dlemoal@kernel.org/
> >
> >
>
> I have asked the reporter on Bugzilla to check the fix above. When he
> reports back successfully, I'll mark this report as fixed.
>
Another user has confirmed the fix (see Bugzilla), so:
#regzbot fix: https://lore.kernel.org/linux-scsi/20230915022034.678121-1-dlemoal@kernel.org/
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-19 6:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-18 0:18 Fwd: Marvell RAID Controller issues since 6.5.x Bagas Sanjaya
2023-09-18 7:34 ` Niklas Cassel
2023-09-18 7:56 ` Bagas Sanjaya
2023-09-19 6:53 ` Bagas Sanjaya [this message]
2023-09-19 11:32 ` Linux regression tracking #update (Thorsten Leemhuis)
2023-09-19 12:08 ` 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=ZQlFg4GsULu633P1@debian.me \
--to=bagasdotme@gmail.com \
--cc=Niklas.Cassel@wdc.com \
--cc=dlemoal@kernel.org \
--cc=jejb@linux.ibm.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=regressions@lists.linux.dev \
--cc=song@kernel.org \
--cc=timo.gurr@gmail.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