From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Simon Horman <horms@verge.net.au>
Cc: Fengguang Wu <fengguang.wu@intel.com>,
kbuild-all@01.org, Tejun Heo <tj@kernel.org>,
Linux-SH <linux-sh@vger.kernel.org>,
linux-ide@vger.kernel.org,
Vladimir Barinov <vladimir.barinov@cogentembedded.com>
Subject: Re: drivers/ata/sata_rcar.c:183:2: warning: large integer implicitly truncated to unsigned type
Date: Tue, 04 Jun 2013 14:05:20 +0400 [thread overview]
Message-ID: <51ADBBE0.2020408@cogentembedded.com> (raw)
In-Reply-To: <20130604014521.GN23054@verge.net.au>
Hello.
On 04-06-2013 5:45, Simon Horman wrote:
> could you look into a fix for this?
> I believe that it is a result of my patch "libata: do not limit R-Car SATA
> driver to shmobile", which now allows the R-Car SATA driver to be compiled
> for a (much) wider range of hardware.
It is a result of compiling with gcc 4.8. As Tejun wrote, the warning
has been already fixed and the fix queued in his tree.
WBR, Sergei
WARNING: multiple messages have this Message-ID (diff)
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Simon Horman <horms@verge.net.au>
Cc: Fengguang Wu <fengguang.wu@intel.com>,
kbuild-all@01.org, Tejun Heo <tj@kernel.org>,
Linux-SH <linux-sh@vger.kernel.org>,
linux-ide@vger.kernel.org,
Vladimir Barinov <vladimir.barinov@cogentembedded.com>
Subject: Re: drivers/ata/sata_rcar.c:183:2: warning: large integer implicitly truncated to unsigned type
Date: Tue, 04 Jun 2013 10:05:20 +0000 [thread overview]
Message-ID: <51ADBBE0.2020408@cogentembedded.com> (raw)
In-Reply-To: <20130604014521.GN23054@verge.net.au>
Hello.
On 04-06-2013 5:45, Simon Horman wrote:
> could you look into a fix for this?
> I believe that it is a result of my patch "libata: do not limit R-Car SATA
> driver to shmobile", which now allows the R-Car SATA driver to be compiled
> for a (much) wider range of hardware.
It is a result of compiling with gcc 4.8. As Tejun wrote, the warning
has been already fixed and the fix queued in his tree.
WBR, Sergei
next prev parent reply other threads:[~2013-06-04 10:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <51a59c1b.AMyrU/XAl1VcZ02t%fengguang.wu@intel.com>
[not found] ` <20130529072447.GC12650@localhost>
2013-06-04 1:45 ` drivers/ata/sata_rcar.c:183:2: warning: large integer implicitly truncated to unsigned type Simon Horman
2013-06-04 1:45 ` Simon Horman
2013-06-04 1:46 ` Tejun Heo
2013-06-04 1:46 ` Tejun Heo
2013-06-04 10:05 ` Sergei Shtylyov [this message]
2013-06-04 10:05 ` Sergei Shtylyov
2013-06-04 13:18 ` Simon Horman
2013-06-04 13:18 ` Simon Horman
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=51ADBBE0.2020408@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=fengguang.wu@intel.com \
--cc=horms@verge.net.au \
--cc=kbuild-all@01.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=tj@kernel.org \
--cc=vladimir.barinov@cogentembedded.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.