From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: linux-next: Tree for Feb 5 (btrfs/zstd)
Date: Tue, 5 Feb 2019 09:40:40 -0800 [thread overview]
Message-ID: <26ce21e5-0e3c-d847-c895-6cb166507441@infradead.org> (raw)
In-Reply-To: <20190205171228.41a9f771@canb.auug.org.au>
On 2/4/19 10:12 PM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20190204:
>
on i386:
../fs/btrfs/zstd.c: In function ‘zstd_reclaim_timer_fn’:
../fs/btrfs/zstd.c:27:35: warning: integer overflow in expression [-Woverflow]
#define ZSTD_BTRFS_RECLAIM_NS (45 * NSEC_PER_SEC)
^
../fs/btrfs/zstd.c:96:33: note: in expansion of macro ‘ZSTD_BTRFS_RECLAIM_NS’
if (now < victim->last_used + ZSTD_BTRFS_RECLAIM_NS)
^
--
~Randy
next parent reply other threads:[~2019-02-05 17:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190205171228.41a9f771@canb.auug.org.au>
2019-02-05 17:40 ` Randy Dunlap [this message]
2019-02-05 18:25 ` linux-next: Tree for Feb 5 (btrfs/zstd) David Sterba
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=26ce21e5-0e3c-d847-c895-6cb166507441@infradead.org \
--to=rdunlap@infradead.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).