All of lore.kernel.org
 help / color / mirror / Atom feed
From: keith.busch@intel.com (Keith Busch)
Subject: [PATCH] nvme: enforce 64bit offset for nvme_get_log_ext fn
Date: Tue, 27 Mar 2018 14:00:55 -0600	[thread overview]
Message-ID: <20180327200054.GC30867@localhost.localdomain> (raw)
In-Reply-To: <20180327180033.28316-1-mb@lightnvm.io>

On Tue, Mar 27, 2018@08:00:33PM +0200, Matias Bj?rling wrote:
> Compiling on 32 bits system produces a warning for the shift width
> when shifting 32 bit integer with 64bit integer.
> 
> Make sure that offset always is 64bit, and use macros for retrieving
> lower and upper bits of the offset.

Thanks, applied to nvme.

WARNING: multiple messages have this Message-ID (diff)
From: Keith Busch <keith.busch@intel.com>
To: "Matias Bjørling" <mb@lightnvm.io>
Cc: linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org
Subject: Re: [PATCH] nvme: enforce 64bit offset for nvme_get_log_ext fn
Date: Tue, 27 Mar 2018 14:00:55 -0600	[thread overview]
Message-ID: <20180327200054.GC30867@localhost.localdomain> (raw)
In-Reply-To: <20180327180033.28316-1-mb@lightnvm.io>

On Tue, Mar 27, 2018 at 08:00:33PM +0200, Matias Bjørling wrote:
> Compiling on 32 bits system produces a warning for the shift width
> when shifting 32 bit integer with 64bit integer.
> 
> Make sure that offset always is 64bit, and use macros for retrieving
> lower and upper bits of the offset.

Thanks, applied to nvme.

  reply	other threads:[~2018-03-27 20:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-27 18:00 [PATCH] nvme: enforce 64bit offset for nvme_get_log_ext fn Matias Bjørling
2018-03-27 18:00 ` Matias Bjørling
2018-03-27 20:00 ` Keith Busch [this message]
2018-03-27 20:00   ` 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=20180327200054.GC30867@localhost.localdomain \
    --to=keith.busch@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 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.