All of lore.kernel.org
 help / color / mirror / Atom feed
From: tandrews@grok.co.za (Thomas Andrews)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] procedure for submitting patches
Date: Mon, 29 May 2006 17:47:11 +0000	[thread overview]
Message-ID: <20060529174711.GD21868@grok.co.za> (raw)
In-Reply-To: <20060510173848.GC30963@grok.co.za>

On Mon, May 29, 2006 at 07:36:08PM +0200, Jean Delvare wrote:

> > I'm not about to submit a patch, but sometime in the future I will be
> > doing so, so I want to understand fully how it works around here.
> > Firstly some notes though:
> > 
> > In the module that I'm working on:
> > 
> >     (a) I have found (and fixed) a bug in the original code.
> >     (b) I have made enhancements that are not all related to one
> >         another.
> > 
> > Should I submit seperate patches for all the different bits that I've
> > done, or should I (at least initially) submit one huge patch for the
> > lot?
> 
> Alawys submit seperate patches. There are no exceptions to this rule.
> 
> > Is there one specific person that I should send the patch(es) to, or is
> > the list the place where it all happens?
> 
> Yes, this list is the right place (assuming your work is related to
> hardware monitoring or i2c). For bug fixes, or if you think your patch
> is ready to be pushed upstream, it's a good idea to Cc me.
> 
> > I'm pretty new to all this, so I can imagine that my code will have to
> > be massaged a bit to fit in properly..
> 
> Probably, but we try to be nice with newcomers, so don't worry :)

Thanks Jean. I've pretty much finished with my changes to scx200_acb.c
but I won't submit any patches until I've done some fairly heavy
testing because making the driver operate as a slave using interrupts
is quite a big change (in my opinion), and I don't want to submit
something that's buggy.

Regards,
Thomas


      parent reply	other threads:[~2006-05-29 17:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-10 17:38 [lm-sensors] procedure for submitting patches Thomas Andrews
2006-05-29 17:36 ` Jean Delvare
2006-05-29 17:47 ` Thomas Andrews [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=20060529174711.GD21868@grok.co.za \
    --to=tandrews@grok.co.za \
    --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.