On Tue, Feb 22, 2011 at 6:44 PM, mohit verma <[email protected]> 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 < > [email protected]> wrote: > >> On Wed, Feb 23, 2011 at 01:19, mohit verma <[email protected]> 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 > [email protected] > http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies > >
_______________________________________________ Kernelnewbies mailing list [email protected] http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
