linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: beanhuo@micron.com, stanley.chu@mediatek.com, jejb@linux.ibm.com,
	cang@codeaurora.org, bvanassche@acm.org, asutoshd@codeaurora.org,
	avri.altman@wdc.com, tomas.winkler@intel.com,
	Bean Huo <huobean@gmail.com>,
	alim.akhtar@samsung.com
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>,
	linux-scsi@vger.kernel.org, beanhuo@outlook.com,
	linux-kernel@vger.kernel.org
Subject: Re: [RESENT PATCH v5 0/5] scsi: ufs: cleanup ufs initialization
Date: Mon, 15 Jun 2020 23:59:54 -0400	[thread overview]
Message-ID: <159227986421.24883.16863663810252939595.b4-ty@oracle.com> (raw)
In-Reply-To: <20200603091959.27618-1-huobean@gmail.com>

On Wed, 3 Jun 2020 11:19:54 +0200, Bean Huo wrote:

> 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"
> 
> [...]

Applied to 5.9/scsi-queue, thanks!

[1/5] scsi: ufs: Remove max_t in ufs_get_device_desc
      https://git.kernel.org/mkp/scsi/c/458a45f5262b
[2/5] scsi: ufs: Delete ufshcd_read_desc()
      https://git.kernel.org/mkp/scsi/c/c4607a09450d
[3/5] scsi: ufs: Fix potential NULL pointer access during memcpy
      https://git.kernel.org/mkp/scsi/c/cbe193f6f093
[4/5] scsi: ufs: Clean up ufs initialization path
      https://git.kernel.org/mkp/scsi/c/7a0bf85b5e18
[5/5] scsi: ufs: Add compatibility with 3.1 UFS unit descriptor length
      https://git.kernel.org/mkp/scsi/c/72fb690eece1

-- 
Martin K. Petersen	Oracle Linux Engineering

      parent reply	other threads:[~2020-06-16  4:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-03  9:19 [RESENT PATCH v5 0/5] scsi: ufs: cleanup ufs initialization Bean Huo
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 [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=159227986421.24883.16863663810252939595.b4-ty@oracle.com \
    --to=martin.petersen@oracle.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=huobean@gmail.com \
    --cc=jejb@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --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).