From: Bart Van Assche <Bart.VanAssche@wdc.com>
To: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"alim.akhtar@samsung.com" <alim.akhtar@samsung.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "subhashj@codeaurora.org" <subhashj@codeaurora.org>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
"vinholikatti@gmail.com" <vinholikatti@gmail.com>
Subject: Re: [PATCH v2 3/4] scsi: ufs: Remove unused #defines
Date: Tue, 3 Oct 2017 15:40:12 +0000 [thread overview]
Message-ID: <1507045211.2702.7.camel@wdc.com> (raw)
In-Reply-To: <1507044085-16905-3-git-send-email-alim.akhtar@samsung.com>
On Tue, 2017-10-03 at 20:51 +0530, Alim Akhtar wrote:
> HOST_ERROR_INDICATOR and DEVICE_ERROR_INDICATOR are not used
> anywhere. Also as per JESD223C specification, bit[7:4] are reserved.
> Lets remove these #defines.
Reviewed-by: Bart Van Assche <bart.vanassche@wdc.com>
next prev parent reply other threads:[~2017-10-03 15:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20171003152909epcas2p4e6e80cb1c544c38c33267a2d2767e40e@epcas2p4.samsung.com>
2017-10-03 15:21 ` [PATCH v2 1/4] scsi: ufs: Change HCI macro to actual bit position Alim Akhtar
[not found] ` <CGME20171003152910epcas2p3a89515a352b8291d7cdeb5a97536d2a8@epcas2p3.samsung.com>
2017-10-03 15:21 ` [PATCH v2 v2 2/4] scsi: ufs-qcom: Remove uses of UFS_BIT() macro Alim Akhtar
2017-10-03 15:39 ` Bart Van Assche
[not found] ` <CGME20171003152911epcas2p31ec5c2819836a1999ce41555f72aeca6@epcas2p3.samsung.com>
2017-10-03 15:21 ` [PATCH v2 3/4] scsi: ufs: Remove unused #defines Alim Akhtar
2017-10-03 15:40 ` Bart Van Assche [this message]
[not found] ` <CGME20171003152912epcas1p442acf97496d1473907d6d73b7c51aa82@epcas1p4.samsung.com>
2017-10-03 15:21 ` [PATCH v2 4/4] scsi: ufs: Remove unused UFS_BIT() macro Alim Akhtar
2017-10-03 15:40 ` Bart Van Assche
2017-10-03 15:39 ` [PATCH v2 1/4] scsi: ufs: Change HCI macro to actual bit position Bart Van Assche
2017-10-11 17:45 ` Martin K. Petersen
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=1507045211.2702.7.camel@wdc.com \
--to=bart.vanassche@wdc.com \
--cc=alim.akhtar@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=subhashj@codeaurora.org \
--cc=vinholikatti@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;
as well as URLs for NNTP newsgroup(s).