From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
Muni Sekhar <munisekharrms@gmail.com>,
Oliver Neukum <oneukum@suse.com>,
kernelnewbies <kernelnewbies@kernelnewbies.org>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: LDD 3rd ed. - It was: Re: read() via USB bus
Date: Thu, 12 Aug 2021 06:13:54 -0400 [thread overview]
Message-ID: <147449.1628763234@turing-police> (raw)
In-Reply-To: <13470108.apdoE9Qb8s@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 794 bytes --]
On Thu, 12 Aug 2021 11:45:45 +0200, "Fabio M. De Francesco" said:
> I've heard that your book, LDD 3rd edition, has become obsolete a long time
> ago and most sample code cannot anymore build. Reading what you wrote above
> seems to contradict what I've been told by others... I must admit that I've
> just had a print copy of it that I have not yet opened for reading, therefore
> maybe that I'm totally wrong in assuming the above.
The APIs have all changed a lot since the 3rd edition.
The concepts haven't changed that much. And given that the in-kernel APIs
have *always* been a moving target, being able to deal with the fact that
a given function now takes a 'struct foo*' rather than a 'struct bar *' is a very
necessary skill for anybody who's planning to do serious kernel work.
[-- Attachment #2: Type: application/pgp-signature, Size: 494 bytes --]
next prev parent reply other threads:[~2021-08-12 10:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-09 7:58 read() via USB bus Muni Sekhar
2021-08-09 8:15 ` Oliver Neukum
2021-08-09 8:44 ` Greg KH
2021-08-12 9:45 ` LDD 3rd ed. - It was: " Fabio M. De Francesco
2021-08-12 10:13 ` Valdis Klētnieks [this message]
2021-08-12 10:18 ` Greg KH
2021-08-12 10:26 ` Robert P. J. Day
2021-08-09 16:19 ` Muni Sekhar
2021-08-10 14:13 ` Muni Sekhar
2021-08-10 14:20 ` Oliver Neukum
[not found] ` <CAHhAz+ioThu3v4VW6LVqFn9MhgNaqv=qDoxh8Orkw2LOEC_JYA@mail.gmail.com>
2021-08-11 10:04 ` Oliver Neukum
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=147449.1628763234@turing-police \
--to=valdis.kletnieks@vt.edu \
--cc=fmdefrancesco@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=kernelnewbies@kernelnewbies.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=munisekharrms@gmail.com \
--cc=oneukum@suse.com \
/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).