From: Randy Dunlap <rdunlap@infradead.org>
To: Mike Snitzer <snitzer@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ingo Molnar <mingo@redhat.com>, Arnd Bergmann <arnd@arndb.de>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
dm-devel@redhat.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for Jun 4 (md/dm-writecache.c)
Date: Mon, 4 Jun 2018 11:27:55 -0700 [thread overview]
Message-ID: <7b566935-a03d-ecab-be2a-10e25e4554f6@infradead.org> (raw)
In-Reply-To: <20180604182259.GA5440@redhat.com>
On 06/04/2018 11:22 AM, Mike Snitzer wrote:
> On Mon, Jun 04 2018 at 12:06pm -0400,
> Randy Dunlap <rdunlap@infradead.org> wrote:
>
>> On 06/04/2018 04:59 AM, Stephen Rothwell wrote:
>>> Hi all,
>>>
>>> Changes since 20180601:
>>>
>>
>> on x86_64:
>>
>> In file included from ../drivers/md/dm-writecache.c:8:0:
>> ../drivers/md/dm-writecache.c: In function ‘writecache_status’:
>> ../include/linux/compiler.h:61:17: warning: format ‘%ld’ expects argument of type ‘long int’, but argument 4 has type ‘int’ [-Wformat=]
>> static struct ftrace_branch_data \
>> ^
>> ../include/linux/device-mapper.h:550:46: note: in definition of macro ‘DMEMIT’
>> 0 : scnprintf(result + sz, maxlen - sz, x))
>> ^
>> ../include/linux/compiler.h:48:24: note: in expansion of macro ‘__branch_check__’
>> # define unlikely(x) (__branch_check__(x, 0, __builtin_constant_p(x)))
>> ^
>> ../drivers/md/dm-writecache.c:414:35: note: in expansion of macro ‘unlikely’
>> #define writecache_has_error(wc) (unlikely(READ_ONCE((wc)->error)))
>> ^
>> ../include/linux/compiler.h:56:23: note: in expansion of macro ‘__trace_if’
>> #define if(cond, ...) __trace_if( (cond , ## __VA_ARGS__) )
>> ^
>> ../include/linux/compiler.h:251:2: note: in expansion of macro ‘if’
>> if (check) \
>> ^
>> ../include/linux/compiler.h:258:22: note: in expansion of macro ‘__READ_ONCE’
>> #define READ_ONCE(x) __READ_ONCE(x, 1)
>> ^
>> ../drivers/md/dm-writecache.c:414:44: note: in expansion of macro ‘READ_ONCE’
>> #define writecache_has_error(wc) (unlikely(READ_ONCE((wc)->error)))
>> ^
>> ../drivers/md/dm-writecache.c:2196:32: note: in expansion of macro ‘writecache_has_error’
>> DMEMIT("%ld %llu %llu %llu", writecache_has_error(wc),
>> ^
>>
>> s/%ld/%d/
>
> AFAICT, this is the correct fix:
> https://patchwork.kernel.org/patch/10438865/
>
> Not seen any response to it (Steven and Ingo were emailed, Arnd and LKML
> were cc'd).
Yes, thanks. That looks good.
--
~Randy
next prev parent reply other threads:[~2018-06-04 18:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-04 11:59 linux-next: Tree for Jun 4 Stephen Rothwell
2018-06-04 16:06 ` linux-next: Tree for Jun 4 (md/dm-writecache.c) Randy Dunlap
2018-06-04 18:22 ` Mike Snitzer
2018-06-04 18:27 ` Randy Dunlap [this message]
2018-06-04 19:31 ` Steven Rostedt
2018-06-04 16:12 ` linux-next: Tree for Jun 4 (fs/afs/) Randy Dunlap
2018-06-14 15:08 ` David Howells
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=7b566935-a03d-ecab-be2a-10e25e4554f6@infradead.org \
--to=rdunlap@infradead.org \
--cc=arnd@arndb.de \
--cc=dm-devel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=sfr@canb.auug.org.au \
--cc=snitzer@redhat.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