From: Dave Young <dyoung@redhat.com>
To: kexec@lists.infradead.org
Subject: build fix: use __func__ instead of __function__
Date: Mon, 12 Dec 2011 17:30:45 +0800 [thread overview]
Message-ID: <20111212093045.GA20934@darkstar.nay.redhat.com> (raw)
Below build failure happens:
kexec/crashdump.c: In function ‘get_crash_notes_per_cpu’:
kexec/crashdump.c:106: error: ‘__function__’ undeclared (first use in this function)
kexec/crashdump.c:106: error: (Each undeclared identifier is reported only once
kexec/crashdump.c:106: error: for each function it appears in.)
make: *** [kexec/crashdump.o] Error 1
change to use __func__ instead of __function to fix this issue.
---
kexec/crashdump.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/kexec/crashdump.c b/kexec/crashdump.c
index e7ac42c..db4a31e 100644
--- a/kexec/crashdump.c
+++ b/kexec/crashdump.c
@@ -103,7 +103,7 @@ int get_crash_notes_per_cpu(int cpu, uint64_t *addr, uint64_t *len)
*addr = (uint64_t) temp;
*len = MAX_NOTE_BYTES; /* we should get this from the kernel instead */
#ifdef DEBUG
- printf("%s: crash_notes addr = %Lx\n", __function__, *addr);
+ printf("%s: crash_notes addr = %Lx\n", __func__, *addr);
#endif
fclose(fp);
--
1.7.4.4
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
reply other threads:[~2011-12-12 9:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20111212093045.GA20934@darkstar.nay.redhat.com \
--to=dyoung@redhat.com \
--cc=kexec@lists.infradead.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).