* [lm-sensors] How to submit patches
@ 2006-07-02 10:32 carlos.olalla at urv.cat
2006-07-02 21:48 ` Rudolf Marek
` (3 more replies)
0 siblings, 4 replies; 5+ messages in thread
From: carlos.olalla at urv.cat @ 2006-07-02 10:32 UTC (permalink / raw)
To: lm-sensors
Hello everybodyI have been working in patches for kernel drivers and libsensors, adding / mapping omitted registers aboutpwms and pwm divisors of the winbond family.Are these patches welcome? How can I submit them?RegardsCarlos
Carlos Olalla Martinez
carlos.olalla at urv.net
carlos.olalla at estudiants.urv.cat
http://www.tinet.org/~com.ea
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20060702/07750c4f/attachment.html
^ permalink raw reply [flat|nested] 5+ messages in thread
* [lm-sensors] How to submit patches
2006-07-02 10:32 [lm-sensors] How to submit patches carlos.olalla at urv.cat
@ 2006-07-02 21:48 ` Rudolf Marek
2006-07-03 10:57 ` carlos.olalla at urv.cat
` (2 subsequent siblings)
3 siblings, 0 replies; 5+ messages in thread
From: Rudolf Marek @ 2006-07-02 21:48 UTC (permalink / raw)
To: lm-sensors
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
^ permalink raw reply [flat|nested] 5+ messages in thread
* [lm-sensors] How to submit patches
2006-07-02 10:32 [lm-sensors] How to submit patches carlos.olalla at urv.cat
2006-07-02 21:48 ` Rudolf Marek
@ 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
3 siblings, 0 replies; 5+ messages in thread
From: carlos.olalla at urv.cat @ 2006-07-03 10:57 UTC (permalink / raw)
To: lm-sensors
Thx for your answer Rudolf> 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)I have seen that the kernel drivers from latest SVN snapshot of lm-sensors athttp://dl.lm-sensors.org/lm-sensors/snapshots/are different from the ones athttp://www.kernel.org/should i use the latest lm-sensors SVN snapshot for libsensors patches?and the latest kernel for drivers patches?I guess this is obvious but i want to be sureThx again!
Carlos Olalla Martinez
carlos.olalla at urv.net
carlos.olalla at estudiants.urv.cat
http://www.tinet.org/~com.ea
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20060703/6a54cf89/attachment.html
^ permalink raw reply [flat|nested] 5+ messages in thread
* [lm-sensors] How to submit patches
2006-07-02 10:32 [lm-sensors] How to submit patches carlos.olalla at urv.cat
2006-07-02 21:48 ` Rudolf Marek
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
3 siblings, 0 replies; 5+ messages in thread
From: carlos.olalla at urv.cat @ 2006-07-03 11:05 UTC (permalink / raw)
To: lm-sensors
Sorry, text formatted my msg now ->
Thx for your answer Rudolf
> 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)
I have seen that the kernel drivers from latest SVN snapshot of lm-sensors at
http://dl.lm-sensors.org/lm-sensors/snapshots/
are different from the ones at
http://www.kernel.org/
should i use the latest lm-sensors SVN snapshot for libsensors patches?
and the latest kernel for drivers patches?
I guess this is obvious but i want to be sure
Thx again!
Carlos Olalla Martinez
carlos.olalla at urv.net
carlos.olalla at estudiants.urv.cat
http://www.tinet.org/~com.ea
^ permalink raw reply [flat|nested] 5+ messages in thread
* [lm-sensors] How to submit patches
2006-07-02 10:32 [lm-sensors] How to submit patches carlos.olalla at urv.cat
` (2 preceding siblings ...)
2006-07-03 11:05 ` carlos.olalla at urv.cat
@ 2006-07-03 11:09 ` Rudolf Marek
3 siblings, 0 replies; 5+ messages in thread
From: Rudolf Marek @ 2006-07-03 11:09 UTC (permalink / raw)
To: lm-sensors
Hello Carlos
It depends if your drivers are for kernel 2.4 or 2.6.
The snapshot has only driver for kernel 2.4.
The kernel 2.6 has no own repository.
Regards
Rudolf
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2006-07-03 11:09 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-07-02 10:32 [lm-sensors] How to submit patches carlos.olalla at urv.cat
2006-07-02 21:48 ` Rudolf Marek
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
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.