From: Guenter Roeck <linux@roeck-us.net>
To: Rob Herring <rob.herring@calxeda.com>
Cc: James Hogan <james.hogan@imgtec.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-next@vger.kernel.org, linux-metag@vger.kernel.org
Subject: Commit f26150004 (metag: use common of_flat_dt_match_machine) causes metag build failures in linux-next
Date: Sun, 06 Oct 2013 11:26:26 -0700 [thread overview]
Message-ID: <5251AB52.3000506@roeck-us.net> (raw)
arch/metag/kernel/devtree.c: In function 'setup_machine_fdt':
arch/metag/kernel/devtree.c:52: error: 'arch_get_next_mach' undeclared (first use in this function)
arch/metag/kernel/devtree.c:52: error: (Each undeclared identifier is reported only once
arch/metag/kernel/devtree.c:52: error: for each function it appears in.)
arch/metag/kernel/devtree.c:52: warning: assignment discards qualifiers from pointer target type
make[1]: *** [arch/metag/kernel/devtree.o] Error 1
Not surprising, since arch_get_next_mach() is not defined for metag.
Guenter
next reply other threads:[~2013-10-06 18:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-06 18:26 Guenter Roeck [this message]
2013-10-07 9:43 ` Commit f26150004 (metag: use common of_flat_dt_match_machine) causes metag build failures in linux-next James Hogan
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=5251AB52.3000506@roeck-us.net \
--to=linux@roeck-us.net \
--cc=james.hogan@imgtec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-metag@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rob.herring@calxeda.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