From: Avri Altman <Avri.Altman@wdc.com>
To: Bart Van Assche <bvanassche@acm.org>,
"Martin K . Petersen" <martin.petersen@oracle.com>,
"James E . J . Bottomley" <jejb@linux.vnet.ibm.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
Christoph Hellwig <hch@lst.de>,
Yaniv Gardi <ygardi@codeaurora.org>,
Subhash Jadavani <subhashj@codeaurora.org>,
Stanley Chu <stanley.chu@mediatek.com>,
Tomas Winkler <tomas.winkler@intel.com>
Subject: RE: [PATCH 2/3] ufs: Use enum dev_cmd_type where appropriate
Date: Wed, 30 Oct 2019 11:25:48 +0000 [thread overview]
Message-ID: <MN2PR04MB699199B4B4666663F194ABB3FC600@MN2PR04MB6991.namprd04.prod.outlook.com> (raw)
In-Reply-To: <20191029230710.211926-3-bvanassche@acm.org>
>
> Declare all variables that hold dev_cmd_type values as an enum instead of as an
> int.
>
> Cc: Yaniv Gardi <ygardi@codeaurora.org>
> Cc: Subhash Jadavani <subhashj@codeaurora.org>
> Cc: Stanley Chu <stanley.chu@mediatek.com>
> Cc: Avri Altman <avri.altman@wdc.com>
> Cc: Tomas Winkler <tomas.winkler@intel.com>
> Signed-off-by: Bart Van Assche <bvanassche@acm.org>
Reviewed-by: Avri Altman <avri.altman@wdc.com>
next prev parent reply other threads:[~2019-10-30 11:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-29 23:07 [PATCH 0/3] Three small UFS patches Bart Van Assche
2019-10-29 23:07 ` [PATCH 1/3] ufs: Fix kernel-doc warnings Bart Van Assche
2019-10-30 11:20 ` Avri Altman
2019-11-01 2:15 ` Martin K. Petersen
2019-10-29 23:07 ` [PATCH 2/3] ufs: Use enum dev_cmd_type where appropriate Bart Van Assche
2019-10-30 11:25 ` Avri Altman [this message]
2019-11-01 2:16 ` Martin K. Petersen
2019-10-29 23:07 ` [PATCH 3/3] ufs: Remove .setup_xfer_req() Bart Van Assche
2019-10-30 11:19 ` Avri Altman
2019-11-04 12:57 ` Avri Altman
2019-11-05 16:17 ` Alim Akhtar
2019-11-06 4:09 ` Alim Akhtar
2019-11-06 4:45 ` Bart Van Assche
2019-11-06 5:04 ` Martin K. Petersen
2019-11-05 5:01 ` 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=MN2PR04MB699199B4B4666663F194ABB3FC600@MN2PR04MB6991.namprd04.prod.outlook.com \
--to=avri.altman@wdc.com \
--cc=bvanassche@acm.org \
--cc=hch@lst.de \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=stanley.chu@mediatek.com \
--cc=subhashj@codeaurora.org \
--cc=tomas.winkler@intel.com \
--cc=ygardi@codeaurora.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.