From: Brian Norris <computersforpeace@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Graham Moore <grmoore@opensource.altera.com>,
Marek Vasut <marex@denx.de>
Subject: Re: linux-next: build failure after merge of the l2-mtd tree
Date: Mon, 18 Jul 2016 18:20:39 -0700 [thread overview]
Message-ID: <20160719012039.GA18583@google.com> (raw)
In-Reply-To: <20160719105930.39012675@canb.auug.org.au>
On Tue, Jul 19, 2016 at 10:59:30AM +1000, Stephen Rothwell wrote:
> Hi Brian,
>
> After merging the l2-mtd tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/mtd/spi-nor/cadence-quadspi.c: In function 'cqspi_indirect_read_execute':
> drivers/mtd/spi-nor/cadence-quadspi.c:529:4: error: implicit declaration of function 'readsl' [-Werror=implicit-function-declaration]
> readsl(ahb_base, rxbuf, DIV_ROUND_UP(bytes_to_read, 4));
> ^
> drivers/mtd/spi-nor/cadence-quadspi.c: In function 'cqspi_indirect_write_execute':
> drivers/mtd/spi-nor/cadence-quadspi.c:613:3: error: implicit declaration of function 'writesl' [-Werror=implicit-function-declaration]
> writesl(cqspi->ahb_base, txbuf, DIV_ROUND_UP(write_bytes, 4));
> ^
>
> Caused by commit
>
> 140623410536 ("mtd: spi-nor: Add driver for Cadence Quad SPI Flash Controller")
Known:
http://lists.infradead.org/pipermail/linux-mtd/2016-July/068569.html
> Missing include of linux/io.h ...
It's not missing linux/io.h; x86 is missing readsl()/writesl(). If x86
folks don't have a solution, then I guess we'll just make this depend on
!X86.
> I have used the l2-mtd tree from next-20160718 for today.
Regards,
Brian
next prev parent reply other threads:[~2016-07-19 1:20 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-19 0:59 linux-next: build failure after merge of the l2-mtd tree Stephen Rothwell
2016-07-19 1:20 ` Brian Norris [this message]
2016-07-19 1:46 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2017-08-28 2:19 Stephen Rothwell
2017-08-28 22:06 ` Brian Norris
2017-02-09 1:08 Stephen Rothwell
2017-02-09 1:59 ` Brian Norris
2017-02-09 1:59 ` Brian Norris
2015-12-21 5:47 Stephen Rothwell
2015-09-30 5:16 Stephen Rothwell
2014-05-22 5:30 Stephen Rothwell
2014-05-26 17:42 ` Brian Norris
2014-05-26 23:59 ` Stephen Rothwell
2014-05-27 10:40 ` Artem Bityutskiy
2014-05-27 22:49 ` Stephen Rothwell
2012-10-12 0:14 Stephen Rothwell
2012-10-12 4:51 ` Dinh Nguyen
2012-10-12 4:51 ` Dinh Nguyen
2012-10-18 0:28 ` Stephen Rothwell
2012-10-18 9:26 ` Artem Bityutskiy
2012-02-07 2:58 Stephen Rothwell
2012-02-07 8:02 ` Artem Bityutskiy
2012-02-06 1:07 Stephen Rothwell
2012-02-06 1:07 ` Stephen Rothwell
2012-02-06 9:14 ` Artem Bityutskiy
2012-02-06 9:14 ` Artem Bityutskiy
2012-02-06 21:10 ` Stephen Rothwell
2012-02-06 21:10 ` 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=20160719012039.GA18583@google.com \
--to=computersforpeace@gmail.com \
--cc=grmoore@opensource.altera.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=marex@denx.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.