Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH v2 1/2] nvme-core: change commas to semicolons in nvme_get_log_page
Date: Mon, 19 Jun 2017 08:59:26 +0200	[thread overview]
Message-ID: <20170619065926.GB12938@lst.de> (raw)
In-Reply-To: <1497791759-5754-1-git-send-email-sagi@grimberg.me>

This looks ok, but I think it's just too much churn at the moment.
We already have one patch that moves it to scsi.c as part of the
fw activation without reset patchset, and we if the scsi emulation
removal goes in it should just go away entirely..

  parent reply	other threads:[~2017-06-19  6:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-18 13:15 [PATCH v2 1/2] nvme-core: change commas to semicolons in nvme_get_log_page Sagi Grimberg
2017-06-18 13:15 ` [PATCH v2 2/2] nvme: use a single NVME_AQ_DEPTH and relax it to 32 Sagi Grimberg
2017-06-18 15:10   ` Max Gurtovoy
2017-06-19  6:58   ` Christoph Hellwig
2017-06-19 16:01   ` Keith Busch
2017-06-19 16:47     ` Sagi Grimberg
2017-06-19 16:28   ` Martin K. Petersen
2017-06-18 15:10 ` [PATCH v2 1/2] nvme-core: change commas to semicolons in nvme_get_log_page Max Gurtovoy
2017-06-19  6:59 ` Christoph Hellwig [this message]
2017-06-19  8:06   ` Sagi Grimberg

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=20170619065926.GB12938@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