LKML Archive on
help / color / mirror / Atom feed
* Re: [PATCH 0/5] 2.4.27-pre3 pcnet32.c
       [not found] <>
@ 2004-05-21 21:10 ` Jeff Garzik
  0 siblings, 0 replies; only message in thread
From: Jeff Garzik @ 2004-05-21 21:10 UTC (permalink / raw)
  To: Don Fry; +Cc: tsbogend, netdev, Linux Kernel

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.


P.S.  Somebody should put this into Documentation/SubmittingPatches...

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2004-05-21 21:10 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <>
2004-05-21 21:10 ` [PATCH 0/5] 2.4.27-pre3 pcnet32.c Jeff Garzik

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).