From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Cyrille Pitchen <cyrille.pitchen@atmel•com>
Cc: Linux-Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Brian Norris <computersforpeace@gmail•com>
Subject: linux-next: build failure after merge of the spi-nor tree
Date: Thu, 4 May 2017 10:51:42 +1000 [thread overview]
Message-ID: <20170504105142.0ebe23ba@canb.auug.org.au> (raw)
Hi Cyrille,
After merging the spi-nor tree, today's linux-next build (x86_64
allmodconfig) failed like this:
In file included from include/linux/printk.h:329:0,
from include/linux/kernel.h:13,
from include/linux/clk.h:16,
from drivers/mtd/spi-nor/stm32-quadspi.c:8:
drivers/mtd/spi-nor/stm32-quadspi.c: In function 'stm32_qspi_read':
drivers/mtd/spi-nor/stm32-quadspi.c:378:21: warning: format '%x' expects argument of type 'unsigned int', but argument 7 has type 'size_t {aka long unsigned int}' [-Wformat=]
dev_dbg(qspi->dev, "read(%#.2x): buf:%p from:%#.8x len:%#x\n",
^
include/linux/dynamic_debug.h:134:39: note: in definition of macro 'dynamic_dev_dbg'
__dynamic_dev_dbg(&descriptor, dev, fmt, \
^
drivers/mtd/spi-nor/stm32-quadspi.c:378:2: note: in expansion of macro 'dev_dbg'
dev_dbg(qspi->dev, "read(%#.2x): buf:%p from:%#.8x len:%#x\n",
^
drivers/mtd/spi-nor/stm32-quadspi.c: In function 'stm32_qspi_write':
drivers/mtd/spi-nor/stm32-quadspi.c:405:15: warning: format '%x' expects argument of type 'unsigned int', but argument 7 has type 'size_t {aka long unsigned int}' [-Wformat=]
dev_dbg(dev, "write(%#.2x): buf:%p to:%#.8x len:%#x\n",
^
include/linux/dynamic_debug.h:134:39: note: in definition of macro 'dynamic_dev_dbg'
__dynamic_dev_dbg(&descriptor, dev, fmt, \
^
drivers/mtd/spi-nor/stm32-quadspi.c:405:2: note: in expansion of macro 'dev_dbg'
dev_dbg(dev, "write(%#.2x): buf:%p to:%#.8x len:%#x\n",
^
drivers/mtd/spi-nor/stm32-quadspi.c: In function 'stm32_qspi_flash_setup':
drivers/mtd/spi-nor/stm32-quadspi.c:543:27: error: 'SZ_1K' undeclared (first use in this function)
flash->fsize = FSIZE_VAL(SZ_1K);
^
drivers/mtd/spi-nor/stm32-quadspi.c:110:33: note: in definition of macro 'FSIZE_VAL'
#define FSIZE_VAL(size) (__fls(size) - 1)
^
drivers/mtd/spi-nor/stm32-quadspi.c:543:27: note: each undeclared identifier is reported only once for each function it appears in
flash->fsize = FSIZE_VAL(SZ_1K);
^
drivers/mtd/spi-nor/stm32-quadspi.c:110:33: note: in definition of macro 'FSIZE_VAL'
#define FSIZE_VAL(size) (__fls(size) - 1)
^
Exposed by commit
7a754f2016a0 ("mtd: spi-nor: stm32-quadspi: allow building with COMPILE_TEST")
I have used the spi-nor tree from next-20170503 for today.
--
Cheers,
Stephen Rothwell
next reply other threads:[~2017-05-04 0:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-04 0:51 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-06-21 2:19 linux-next: build failure after merge of the spi-nor tree Stephen Rothwell
2017-06-21 22:37 ` Cyrille Pitchen
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=20170504105142.0ebe23ba@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=computersforpeace@gmail$(echo .)com \
--cc=cyrille.pitchen@atmel$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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