From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Ben Dooks <ben-linux@fluff.org>
Subject: linux-next: build failure after merge of the devicetree tree
Date: Wed, 5 Oct 2011 16:24:14 +1100 [thread overview]
Message-ID: <20111005162414.da7b35fd2baf34efa63d2f2a@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 646 bytes --]
Hi Grant,
After merging the devicetree tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/tty/serial/altera_jtaguart.c:483:3: error: implicit declaration of function 'of_match_ptr' [-Werror=implicit-function-declaration]
drivers/tty/serial/altera_jtaguart.c:483:34: error: 'altera_jtaguart_match' undeclared here (not in a function)
Caused by commit 85888069cf5d ("tty: use of_match_ptr() for
of_match_table entry").
I have used the version of the devicetree tree from next-20111004 for
today.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2011-10-05 5:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-05 5:24 Stephen Rothwell [this message]
2011-10-05 5:54 ` linux-next: build failure after merge of the devicetree tree Grant Likely
-- strict thread matches above, loose matches on Subject: below --
2023-12-11 5:05 Stephen Rothwell
2023-12-12 9:04 ` Sibi Sankar
2024-01-19 0:58 ` Stephen Rothwell
2024-01-19 14:07 ` Rob Herring
2023-12-08 2:51 Stephen Rothwell
2023-12-08 7:34 ` Krzysztof Kozlowski
2023-12-07 1:57 Stephen Rothwell
2023-12-07 15:11 ` Rob Herring
2023-12-07 20:58 ` Stephen Rothwell
2023-12-07 22:05 ` Rob Herring
2023-12-08 3:11 ` Stephen Rothwell
2023-04-11 2:28 Stephen Rothwell
2014-05-26 5:05 Stephen Rothwell
2014-05-26 7:22 ` Thomas Petazzoni
2010-07-30 3:57 Stephen Rothwell
2010-07-30 6:11 ` Grant Likely
2010-07-15 2:15 Stephen Rothwell
2010-07-15 6:06 ` Grant Likely
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=20111005162414.da7b35fd2baf34efa63d2f2a@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=ben-linux@fluff.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
/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).