public inbox for linux-nvme@lists.infradead.org
 help / color / mirror / Atom feed
From: keith.busch@linux.intel.com (Keith Busch)
Subject: [PATCH 1/6] nvme-ana-log: fixup compiler warning in show_ana_log()
Date: Fri, 17 Aug 2018 15:55:07 -0600	[thread overview]
Message-ID: <20180817215507.GA9931@localhost.localdomain> (raw)
In-Reply-To: <BYAPR04MB4502A06AE5FE20A06720D95F863D0@BYAPR04MB4502.namprd04.prod.outlook.com>

On Fri, Aug 17, 2018@09:44:34PM +0000, Chaitanya Kulkarni wrote:
> 
> Not sure if this is relevant but le64_to_cpu() we are fixing warnings by the cast,
> maybe follow the same pattern everywhere?
> 
> http://lists.infradead.org/pipermail/linux-nvme/2018-June/018585.html

Yeah, consistency is always good. I'm fine with the PRI macros, but either
way is fine as long as we compile without warnings on all architectures.

  reply	other threads:[~2018-08-17 21:55 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-17  7:29 [PATCH 0/6] nvme-cli fixes and ANA updates Hannes Reinecke
2018-08-17  7:29 ` [PATCH 1/6] nvme-ana-log: fixup compiler warning in show_ana_log() Hannes Reinecke
2018-08-17  8:09   ` Christoph Hellwig
2018-08-17 21:44     ` Chaitanya Kulkarni
2018-08-17 21:55       ` Keith Busch [this message]
2018-08-17  7:29 ` [PATCH 2/6] nvme-vendor: fixup c99 declaration in huawei plugin Hannes Reinecke
2018-08-17  8:09   ` Christoph Hellwig
2018-08-17 21:56     ` Keith Busch
2018-08-17  7:29 ` [PATCH 3/6] nvme-discover: sanitize options Hannes Reinecke
2018-08-17  8:10   ` Christoph Hellwig
2018-08-17  7:29 ` [PATCH 4/6] nvme-discover: Retry discovery log if the generation counter changes Hannes Reinecke
2018-08-17  8:11   ` Christoph Hellwig
2018-08-17 10:06     ` Hannes Reinecke
2018-08-17  7:29 ` [PATCH 5/6] nvme-list-subsys: Print PCIe controller address Hannes Reinecke
2018-08-17  8:12   ` Christoph Hellwig
2018-08-17 10:06     ` Hannes Reinecke
2018-08-17  7:29 ` [PATCH 6/6] nvme-list-subsys: Add device name argument and print out ANA state Hannes Reinecke
2018-08-17  8:12   ` Christoph Hellwig
2018-08-17 22:14   ` Chaitanya Kulkarni
2018-08-17 21:58 ` [PATCH 0/6] nvme-cli fixes and ANA updates Keith Busch

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=20180817215507.GA9931@localhost.localdomain \
    --to=keith.busch@linux.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