linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bean Huo <huobean@gmail.com>
To: alim.akhtar@samsung.com, avri.altman@wdc.com,
	asutoshd@codeaurora.org, jejb@linux.ibm.com,
	martin.petersen@oracle.com, stanley.chu@mediatek.com,
	beanhuo@micron.com, bvanassche@acm.org, tomas.winkler@intel.com,
	cang@codeaurora.org
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
	beanhuo@outlook.com
Subject: [RESENT PATCH v5 0/5] scsi: ufs: cleanup ufs initialization
Date: Wed,  3 Jun 2020 11:19:54 +0200	[thread overview]
Message-ID: <20200603091959.27618-1-huobean@gmail.com> (raw)

From: Bean Huo <beanhuo@micron.com>

Resent this patchset since linux-scsi@vger.kernel.org and
linux-kernel@vger.kernel.org rejected my email


Cleanup UFS descriptor length initialization, and delete some unnecessary code.

Changelog:
v4 - v5:
    1. Rebased patch
    2. In the patch 3/5, change "param_size > buff_len" to
       "(param_offset + param_size) > buff_len"

v3 - v4:
    1. add desc_id >= QUERY_DESC_IDN_MAX check in patch 4/5 (Avri Altman)
    2. update buff_len to hold the true descriptor size in 4/5 (Avri Altman)
    3. add new patch 3/5

v2 - v3:
    1. Fix typo in the commit message (Avri Altman & Bart van Assche)
    2. Delete ufshcd_init_desc_sizes() in patch 3/4 (Stanley Chu)
    3. Remove max_t() and buff_len in patch 1/4 (Bart van Assche)
    4. Add patch 4/4 to compatable with 3.1 UFS unit descriptor length

v1 - v2:
    1. split patch
    2. fix one compiling WARNING (Reported-by: kbuild test robot <lkp@intel.com>)

Bart van Assche (1):
  scsi: ufs: remove max_t in ufs_get_device_desc

Bean Huo (4):
  scsi: ufs: delete ufshcd_read_desc()
  scsi: ufs: fix potential access NULL pointer while memcpy
  scsi: ufs: cleanup ufs initialization path
  scsi: ufs: add compatibility with 3.1 UFS unit descriptor length

 drivers/scsi/ufs/ufs.h     |  11 +-
 drivers/scsi/ufs/ufs_bsg.c |   5 +-
 drivers/scsi/ufs/ufshcd.c  | 207 +++++++++----------------------------
 drivers/scsi/ufs/ufshcd.h  |  16 +--
 4 files changed, 54 insertions(+), 185 deletions(-)

-- 
2.17.1


             reply	other threads:[~2020-06-03  9:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-03  9:19 Bean Huo [this message]
2020-06-03  9:19 ` [RESENT PATCH v5 1/5] scsi: ufs: remove max_t in ufs_get_device_desc Bean Huo
2020-06-03  9:19 ` [RESENT PATCH v5 2/5] scsi: ufs: delete ufshcd_read_desc() Bean Huo
2020-06-03  9:19 ` [RESENT PATCH v5 3/5] scsi: ufs: fix potential access NULL pointer while memcpy Bean Huo
2020-06-03  9:19 ` [RESENT PATCH v5 4/5] scsi: ufs: cleanup ufs initialization path Bean Huo
2020-06-03  9:19 ` [RESENT PATCH v5 5/5] scsi: ufs: add compatibility with 3.1 UFS unit descriptor length Bean Huo
2020-06-03 10:33 ` [RESENT PATCH v5 0/5] scsi: ufs: cleanup ufs initialization Avri Altman
2020-06-16  3:59 ` 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=20200603091959.27618-1-huobean@gmail.com \
    --to=huobean@gmail.com \
    --cc=alim.akhtar@samsung.com \
    --cc=asutoshd@codeaurora.org \
    --cc=avri.altman@wdc.com \
    --cc=beanhuo@micron.com \
    --cc=beanhuo@outlook.com \
    --cc=bvanassche@acm.org \
    --cc=cang@codeaurora.org \
    --cc=jejb@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=stanley.chu@mediatek.com \
    --cc=tomas.winkler@intel.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).