From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>, linux-next@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org,
Trond Myklebust <trond.myklebust@primarydata.com>,
Anna Schumaker <anna.schumaker@netapp.com>
Subject: Re: linux-next: Tree for Feb 24 (nfs/blocklayout)
Date: Fri, 24 Feb 2017 10:14:02 -0800 [thread overview]
Message-ID: <3df46d20-3b1c-98ee-8466-021b8ae44919@infradead.org> (raw)
In-Reply-To: <20170224140153.41e07762@canb.auug.org.au>
On 02/23/17 19:01, Stephen Rothwell wrote:
> Hi all,
>
> Please do not add any material intended for v4.12 to your linux-next
> included branches until after v4.11-rc1 has been released.
>
> Changes since 20170223:
>
on i386, when CONFIG_LBDAF is not enabled:
../fs/nfs/blocklayout/blocklayout.c:227:9: warning: large integer implicitly truncated to unsigned type [-Woverflow]
../fs/nfs/blocklayout/blocklayout.c:284:4: warning: large integer implicitly truncated to unsigned type [-Woverflow]
../fs/nfs/blocklayout/blocklayout.c:371:9: warning: large integer implicitly truncated to unsigned type [-Woverflow]
../fs/nfs/blocklayout/blocklayout.c:446:2: warning: large integer implicitly truncated to unsigned type [-Woverflow]
../fs/nfs/blocklayout/blocklayout.c:724:3: warning: large integer implicitly truncated to unsigned type [-Woverflow]
--
~Randy
parent reply other threads:[~2017-02-24 18:14 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20170224140153.41e07762@canb.auug.org.au>]
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=3df46d20-3b1c-98ee-8466-021b8ae44919@infradead.org \
--to=rdunlap@infradead.org \
--cc=anna.schumaker@netapp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=trond.myklebust@primarydata.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;
as well as URLs for NNTP newsgroup(s).