linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: yangerkun <yangerkun@huawei.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	Alasdair G Kergon <agk@redhat.com>,
	Mike Snitzer <snitzer@redhat.com>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	Bryan Gurney <bgurney@redhat.com>
Subject: Re: linux-next: build warning after merge of the device-mapper tree
Date: Thu, 9 Jul 2020 12:38:30 +0800	[thread overview]
Message-ID: <a6ff1a7c-628d-449e-f177-c4d23efbcd07@huawei.com> (raw)
In-Reply-To: <20200709132609.6de53604@canb.auug.org.au>

在 2020/7/9 11:26, Stephen Rothwell 写道:
> Hi all,
> 
> After merging the device-mapper tree, today's linux-next build (x86_64
> allmodconfig) produced this warning:
> 
> In file included from drivers/md/dm-dust.c:11:
> drivers/md/dm-dust.c: In function 'dust_list_badblocks':
> drivers/md/dm-dust.c:307:10: warning: zero-length gnu_printf format string [-Wformat-zero-length]
>    307 |   DMEMIT("");
Mike and Bryan,

Should we just use "DMEMIT("\n")"? Maybe it's bad since this lead a
blank line...


>        |          ^~
> include/linux/device-mapper.h:555:46: note: in definition of macro 'DMEMIT'
>    555 |      0 : scnprintf(result + sz, maxlen - sz, x))
>        |                                              ^
> 
> Introduced by commit
> 
>    20f93ea74f9c ("dm dust: add interface to list all badblocks")
> 


  reply	other threads:[~2020-07-09  4:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-09  3:26 linux-next: build warning after merge of the device-mapper tree Stephen Rothwell
2020-07-09  4:38 ` yangerkun [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-08  3:42 Stephen Rothwell
2021-07-21  7:34 Stephen Rothwell
2021-08-10  9:31 ` Stephen Rothwell
2021-01-22  6:56 Stephen Rothwell
2019-02-20  2:15 Stephen Rothwell
2019-02-20  3:35 ` Mike Snitzer
2018-09-18  1:53 Stephen Rothwell
2017-12-11  2:05 Stephen Rothwell
2017-12-11  5:24 ` Mike Snitzer
2017-12-11  5:43   ` Stephen Rothwell

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=a6ff1a7c-628d-449e-f177-c4d23efbcd07@huawei.com \
    --to=yangerkun@huawei.com \
    --cc=agk@redhat.com \
    --cc=bgurney@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).