From: rpjday@crashcourse.ca (Robert P. J. Day)
To: kernelnewbies@lists.kernelnewbies.org
Subject: USB Start Learning Codebase
Date: Fri, 17 Oct 2014 02:58:40 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.2.11.1410170256210.19425@localhost> (raw)
In-Reply-To: <541B8619.5010909@gmail.com>
On Thu, 18 Sep 2014, nick wrote:
> Hey Guys,
> I am asking here about how to start with the usb stack as I am
> interested in learning that alongside the btrfs codebase.
> Nick
personally, i suggest immediately submitting malformed, unnecessary
and gramatically broken patches to the USB mailing list, so that the
maintainers can politely and patiently explain to you where you went
wrong -- i've always thought that was a *great* way to learn the
complexities of a kernel subsystem.
that was just cruel, wasn't it?
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
prev parent reply other threads:[~2014-10-17 9:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-19 1:26 USB Start Learning Codebase nick
2014-10-17 9:58 ` Robert P. J. Day [this message]
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.1410170256210.19425@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.