Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH] nvme: add wrapper for nvme ctrl register r/w
Date: Wed, 12 Jul 2017 13:55:47 +0200	[thread overview]
Message-ID: <20170712115547.GA11085@lst.de> (raw)
In-Reply-To: <ad43c2ae-c3af-351d-7a58-0f2f35e79d30@grimberg.me>

On Wed, Jul 12, 2017@01:34:14PM +0300, Sagi Grimberg wrote:
> Not sure whats special about register read/write that they
> deserve a wrapper, but its easy enough to get in before
> my patches if I'll see a review on it.

Mostly because it's a little shorter and we're only going to get
more and more of these calls.  In the end I don't feel strongly
and we can just skip the patch for now and reconsider it once
we have more register read/write calls.

  reply	other threads:[~2017-07-12 11:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-29 17:26 [PATCH] nvme: add wrapper for nvme ctrl register r/w weiping zhang
2017-07-12  7:20 ` Christoph Hellwig
2017-07-12 10:34   ` Sagi Grimberg
2017-07-12 11:55     ` Christoph Hellwig [this message]
2017-07-12 12:01       ` Johannes Thumshirn
2017-07-12 13:25         ` weiping zhang
2017-07-14  9:57         ` weiping zhang

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=20170712115547.GA11085@lst.de \
    --to=hch@lst.de \
    /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