kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: okaratas@yandex.com (Ozgur)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Updating LDD3
Date: Tue, 24 Oct 2017 14:02:17 +0300	[thread overview]
Message-ID: <315651508842937@web15j.yandex.ru> (raw)
In-Reply-To: <20171024105803.GA14014@liam-mint>

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

  reply	other threads:[~2017-10-24 11:02 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 [this message]
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
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=315651508842937@web15j.yandex.ru \
    --to=okaratas@yandex.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).