From: spradlim <spradlim@bashful.msoe.edu>
To: kernel-janitors@vger.kernel.org
Subject: First Patch, please verify it
Date: Tue, 17 Nov 2009 06:03:22 +0000 [thread overview]
Message-ID: <20091117060322.GA1816@bashful.msoe.edu> (raw)
I tried to follow the documentation for submitting patches.
Is the following patch correctly submitted.
I just cleaned up dead code warnings....
Let me know how it is and I can continue to commit more patches.
I have written drivers just not for the Linux kernel. This is
a good way to look over source code and become familiar with the
kernel.
--
Mike Spradling
reply other threads:[~2009-11-17 6:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20091117060322.GA1816@bashful.msoe.edu \
--to=spradlim@bashful.msoe.edu \
--cc=kernel-janitors@vger.kernel.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.