netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Don Fry <brazilnut@us.ibm.com>
Cc: Netdev <netdev@oss.sgi.com>
Subject: Re: patch submission question
Date: Fri, 21 May 2004 16:45:37 -0400	[thread overview]
Message-ID: <40AE6A71.1070305@pobox.com> (raw)
In-Reply-To: <200405201543.i4KFhHk08317@DYN318364BLD.beaverton.ibm.com>

Don Fry wrote:
> Jeff,
> 
> I have four one-line patches for the pcnet32 driver.  Should I send them
> as one patch, or four one-line patches?
> 
> 1) Change PCnet/FAST III 79C976 to PCnet/PRO 79C976.
> 2) In pcnet32_interrupt change (delta >= TX_RING_SIZE) to  (... > ...)
> 3) add 'static' to pcnet32_get_regs and pcnet32_get_regs_len.
>     (prototype has static, routine does not have static).
> 4) reading bcr34 hangs the system with some variants of the chip in
> pcnet2_get_regs.


Sorry I didn't get back to you before you actually sent the patches. 
Life is what it is...  Also, I hope you don't mind me adding a CC to 
netdev@oss.sgi.com.  Even for questions like the above, I _really_ 
encourage you to CC the mailing list, that way all knowledge (including 
my preferences) are shared and archived.  This is another part of open 
development.

The main point is to separate things out into logical changes.  For 
practical purposes, this usually means I will often lump several minor 
changes into a single patch.  It is up to you, the maintainer, to decide 
where to draw the line.

In your above example, I would send #2 and #4 as separate patches, and 
combine #1 and #3 into a single "trivial changes" patch.

	Jeff

           reply	other threads:[~2004-05-21 20:45 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <200405201543.i4KFhHk08317@DYN318364BLD.beaverton.ibm.com>]

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=40AE6A71.1070305@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=brazilnut@us.ibm.com \
    --cc=netdev@oss.sgi.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).