From: chambilkethakur@gmail.com (Anuz Pratap Singh Tomar)
To: kernelnewbies@lists.kernelnewbies.org
Subject: adding a system call
Date: Tue, 22 Feb 2011 21:21:05 +0000 [thread overview]
Message-ID: <AANLkTinaZnexN2E7JS6BSwjXiF9rBXU00Lg_s++Y8tzz@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=cDoh=tbVeYow+GefsoHJ+vQUVVVf1fhvZGgNO@mail.gmail.com>
On Tue, Feb 22, 2011 at 6:44 PM, mohit verma <mohit89mlnc@gmail.com> wrote:
> ok mulyadi ,
> i got u late what u wanted to see . here are the diff files
> sorry for delay.
>
>
There is a good illustration of "how to add syscalls to kernel" y given in
Robert Love's book LKD, refer it.
when you attach files like these please follow a convention like naming them
as mypatch.patch, mypatch.diff or even mypatch.txt. not all mail clients can
read these files and may drop them.
Please DON'T top post, its annoying.
For coding standards please refer for coding style guide by Linus, its
inside the Documentation directory inside the kernel source.
There are many utilities like patchcheck.pl and indent, which can make your
code more readable.
-A
>
> On Wed, Feb 23, 2011 at 12:09 AM, Mulyadi Santosa <
> mulyadi.santosa at gmail.com> wrote:
>
>> On Wed, Feb 23, 2011 at 01:19, mohit verma <mohit89mlnc@gmail.com> wrote:
>> > and i added:
>> > 1. #define __NR_hariohm 264
>> > __SYSCALL(__NR_hariohm, sys_hariohm) in unistd.h file.
>>
>> grepping inside unistd.h, I got
>>
>> #undef __NR_syscalls
>> #define __NR_syscalls 264
>>
>> So, it seems that you violate one rule: you add a syscall but didn't
>> increase the number of total syscalls registered.
>>
>> Am I right or am I right?
>>
>> --
>> regards,
>>
>> Mulyadi Santosa
>> Freelance Linux trainer and consultant
>>
>> blog: the-hydra.blogspot.com
>> training: mulyaditraining.blogspot.com
>>
>
>
>
> --
> ........................
> *MOHIT VERMA*
>
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20110222/c2278f6a/attachment.html
prev parent reply other threads:[~2011-02-22 21:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-22 15:14 adding a system call mohit verma
2011-02-22 15:18 ` mohit verma
2011-02-22 17:50 ` Mulyadi Santosa
2011-02-22 18:01 ` mohit verma
2011-02-22 18:10 ` Mulyadi Santosa
2011-02-22 18:19 ` mohit verma
2011-02-22 18:39 ` Mulyadi Santosa
2011-02-22 18:44 ` mohit verma
2011-02-22 21:21 ` Anuz Pratap Singh Tomar [this message]
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=AANLkTinaZnexN2E7JS6BSwjXiF9rBXU00Lg_s++Y8tzz@mail.gmail.com \
--to=chambilkethakur@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).