kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: valdis.kletnieks@vt.edu (valdis.kletnieks at vt.edu)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Need Suggestions
Date: Wed, 18 Jul 2018 19:10:20 -0400	[thread overview]
Message-ID: <63045.1531955420@turing-police.cc.vt.edu> (raw)
In-Reply-To: <20180718142941.0cc9b290@user-Satellite-A100>

On Wed, 18 Jul 2018 14:29:41 -0700, Dave Stevens said:
> On Wed, 18 Jul 2018 18:19:05 -0300 "Daniel." <danielhilst@gmail.com> wrote:
>
> > > Hi Athul...
> > > This is my collegemate's writing, ... This will solve all your
> > > confusions....
> > >
>
> is it the policy on this list to trim?

Only the irrelevant parts, leave the parts that are the context for the reply.
So that *should* have been trimmed down to:

---
> 4) Without hesitation buy,?Robert Love's Linux Kernel Programming?book. It is
> one of the best beginner material and start reading it parallel to the OS book.
> This is easier to read than the previous one and more practical. But the
> previous one adds more value and is more theoretical. Handle (3) and (4) in
> parallel without blocking on any of the other activities.

I can confirm, this book is GOOOOOOD! Also check LDD3,? it's open and online
available, you may find some of it's authors in this mailist! :-). http://
www.makelinux.net/ldd3/ it's a outdated but it was a very valuable source to
me. You can find the examples updated on the internet. 
---

Also, MUAs the encourage top-posting and allowing quoting without a '> ' or
other indicator of quoting depth are a pox on email.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 486 bytes
Desc: not available
URL: <http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20180718/3934d885/attachment.sig>

  reply	other threads:[~2018-07-18 23:10 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-14 16:04 Need Suggestions Athul Joy
2018-07-14 16:27 ` ozgur at goosey.org
2018-07-14 17:31   ` Cindy-Sue Causey
2018-07-14 18:07     ` ozgur at goosey.org
2018-07-15 13:39       ` valdis.kletnieks at vt.edu
2018-07-18  0:35 ` Richard Siegfried
2018-07-18  0:43   ` Richard Siegfried
2018-07-18  4:10   ` Dave Stevens
2018-07-18  4:41     ` valdis.kletnieks at vt.edu
2018-07-18  5:00       ` Dave Stevens
2018-07-18  4:39 ` inventsekar
2018-07-18 21:19   ` Daniel.
2018-07-18 21:29     ` Dave Stevens
2018-07-18 23:10       ` valdis.kletnieks at vt.edu [this message]
2018-07-19  1:16         ` Daniel.
2018-07-19  2:37           ` valdis.kletnieks at vt.edu
2018-07-19  2:42             ` Daniel.
2018-07-25 21:37   ` Himanshu Jha
2018-07-25 22:10     ` valdis.kletnieks at vt.edu
2018-08-01 21:29       ` Ruben Safir
2018-08-02  4:36         ` Himanshu Jha

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=63045.1531955420@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).