From: Valdis.Kletnieks@vt.edu (Valdis.Kletnieks at vt.edu)
To: kernelnewbies@lists.kernelnewbies.org
Subject: remote system call
Date: Sat, 05 Mar 2016 16:58:07 -0500 [thread overview]
Message-ID: <80466.1457215087@turing-police.cc.vt.edu> (raw)
In-Reply-To: <CAKfJ7KKquo-6zH2PNf_OSTU89tkyuwajZBgdKPT5jBSh3M+1iQ@mail.gmail.com>
On Sat, 05 Mar 2016 15:58:13 +0530, Nitin Varyani said:
> Codes are huge and documentation is negligible. How can I separate whay I
> want to achieve from that big code?
Why do you think that's possible?
It's a lot more complicated problem to solve than you think. Maybe
that huge code is necessary to achieve what you are trying to do.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 848 bytes
Desc: not available
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20160305/4ada2ae2/attachment.bin
next prev parent reply other threads:[~2016-03-05 21:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-03 11:12 remote system call Nitin Varyani
2016-03-03 16:37 ` Mulyadi Santosa
2016-03-05 10:28 ` Nitin Varyani
2016-03-05 21:58 ` Valdis.Kletnieks at vt.edu [this message]
2016-03-12 17:00 ` Nicholas Mc Guire
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=80466.1457215087@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--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).