All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Kiwoong Kim" <kwmad.kim@samsung.com>
To: <linux-scsi@vger.kernel.org>
Subject: RE: [RFC PATCH v2 0/2] ufs: introduce callbacks to get command information
Date: Thu, 2 Jul 2020 11:55:47 +0900	[thread overview]
Message-ID: <00ad01d6501c$49e85e80$ddb91b80$@samsung.com> (raw)
In-Reply-To: <1593658191.3278.7.camel@mtkswgap22>

> Hi Kiwoong,
> 
> On Thu, 2020-07-02 at 11:38 +0900, Kiwoong Kim wrote:
> > Some SoC specific might need command history for various reasons, such
> > as stacking command contexts in system memory to check for debugging
> > in the future or scaling some DVFS knobs to boost IO throughput.
> >
> > What you would do with the information could be variant per SoC
> > vendor.
> >
> > Kiwoong Kim (2):
> >   ufs: introduce a callback to get info of command completion
> >   exynos-ufs: implement dbg_register_dump and compl_xfer_req
> 
> Thanks for the update!
> 
> Would you please elaborate the change log in cover letter for easier
> review in the future?
> 
> Thanks,
> Stanley Chu
> 

I'll keep in mind.

Thanks.
Kiwoong Kim



      reply	other threads:[~2020-07-02  2:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20200702024556epcas2p41b15bb9fb91884435a2cb8711273d29f@epcas2p4.samsung.com>
2020-07-02  2:38 ` [RFC PATCH v2 0/2] ufs: introduce callbacks to get command information Kiwoong Kim
2020-07-02  2:38   ` [RFC PATCH v2 1/2] ufs: introduce a callback to get info of command completion Kiwoong Kim
2020-07-02  5:10     ` Stanley Chu
2020-07-02  6:34     ` kernel test robot
2020-07-02 10:44     ` kernel test robot
2020-07-02  2:38   ` [RFC PATCH v2 2/2] exynos-ufs: implement dbg_register_dump and compl_xfer_req Kiwoong Kim
2020-07-02  7:27     ` kernel test robot
2020-07-02 23:54     ` kernel test robot
2020-07-02  2:49   ` [RFC PATCH v2 0/2] ufs: introduce callbacks to get command information Stanley Chu
2020-07-02  2:55     ` Kiwoong Kim [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='00ad01d6501c$49e85e80$ddb91b80$@samsung.com' \
    --to=kwmad.kim@samsung.com \
    --cc=linux-scsi@vger.kernel.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.