From: Jan Stancek <jstancek@redhat.com>
To: Xiaoguang Wang <wangxg.fnst@cn.fujitsu.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH] syscalls/getrandom: add configure check for linux/random.h
Date: Wed, 22 Jul 2015 04:16:51 -0400 (EDT) [thread overview]
Message-ID: <825821983.1905967.1437553011524.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <1437532823-19315-1-git-send-email-wangxg.fnst@cn.fujitsu.com>
----- Original Message -----
> From: "Xiaoguang Wang" <wangxg.fnst@cn.fujitsu.com>
> To: ltp-list@lists.sourceforge.net
> Sent: Wednesday, 22 July, 2015 4:40:23 AM
> Subject: [LTP] [PATCH] syscalls/getrandom: add configure check for linux/random.h
>
> For simplicity, I think we should just verify whether 'linux/random.h'
> is valid, here if it's valid, that means such codes will be compiled
> correctly.
>
> #include <linux/random.h>
> int main(void)
> {
> getrandom(NULL, 100, 0);
> return 0;
> }
> Signed-off-by: Xiaoguang Wang <wangxg.fnst@cn.fujitsu.com>
I added paragraph about autoconf behaviour before 2.64, removed
getrandom() call from commit message and pushed.
Thank you,
Jan
------------------------------------------------------------------------------
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2015-07-22 8:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <371268015.770228.1437399185640.JavaMail.zimbra@redhat.com>
2015-07-22 2:40 ` [LTP] [PATCH] syscalls/getrandom: add configure check for linux/random.h Xiaoguang Wang
2015-07-22 8:16 ` Jan Stancek [this message]
2015-07-22 8:14 ` Xiaoguang Wang
2015-07-13 12:11 Jan Stancek
2015-07-13 13:03 ` Cyril Hrubis
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=825821983.1905967.1437553011524.JavaMail.zimbra@redhat.com \
--to=jstancek@redhat.com \
--cc=ltp-list@lists.sourceforge.net \
--cc=wangxg.fnst@cn.fujitsu.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