From: fser@code-libre.org (François)
To: kernelnewbies@lists.kernelnewbies.org
Subject: one more new Bie
Date: Tue, 9 Aug 2016 11:16:21 +0200 [thread overview]
Message-ID: <20160809091619.oq7tvf4zdycvlfzw@sith> (raw)
In-Reply-To: <CAK25hWPOM03-+vXuZ+krCkXtmuEcYG7VChXRyP0wvevY=k++yw@mail.gmail.com>
On Mon, Aug 08, 2016 at 10:40:08PM +0530, Saket Sinha wrote:
> Hi,
>
> The ideal way to start is to write some basic kernel drivers. Look for the
> tutorial at the following links -
>
>
> 1. Linux Device Drivers 3 examples updated to work in recent kernels
> http://examples.oreilly.com/9780596005900/
Not that recent obviously :(
For instance, in sbull, they use blk_fs_request which does not exist
anymore.
--
Fran?ois
next prev parent reply other threads:[~2016-08-09 9:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-08 9:11 one more new Bie Madhu K
2016-08-08 17:10 ` Saket Sinha
2016-08-09 9:16 ` François [this message]
2016-08-08 21:53 ` Dennis Semakin
-- strict thread matches above, loose matches on Subject: below --
2016-08-06 16:13 Anurag Ranjan
2016-08-06 16:24 ` Saket Sinha
2016-08-06 16:48 ` François
2016-08-06 17:02 ` Giedrius Statkevičius
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=20160809091619.oq7tvf4zdycvlfzw@sith \
--to=fser@code-libre.org \
--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).