All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Chris Wright <chrisw@osdl.org>
Cc: Krzysztof Halasa <khc@pm.waw.pl>, Greg KH <greg@kroah.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.11.2
Date: Fri, 11 Mar 2005 14:28:10 -0500	[thread overview]
Message-ID: <4231F14A.2090602@tmr.com> (raw)
In-Reply-To: <20050311173808.GZ28536@shell0.pdx.osdl.net>

Chris Wright wrote:
> * Krzysztof Halasa (khc@pm.waw.pl) wrote:
> 
>>Another patch for 2.6.11.x: already in main tree, fixes kernel panic
>>on receive with WAN cards based on Hitachi SCA/SCA-II: N2, C101,
>>PCI200SYN.
>>Also a documentation change fixing user-panic can-t-find-required-software
>>failure (just the same patch as in mainline) :-)
> 
> 
> We are not accepting documentation fixes.  Could you please send just
> the panic fix to stable@kernel.org (cc lkml)?  And add Signed-off-by...

I really think you should not have a hard and fast rule on doc, for the 
case where a fix also makes the mainline doc wrong and someone might do 
something destructive reading the mainline docs and using the fixed 
code. Drivers come to mind.

I am NOT saying this is such a case, I'm just against zero tolerance 
rules when I can see a reasonable case where they don't do what you want.

-- 
    -bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
  last possible moment - but no longer"  -me

  reply	other threads:[~2005-03-11 19:29 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-09  8:39 Linux 2.6.11.2 Greg KH
2005-03-09  8:39 ` Greg KH
2005-03-17 15:18   ` Gene Heskett
2005-03-09  9:52 ` Marcos D. Marado Torres
2005-03-09 10:04   ` Geert Uytterhoeven
2005-03-09 10:17     ` Marcos D. Marado Torres
2005-03-09 10:41       ` Geert Uytterhoeven
2005-03-09 11:23         ` Jesper Juhl
2005-03-09 21:26       ` Wakko Warner
2005-03-09 10:21     ` Dominik Karall
2005-03-09 10:28       ` Marcos D. Marado Torres
2005-03-09 10:51         ` Adrian Bunk
2005-03-09 15:35         ` Greg KH
2005-03-09 11:11   ` Pavel Machek
2005-03-09 23:57     ` Matt Mackall
2005-03-10  5:16       ` Willy Tarreau
2005-03-11 18:45       ` Bill Davidsen
2005-03-11 19:08         ` Matt Mackall
2005-03-11 19:19           ` Chris Wright
2005-03-11 22:01             ` Greg KH
2005-03-14 17:10               ` Bill Davidsen
2005-03-14 17:32                 ` Greg KH
2005-03-15 20:38           ` Bill Davidsen
2005-03-16  8:56             ` David Greaves
2005-03-09 12:38 ` Andy Whitcroft
2005-03-09 14:03 ` Marcelo Tosatti
2005-03-09 18:38   ` Greg KH
2005-03-09 20:32 ` Bill Davidsen
2005-03-09 21:06 ` Matt Mackall
2005-03-09 21:21   ` Randy.Dunlap
2005-03-09 23:11   ` Greg KH
2005-03-09 23:38     ` Matt Mackall
2005-03-10 12:54     ` Gene Heskett
2005-03-11 19:23       ` Bill Davidsen
2005-03-11 23:33         ` Gene Heskett
2005-03-11 14:53 ` Krzysztof Halasa
2005-03-11 17:38   ` Chris Wright
2005-03-11 19:28     ` Bill Davidsen [this message]
2005-03-11 21:07     ` Krzysztof Halasa
2005-03-11 21:11       ` Chris Wright
     [not found] <fa.dan38um.1m4gojq@ifi.uio.no>
     [not found] ` <fa.animhpl.r201hh@ifi.uio.no>
2005-03-10  1:46   ` Bodo Eggert
2005-03-10  3:08     ` Matt Mackall

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=4231F14A.2090602@tmr.com \
    --to=davidsen@tmr.com \
    --cc=chrisw@osdl.org \
    --cc=greg@kroah.com \
    --cc=khc@pm.waw.pl \
    --cc=linux-kernel@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.