All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stanley Chu <stanley.chu@mediatek.com>
To: Kiwoong Kim <kwmad.kim@samsung.com>
Cc: <linux-scsi@vger.kernel.org>, <alim.akhtar@samsung.com>,
	<avri.altman@wdc.com>, <jejb@linux.ibm.com>,
	<martin.petersen@oracle.com>, <beanhuo@micron.com>,
	<asutoshd@codeaurora.org>, <cang@codeaurora.org>,
	<bvanassche@acm.org>, <grant.jung@samsung.com>,
	<sc.suh@samsung.com>, <hy50.seo@samsung.com>,
	<sh425.lee@samsung.com>, <bhoon95.kim@samsung.com>
Subject: Re: [PATCH v4 1/2] ufs: add a vops to configure block parameter
Date: Wed, 23 Dec 2020 17:31:50 +0800	[thread overview]
Message-ID: <1608715910.14045.6.camel@mtkswgap22> (raw)
In-Reply-To: <d937b2a64d597ce969ad3e36419f9814e5e202ae.1608689016.git.kwmad.kim@samsung.com>

On Wed, 2020-12-23 at 11:05 +0900, Kiwoong Kim wrote:
> There could be some cases to set block parameters
> per host, because of its own dma structure or whatever.
> 
> Signed-off-by: Kiwoong Kim <kwmad.kim@samsung.com>

Reviewed-by: Stanley Chu <stanley.chu@mediatek.com>

  parent reply	other threads:[~2020-12-23  9:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20201223021559epcas2p1c44e4b9764f946c608d810c40c08e53e@epcas2p1.samsung.com>
2020-12-23  2:05 ` [PATCH v4 0/2] permit to set block parameters per vendor Kiwoong Kim
     [not found]   ` <CGME20201223021601epcas2p1311bd2ee57014e3b536de5a5ca286f85@epcas2p1.samsung.com>
2020-12-23  2:05     ` [PATCH v4 1/2] ufs: add a vops to configure block parameter Kiwoong Kim
2020-12-23  2:21       ` Can Guo
2020-12-23  9:31       ` Stanley Chu [this message]
     [not found]   ` <CGME20201223021602epcas2p343141ccef708e29f424d390da5324177@epcas2p3.samsung.com>
2020-12-23  2:05     ` [PATCH v4 2/2] ufs: ufs-exynos: set dma_alignment to 4095 Kiwoong Kim

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=1608715910.14045.6.camel@mtkswgap22 \
    --to=stanley.chu@mediatek.com \
    --cc=alim.akhtar@samsung.com \
    --cc=asutoshd@codeaurora.org \
    --cc=avri.altman@wdc.com \
    --cc=beanhuo@micron.com \
    --cc=bhoon95.kim@samsung.com \
    --cc=bvanassche@acm.org \
    --cc=cang@codeaurora.org \
    --cc=grant.jung@samsung.com \
    --cc=hy50.seo@samsung.com \
    --cc=jejb@linux.ibm.com \
    --cc=kwmad.kim@samsung.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=sc.suh@samsung.com \
    --cc=sh425.lee@samsung.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 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.