From: Jeff Garzik <jgarzik@pobox.com>
To: Don Fry <brazilnut@us.ibm.com>
Cc: tsbogend@alpha.franken.de, netdev@oss.sgi.com,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/5] 2.4.27-pre3 pcnet32.c
Date: Fri, 21 May 2004 17:10:33 -0400 [thread overview]
Message-ID: <40AE7049.80900@pobox.com> (raw)
In-Reply-To: <200405212055.i4LKtx110244@DYN318364BLD.beaverton.ibm.com>
Don Fry wrote:
> Please apply the following patches to 2.4.27-pre3. The first four are simple
> "one line" fixes. The last removes the timer I added a little while ago,
> as it added complexity without improving performance.
>
> [PATCH 1/5] 2.4.27-pre3 pcnet32 add static to two routines.
> [PATCH 2/5] 2.4.27-pre3 pcnet32 avoid hard hang with some chip variants.
> [PATCH 3/5] 2.4.27-pre3 pcnet32 correct 79C976 variant string.
> [PATCH 4/5] 2.4.27-pre3 pcnet32 fix boundary comparison bug.
> [PATCH 5/5] 2.4.27-pre3 pcnet32 remove timer and complexity.
It would help me a lot if you changed your email subject line in two
minor ways:
1) Include the kernel version _inside_ the brackets,
[PATCH 1/5 2.4.27-pre3]
2) Just to make it look a tad nicer and more consistent with other
changelog entries, add a colon after the driver name:
[PATCH 1/5 2.6.6] pcnet32: mark two routines static
This allows me to pass your submission fully automated through scripts.
The resultant one-line description of your patch becomes
[PATCH] pcnet32: mark two routines static
when my scripts merge your patch into the BK repository.
BTW, you don't need to resend your 2.4 and 2.6 pcnet32 patches, this is
just for future reference.
Jeff
P.S. Somebody should put this into Documentation/SubmittingPatches...
next prev parent reply other threads:[~2004-05-21 21:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-21 20:55 [PATCH 0/5] 2.4.27-pre3 pcnet32.c Don Fry
2004-05-21 21:10 ` Jeff Garzik [this message]
2004-05-26 22:15 ` Don Fry
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=40AE7049.80900@pobox.com \
--to=jgarzik@pobox.com \
--cc=brazilnut@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=tsbogend@alpha.franken.de \
/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).