From: axboe@fb.com (Jens Axboe)
Subject: [PATCH] nvme: fix another 32-bit build warning
Date: Tue, 8 Dec 2015 12:15:03 -0700 [thread overview]
Message-ID: <56672C37.401@fb.com> (raw)
In-Reply-To: <8914775.foiT9pJv7s@wuerfel>
On 12/08/2015 08:22 AM, Arnd Bergmann wrote:
> The nvme_user_cmd function was recently moved around from one file
> to another, which made a warning reappear that I had fixed before
> at some point:
>
> drivers/nvme/host/core.c: In function 'nvme_user_cmd':
> drivers/nvme/host/core.c:424:4: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
>
> This applies the same workaround that we have elsewhere in the
> driver with an extra type cast to uintptr_t.
Applied to for-4.5/nvme, thanks Arnd.
--
Jens Axboe
WARNING: multiple messages have this Message-ID (diff)
From: Jens Axboe <axboe@fb.com>
To: Arnd Bergmann <arnd@arndb.de>, <linux-nvme@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Cc: Christoph Hellwig <hch@lst.de>, Keith Busch <keith.busch@intel.com>
Subject: Re: [PATCH] nvme: fix another 32-bit build warning
Date: Tue, 8 Dec 2015 12:15:03 -0700 [thread overview]
Message-ID: <56672C37.401@fb.com> (raw)
In-Reply-To: <8914775.foiT9pJv7s@wuerfel>
On 12/08/2015 08:22 AM, Arnd Bergmann wrote:
> The nvme_user_cmd function was recently moved around from one file
> to another, which made a warning reappear that I had fixed before
> at some point:
>
> drivers/nvme/host/core.c: In function 'nvme_user_cmd':
> drivers/nvme/host/core.c:424:4: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
>
> This applies the same workaround that we have elsewhere in the
> driver with an extra type cast to uintptr_t.
Applied to for-4.5/nvme, thanks Arnd.
--
Jens Axboe
next prev parent reply other threads:[~2015-12-08 19:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-08 15:22 [PATCH] nvme: fix another 32-bit build warning Arnd Bergmann
2015-12-08 15:22 ` Arnd Bergmann
2015-12-08 19:15 ` Jens Axboe [this message]
2015-12-08 19:15 ` Jens Axboe
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=56672C37.401@fb.com \
--to=axboe@fb.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.