From: Christoph Hellwig <hch@infradead.org>
To: Kiwoong Kim <kwmad.kim@samsung.com>
Cc: linux-scsi@vger.kernel.org, jejb@linux.ibm.com,
martin.petersen@oracle.com
Subject: Re: [PATCH] ufs: add quirk to fix abnormal ocs fatal error
Date: Tue, 18 Feb 2020 15:32:22 -0800 [thread overview]
Message-ID: <20200218233222.GA6827@infradead.org> (raw)
In-Reply-To: <20200218224307.8017-1-kwmad.kim@samsung.com>
On Wed, Feb 19, 2020 at 07:43:07AM +0900, Kiwoong Kim wrote:
> Some architectures determines if fatal error for OCS
> occurrs to check status in response upiu. This patch
> is to prevent from reporting command results with that.
This seems to be missing the hunk to actually set the quirk bit..
next prev parent reply other threads:[~2020-02-18 23:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200218224503epcas2p46cec6f56d7564ea7dca4ab600476d938@epcas2p4.samsung.com>
2020-02-18 22:43 ` [PATCH] ufs: add quirk to fix abnormal ocs fatal error Kiwoong Kim
2020-02-18 23:32 ` Christoph Hellwig [this message]
2020-02-18 23:54 ` Kiwoong Kim
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=20200218233222.GA6827@infradead.org \
--to=hch@infradead.org \
--cc=jejb@linux.ibm.com \
--cc=kwmad.kim@samsung.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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).