From: Peng Haitao <penght@cn.fujitsu.com>
To: yanegomi@gmail.com
Cc: ltp-list@lists.sourceforge.net
Subject: [LTP] [PATCH] Fix a building error.
Date: Fri, 14 Jan 2011 17:48:33 +0800 [thread overview]
Message-ID: <4D301BF1.8070101@cn.fujitsu.com> (raw)
Hi Garrett,
A build error is caught after applied commit bacc849720ec4efda5a0a8a9ea6a0e93a1415541.
Signed-off-by: Peng Haitao <penght@cn.fujitsu.com>
---
testcases/kernel/syscalls/mallopt/mallopt01.c | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/testcases/kernel/syscalls/mallopt/mallopt01.c b/testcases/kernel/syscalls/mallopt/mallopt01.c
index d356cb2..26307a6 100644
--- a/testcases/kernel/syscalls/mallopt/mallopt01.c
+++ b/testcases/kernel/syscalls/mallopt/mallopt01.c
@@ -37,6 +37,7 @@
#ifdef CONFIG_COLDFIRE
#define __MALLOC_STANDARD__
#endif
+#include <malloc.h>
#include <stdlib.h>
#include <errno.h>
--
1.7.0.4
--
Best Regards,
Peng Haitao
------------------------------------------------------------------------------
Protect Your Site and Customers from Malware Attacks
Learn about various malware tactics and how to avoid them. Understand
malware threats, the impact they can have on your business, and how you
can protect your company and customers by using code signing.
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next reply other threads:[~2011-01-14 9:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-14 9:48 Peng Haitao [this message]
2011-01-14 12:58 ` [LTP] [PATCH] Fix a building error Cyril Hrubis
2011-01-14 21:24 ` Mike Frysinger
2011-01-14 21:33 ` Garrett Cooper
2011-01-14 21:46 ` Mike Frysinger
2011-01-14 21:52 ` Garrett Cooper
2011-01-14 22:12 ` Mike Frysinger
-- strict thread matches above, loose matches on Subject: below --
2011-01-14 9:31 Peng Haitao
2011-01-28 8:24 ` Peng Haitao
2011-02-14 9:45 ` Peng Haitao
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=4D301BF1.8070101@cn.fujitsu.com \
--to=penght@cn.fujitsu.com \
--cc=ltp-list@lists.sourceforge.net \
--cc=yanegomi@gmail.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