From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Alim Akhtar <alim.akhtar@samsung.com>
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
vinholikatti@gmail.com, martin.petersen@oracle.com,
subhashj@codeaurora.org, Bart.VanAssche@wdc.com
Subject: Re: [PATCH v2 1/4] scsi: ufs: Change HCI macro to actual bit position
Date: Wed, 11 Oct 2017 13:45:18 -0400 [thread overview]
Message-ID: <yq1zi8xfuj5.fsf@oracle.com> (raw)
In-Reply-To: <1507044085-16905-1-git-send-email-alim.akhtar@samsung.com> (Alim Akhtar's message of "Tue, 03 Oct 2017 20:51:22 +0530")
Alim,
> Currently UFS HCI uses UFS_BIT() macro to get various bit position for
> the hardware registers status bits. Which makes code longer instead of
> shorter. This macro does not improve code readability as well. Lets
> re-write these macro definition with the actual bit position.
Applied patches 1-4 to 4.15/scsi-queue. Thank you!
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2017-10-11 17:45 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
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
2017-10-03 15:21 ` [PATCH v2 3/4] scsi: ufs: Remove unused #defines Alim Akhtar
2017-10-03 15:40 ` Bart Van Assche
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 [this message]
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=yq1zi8xfuj5.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=Bart.VanAssche@wdc.com \
--cc=alim.akhtar@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--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