[TRIVIAL] dasd_3990_erp.c typo patch

[TRIVIAL] dasd_3990_erp.c typo patch

Post by Maciej Soltysia » Sun, 16 Feb 2003 22:20:11


with / wiht typo patch

Like That

*** drivers/s390/block/dasd_3990_erp.c~ Mon Feb 25 20:38:03 2002
--- drivers/s390/block/dasd_3990_erp.c  Sat Feb 15 21:10:56 2003
*** 2809,2815 ****
   *     - exit with permanent error
!  *   erp                ERP which is in progress wiht no retry left
   *   erp                modified/additional ERP
--- 2809,2815 ----
   *     - exit with permanent error
!  *   erp                ERP which is in progress with no retry left
   *   erp                modified/additional ERP

GIT/MU d-- s:- a-- C++ UL++++$ P L++++ E- W- N- K- w--- O! M- V- PS+ PE++
Y+ PGP- t+ 5-- X+ R tv- b DI+ D---- G e++>+++ h! y?

< 1K Download

1. Trivial Patch Policy (trivial@rustcorp.com.au)

Hi all,

        I've been collecting trivial patches for a few months now, and
it's time to solidify some rules:

1) Trivial patches must qualify for one of the following to be
        a) Spelling fixes (useful for grep, and sets a good example)
        b) Warning fixes (cluttering with useless warnings is bad)
        c) Compilation fixes (only if they are actually correct)
        d) Runtime fixes (only if they actually fix things)
        e) Removing use of deprecated functions/macros (eg. check_region).
        f) Contact detail and documentation fixes
        g) Non-portable code replaced by portable code
           (even in arch-specific, since people copy, as long as it's trivial)
        h) Any fix by the author/maintainer of the file.
           (ie. patch monkey in re-transmission mode)

   They must also be "trivial" by my definition of trivial.  Best
   patches contain enough context for me to judge without opening the
   file (diff -C<nn> -u is your friend).

   NOTE: This means I'll only take whitespace/indentation fixes from
   the author or maintainer.

2) The patch will not be forwarded to anyone until a new kernel has
   been released after I receive the patch, *unless* noone else is
   sent the patch.  So if you cc: the trivial patch monkey, it'll only
   be forwarded from there if it doesn't make the next kernel.

3) The first time the patch is forwarded, it will be sent to the
   author and/or maintainer.  If they say they've included it in their
   tree, no more forwards will occur (modulo some timeout eventually).
   If they NAK it, the patch will be closed.  Otherwise, the patch
   will be sent directly to Linus or Marcelo on future forwards (the
   maintainer will still be cc'd).

Hopefully this will be a good compromise between coordinating with
maintainers who want control of their files, and stopping trivial
patches from slipping through the cracks.

Rusty, aka the Trivial Patch Monkey.
  Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

2. Solaris 9 & Evolution

3. Trivial 2.5.17: DMA-mapping.txt typo fix

4. remote mounting of msdos hd over ethernet link

5. Trivial typo in comment, please apply

6. Advice on new system

7. Trivial typo fix in Documentation

8. Auditing UNIX

9. trivial typo in drivers/serial/Kconfig

10. [TRIVIAL] ide.c - just a typo?

11. [PATCH] 2.5 trivial reiserfs resizer patch (needed now that

12. [PATCH][RESEND] 2 spelling typos

13. PATCH: sk98 typo fix