From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-ide@vger.kernel.org,
"Martin K . Petersen" <martin.petersen@oracle.com>
Subject: Re: [PATCH] libata: Drop firmware version check from the ST1000LM024 quirk
Date: Tue, 02 Jul 2019 16:41:44 -0400 [thread overview]
Message-ID: <yq1h884f9tj.fsf@oracle.com> (raw)
In-Reply-To: <20190701165813.15607-1-hdegoede@redhat.com> (Hans de Goede's message of "Mon, 1 Jul 2019 18:58:13 +0200")
Hans,
> There are several firmware versions between version 2AR10001 and
> 2BA30001, presumably these also have broken FPDMA_AA activation, so
> lets play it safe and apply the quirk to all firmware versions.
Looks good.
Reviewed-by: Martin K. Petersen <martin.petersen@oracle.com>
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2019-07-03 0:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-01 16:58 [PATCH] libata: Drop firmware version check from the ST1000LM024 quirk Hans de Goede
2019-07-02 20:41 ` Martin K. Petersen [this message]
2019-07-02 21:53 ` Jens Axboe
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=yq1h884f9tj.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=axboe@kernel.dk \
--cc=hdegoede@redhat.com \
--cc=linux-ide@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