From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: How to test a syscall prior to compiling the kernel
Date: Tue, 3 Jun 2014 20:52:23 -0700 [thread overview]
Message-ID: <20140604035223.GA28272@kroah.com> (raw)
In-Reply-To: <CAEK-7JLTa6ZW0jJ3Zu7YekX43Onu0jbiYyxgBK+0QS-eGwChbA@mail.gmail.com>
On Wed, Jun 04, 2014 at 08:52:31AM +0530, Dipanjan Das wrote:
>
> Hi,
>
> While adding a syscall, how do I test the syscall code itself? If I simply try
> to compile the C file individually, will the compiler be able find the
> includes?
Did you try:
man 2 syscall
greg k-h
next prev parent reply other threads:[~2014-06-04 3:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-04 3:22 How to test a syscall prior to compiling the kernel Dipanjan Das
2014-06-04 3:52 ` Greg KH [this message]
2014-06-04 3:59 ` Dipanjan Das
2014-06-04 4:14 ` Augusto Mecking Caringi
2014-06-04 4:19 ` Greg KH
[not found] ` <CAOUBrm3BQyVJys4++o6zPUVxp7+dDSvPiF9MFpOUzSLpyzhN7g@mail.gmail.com>
2014-06-04 8:24 ` navid Rahimi
2014-06-04 15:51 ` Andev
2014-06-04 17:56 ` Valdis.Kletnieks at vt.edu
2014-06-04 18:33 ` Andev
2014-06-04 18:42 ` Greg KH
2014-06-04 19:02 ` Andev
2014-06-04 22:14 ` Greg KH
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=20140604035223.GA28272@kroah.com \
--to=greg@kroah.com \
--cc=kernelnewbies@lists.kernelnewbies.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).