From: r.marek@sh.cvut.cz (Rudolf Marek)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] How to submit patches
Date: Sun, 02 Jul 2006 21:48:20 +0000 [thread overview]
Message-ID: <44A83F24.6040402@sh.cvut.cz> (raw)
In-Reply-To: <fcf695481614.44a7a0d9@urv.cat>
Hello Carlos,
> I have been working in patches for kernel drivers and libsensors, adding
> / mapping omitted registers about
> pwms and pwm divisors of the winbond family.
Well patches always welcomed. Please post the patches to the list.
Just use diff -uprN a/ b/
where a/ and b/ are two trees of sources. (The diff should be done using
the latest kernel -mm)
Indicate that the mail contains a patch with [PATCH] subject line. You may
include the patch into text attachment. The message body will just contain
a description of the patch and Signed-Off-By line if it is for kernel patch.
You may also read
http://www.kernel.org/git/?p=linux/kernel/git/stable/linux-2.6.17.y.git;a=blob;hÂc85bcb3d438b983ccc1535acbbd185867e26c3;hbRcbb7b78994ea3799f1bbb8c03bce1e2f72a271;f=Documentation/SubmittingPatches
and
http://www.kernel.org/git/?p=linux/kernel/git/stable/linux-2.6.17.y.git;a=blob;hÎ5d2c038cf54603d76c32b25e563456ebcf6711;hbRcbb7b78994ea3799f1bbb8c03bce1e2f72a271;f=Documentation/CodingStyle
The SubmittingPatches document is explaining the procedure of submitting patches
to kernel. If you follow the rules and just use the lm-sensors mailing list all
will be fine. (I described the rules briefly above)
I hope it is more clear now. If you have more questions ask please.
Regards
Rudolf
next prev parent reply other threads:[~2006-07-02 21:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-02 10:32 [lm-sensors] How to submit patches carlos.olalla at urv.cat
2006-07-02 21:48 ` Rudolf Marek [this message]
2006-07-03 10:57 ` carlos.olalla at urv.cat
2006-07-03 11:05 ` carlos.olalla at urv.cat
2006-07-03 11:09 ` Rudolf Marek
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=44A83F24.6040402@sh.cvut.cz \
--to=r.marek@sh.cvut.cz \
--cc=lm-sensors@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.