From: leon.woestenberg@gmail.com (Leon Woestenberg)
To: kernelnewbies@lists.kernelnewbies.org
Subject: knewbies project? - updating LDD3 source
Date: Tue, 24 May 2011 22:32:45 +0200 [thread overview]
Message-ID: <BANLkTik4D1m4ho9kY9zLMmgxxtAxCGbNxw@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1105241621070.12752@localhost6.localdomain6>
Hello all,
On Tue, May 24, 2011 at 10:26 PM, Robert P. J. Day
<rpjday@crashcourse.ca> wrote:
> On Tue, 24 May 2011, Javier Martinez Canillas wrote:
>
>> On Tue, May 24, 2011 at 8:14 PM, DG <dangets@gmail.com> wrote:
>> > On Tue, May 24, 2011 at 11:47 AM, Robert P. J. Day
>> > <rpjday@crashcourse.ca> wrote:
>> >> On Tue, 24 May 2011, Jim Cromie wrote:
>> >>
>> >>> over at http://code.google.com/p/ldd3/
>> >>> it says:
>> >>> The famous "Linux Device Drivers" released the sample code. but the
>> >>> code does not reflect the latest kernel updates, some of code cannot
>> >>> even compile. This project is to make it compatible with the current
>> >>> kernel.
>> >>>
Why not take this a little bit higher and rewrite the LDD3 book
sections that need updating, not (only) the source code examples.
This can be taken on piecewise.
I would see this identical to kernel/Documentation/* except that the
pieces are targetting device driver developers.
Regards,
--
Leon
next prev parent reply other threads:[~2011-05-24 20:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-24 17:35 knewbies project? - updating LDD3 source Jim Cromie
2011-05-24 17:47 ` Robert P. J. Day
2011-05-24 18:14 ` DG
2011-05-24 20:17 ` Javier Martinez Canillas
2011-05-24 20:26 ` Robert P. J. Day
2011-05-24 20:32 ` Leon Woestenberg [this message]
2011-05-24 20:36 ` Robert P. J. Day
2011-05-24 21:02 ` Javier Martinez Canillas
2011-05-24 20:37 ` Manohar Vanga
2011-05-25 3:42 ` naren.mehra at gmail.com
2011-05-25 6:27 ` Mohamed Thalib H
2011-05-25 7:29 ` sumeet linux
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=BANLkTik4D1m4ho9kY9zLMmgxxtAxCGbNxw@mail.gmail.com \
--to=leon.woestenberg@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).