From: rpjday@crashcourse.ca (Robert P. J. Day)
To: kernelnewbies@lists.kernelnewbies.org
Subject: About guiding hello world module submission
Date: Wed, 24 Jun 2015 04:38:07 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.11.1506240435190.1030@localhost> (raw)
In-Reply-To: <CAGYCq6gNX0x_TGyHgypAMGM0fWRhaVsgimD=QuYrJFvh6r-Qkw@mail.gmail.com>
On Wed, 24 Jun 2015, Mayur Patil wrote:
> Hi All,
>
> ?? I am conducting one workshop at FUDCon in which I am trying to
> teach how to write and send your first linux kernel device driver.
> Could please suggest me the place where I can guide the students to
> send the device driver?
once upon a time, i wrote an (admittedly-dated) online course on how
to get started with kernel programming (and, yes, it needs updating
:-P):
http://crashcourse.ca/introduction-linux-kernel-programming/introduction-linux-kernel-programming
ignore the $39 reference, the course has been publicly available for
free for a while.
on the second point -- how to *send* that driver to the kernel --
don't you kind of need a rationale for why you're working on a driver
that isn't in the kernel already? i suspect that if you're already
competent enough to be writing a driver for something that isn't in
the kernel, you probably already know the protocol for submitting it,
no?
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
next prev parent reply other threads:[~2015-06-24 8:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-24 4:49 About guiding hello world module submission Mayur Patil
2015-06-24 7:36 ` Daniel Baluta
2015-06-24 17:28 ` Mayur Patil
2015-06-24 23:06 ` Lukas Elsner
2015-06-25 4:44 ` Mayur Patil
2015-06-25 6:17 ` Lukas Elsner
2015-06-24 8:38 ` Robert P. J. Day [this message]
2015-06-24 17:27 ` Mayur Patil
2015-06-24 10:03 ` anish singh
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=alpine.LFD.2.11.1506240435190.1030@localhost \
--to=rpjday@crashcourse.ca \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.