From: sertacolgunsoylu@gmail.com (Sertaç Olgunsoylu)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Include directories
Date: Wed, 14 Mar 2012 23:45:55 -0700 [thread overview]
Message-ID: <CAEDT7TWZ-VMWdDTnczAxncq_AvbTzF1+4eT0qoM_wWAkutHQjw@mail.gmail.com> (raw)
Hi,
While I was doing some reading on system calls, I did a search for
"syscalls.h" to find the header file in LXR. The search results puzzled me.
There is a dozen of "syscalls.h" files coming from directories under
"arch/_arch_name_/include/asm". These are ok, they are architecture
specific definitions or something else needed. The question is why do we
have two different "syscalls.h" headers under both /include/linux and
/include/asm-generic?
Also, I want to understand that what /include/linux headers are for and
what /include/asm-generic headers are for. How do they differentiate
between each other? What is the logic behind having two separate header
folders? How do they relate to each other?
Thanks
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20120314/2ef10681/attachment-0001.html
next reply other threads:[~2012-03-15 6:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-15 6:45 Sertaç Olgunsoylu [this message]
2012-03-27 21:40 ` Include directories Cihangir Aktürk
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=CAEDT7TWZ-VMWdDTnczAxncq_AvbTzF1+4eT0qoM_wWAkutHQjw@mail.gmail.com \
--to=sertacolgunsoylu@gmail.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).