All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Kremer <david.kremer.dk@gmail.com>
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] questions about lm-sensors development
Date: Fri, 10 Feb 2012 09:26:45 +0000	[thread overview]
Message-ID: <4F34E2D5.6080900@gmail.com> (raw)

Hello,

cheers everyone. Thank you for your lm-sensor programs.

I asked recently in a thread if you support a LTS version for the kernel 
3.0, and I had a positive answer. Nevertheless, things are not quite 
clear for me, and it seems your website is lacking of informations on 
how to contribute.

Guenter uses a git repository, not sure how it interacts with the main 
kernel tree.

I would be glad to have a clear explanation of where are the 
repositories for the
different parts of lm-sensors and the development routines you all follow.

Especially I dont't understand very well why your patch are numbered 
0/4, 1/4, etc.

Thank you a lot in advance, I hope to be able to test and report things 
efficiently after you answered me.

Actually I would like to gain experience in linux kernel development, 
and I would like to watch closely your project in which I have personal 
interest but that I find also great because it is really useful for 
everyone. I expect to become a good kernel dev after following this 
project that I find interesting.

Thank you very much.

David Kremer

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

             reply	other threads:[~2012-02-10  9:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-10  9:26 David Kremer [this message]
2012-02-10 14:47 ` [lm-sensors] questions about lm-sensors development Guenter Roeck
2012-02-10 20:28 ` Nikolaus Schulz
2012-02-20 16:43 ` Guenter Roeck

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=4F34E2D5.6080900@gmail.com \
    --to=david.kremer.dk@gmail.com \
    --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.