From: liamryandev@gmail.com (Liam Ryan)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Updating LDD3
Date: Tue, 24 Oct 2017 14:03:59 +0100 [thread overview]
Message-ID: <20171024130358.GA14285@liam-mint> (raw)
In-Reply-To: <CAF3SDA4psKGR1zzx11v1jVPgDMkQVretJb5gCnBHZvEs-GT+FA@mail.gmail.com>
On Tue, Oct 24, 2017 at 10:49:34AM -0200, Daniel. wrote:
> You're welcome!
>
> On Oct 24, 2017 10:38 AM, "Ozgur" <okaratas@yandex.com> wrote:
>
> >
> > Hello,
> >
> > 24.10.2017, 15:31, "Daniel." <danielhilst@gmail.com>:
> >
> > Here it is https://github.com/martinezjavier/ldd3
Thanks I had found this repo which is a great reference for when I get
stuck in my own attempt to update the old code, however I believe this repo is also outdated. For instance it calls aio_complete on line 405 of main.c of scullc which I found has since been removed ( or I made a huge error :) ).
Leaving that aside I'm referring to updating the book itself rather than the code as the text makes reference to the code as written in 2005.
I'll ask the question on the debian-legal list as recommended, I think
the threads diverged at some point.
Regards,
Liam
> >
> > Regards
> >
> >
> > oh, it's very good, nice.
> > Thank you
> >
> > Ozgur
> >
> >
> >
> > On Oct 24, 2017 9:58 AM, "Ozgur" <okaratas@yandex.com> wrote:
> >
> > Hello Daniel,
> >
> > 24.10.2017, 14:50, "Daniel." <danielhilst@gmail.com>:
> >
> > There is a repo at github with all the samples don't?
> >
> >
> >
> > I think that no, I not seen before on github.
> >
> > Regards
> >
> > Ozgur
> >
> >
> >
> > On Oct 24, 2017 9:06 AM, "Ozgur" <okaratas@yandex.com> wrote:
> >
> > Hello Ryan,
> >
> > 24.10.2017, 13:58, "Liam Ryan" <liamryandev@gmail.com>:
> > > I'm currently working through the Linux Device Drivers 3rd edition
> > > (https://lwn.net/Kernel/LDD3/) and much of the code is outdated.
> > >
> > > Right now I'm going through chapter 3 and rewriting the scull.c sample
> > > code so that it will compile with 4.14.x
> > >
> > > I'm wondering about the Creative Commons license on the LDD3 book. I
> > believe I would be able to annotate or alter the pdf files and re-publish
> > them once I respect the license, however I'm wondering if this would be
> > considered bad form? I assume there's a reason somebody else has not done
> > this to date?
> >
> > I think you can update and re-publish the example code and don't break the
> > original comment lines.
> > At least I think this.
> >
> > > Obviously as a kernel newbie I'm not best positioned to do this work but
> > > I'm happy to make a start and publish to a wiki or similar in a few
> > > months once I've gone through everything.
> > >
> > > Thanks,
> > > Liam
> >
> > Regards
> >
> > Ozgur
> >
> >
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2017-10-24 13:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-24 10:58 Updating LDD3 Liam Ryan
2017-10-24 11:02 ` Ozgur
2017-10-24 11:50 ` Daniel.
2017-10-24 11:58 ` Ozgur
2017-10-24 12:31 ` Daniel.
2017-10-24 12:38 ` Ozgur
2017-10-24 12:49 ` Daniel.
2017-10-24 13:03 ` Liam Ryan [this message]
2017-10-25 4:08 ` Tobin C. Harding
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=20171024130358.GA14285@liam-mint \
--to=liamryandev@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).