From: axboe@fb.com (Jens Axboe)
Subject: [PATCH] NVMe: fix type warning on 32-bit
Date: Fri, 29 May 2015 10:06:41 -0600 [thread overview]
Message-ID: <55688E91.10408@fb.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1505282235140.15930@localhost.lm.intel.com>
On 05/28/2015 04:35 PM, Keith Busch wrote:
> On Tue, 19 May 2015, Arnd Bergmann wrote:
>> A recent change to the ioctl handling caused a new harmless
>> warning in the NVMe driver on all 32-bit machines:
>>
>> drivers/block/nvme-core.c: In function 'nvme_submit_io':
>> drivers/block/nvme-core.c:1794:29: warning: cast to pointer from
>> integer of different size [-Wint-to-pointer-cast]
>>
>> In order to shup up that warning, this introduces a new
>> temporary variable that uses a double cast to extract
>> the pointer from an __u64 structure member.
>
>
> Thanks for the fix.
>
> Acked-by: Keith Busch <keith.busch at intel.com>
Picked up for this series.
--
Jens Axboe
WARNING: multiple messages have this Message-ID (diff)
From: Jens Axboe <axboe@fb.com>
To: Keith Busch <keith.busch@intel.com>, Arnd Bergmann <arnd@arndb.de>
Cc: <linux-nvme@lists.infradead.org>,
Matthew Wilcox <willy@linux.intel.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] NVMe: fix type warning on 32-bit
Date: Fri, 29 May 2015 10:06:41 -0600 [thread overview]
Message-ID: <55688E91.10408@fb.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1505282235140.15930@localhost.lm.intel.com>
On 05/28/2015 04:35 PM, Keith Busch wrote:
> On Tue, 19 May 2015, Arnd Bergmann wrote:
>> A recent change to the ioctl handling caused a new harmless
>> warning in the NVMe driver on all 32-bit machines:
>>
>> drivers/block/nvme-core.c: In function 'nvme_submit_io':
>> drivers/block/nvme-core.c:1794:29: warning: cast to pointer from
>> integer of different size [-Wint-to-pointer-cast]
>>
>> In order to shup up that warning, this introduces a new
>> temporary variable that uses a double cast to extract
>> the pointer from an __u64 structure member.
>
>
> Thanks for the fix.
>
> Acked-by: Keith Busch <keith.busch@intel.com>
Picked up for this series.
--
Jens Axboe
next prev parent reply other threads:[~2015-05-29 16:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-19 15:05 [PATCH] NVMe: fix type warning on 32-bit Arnd Bergmann
2015-05-19 15:05 ` Arnd Bergmann
2015-05-28 22:35 ` Keith Busch
2015-05-28 22:35 ` Keith Busch
2015-05-29 16:06 ` Jens Axboe [this message]
2015-05-29 16:06 ` 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=55688E91.10408@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.