All of lore.kernel.org
 help / color / mirror / Atom feed
From: tomas szepe <kala@pinerecords.com>
To: Sandy Harris <pashley@storm.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: The tainted message
Date: Mon, 29 Apr 2002 22:00:35 +0200	[thread overview]
Message-ID: <20020429200035.GA26567@louise.pinerecords.com> (raw)
In-Reply-To: <E171TzX-0008PF-00@the-village.bc.nu> <1019926629.2045.698.camel@phantasy> <1020099580.5131.14.camel@w-beattie1> <20020429171516.GA25377@louise.pinerecords.com> <20020429184331.3230f5ab.spyro@armlinux.org> <20020429174232.GA25502@louise.pinerecords.com> <ui6rcugr35a6h8u1tf6sq5js4mn5c19sq2@4ax.com> <20020429192107.GA26369@louise.pinerecords.com> <3CCD93E6.F637706A@storm.ca>

> > > >> thie warning should be:
> > > >>
> > > >> Warning: Module %s is not open source, and as such, loading it will make
> > > >> your kernel un-debuggable. Please do not submit bug reports from a kernel
> > > >> with this module loaded, as they will be useless, and likely ignored.
> > > >
> > > >Very good! I'd only change the tense to "The non-opensource module %s is
> > > >about to be loaded, which will make your kernel impossible to debug," so
> > > >that it's crystal clear that the message is not a failure notification.
> > >
> > > Pschologically it would be better to phrase it as a postive statement.
> > >
> > > Warning: Module %s is not open source, and as such, loading it will
> > > make your kernel un-debuggable. Before reporting problems to
> > > Linux-kernel, please replicate the problem without the module loaded.
> > 
> > You're right. And, hmmm, tell you what.. I also like your version because
> > it makes no statements whatsoever about vendor support, or support from
> > anyone else than the people on linux-kernel.
> > 
> > Now, would anyone attempt to sum up all the points made here and come up
> > w/ something like a "final-draft" proposal?
> 
> Warning: Source code for module %s is not publicly available. Problems
> with a kernel that has loaded this module can be debugged only by someone
> with access to the module source. Before reporting a problem to the Linux
> kernel mailing list, please replicate the problem without the module loaded.


Indeed, this would certainly do much better than the current caption.
"What say you, Mr. ModutilsMaintainer?" <wink wink>


T.

  reply	other threads:[~2002-04-29 20:00 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-27  4:51 The tainted message Richard Thrapp
2002-04-27  7:50 ` arjan
2002-04-27  8:06 ` Enrico Demarin
2002-04-27 18:45   ` Alan Cox
2002-04-27 12:08 ` Francois Romieu
2002-04-27 15:51   ` Richard Thrapp
2002-04-27 17:02     ` was: " Francois Romieu
2002-04-28  0:33     ` Keith Owens
2002-04-27 15:20 ` Alan Cox
2002-04-27 14:27   ` Martin Dalecki
2002-04-27 18:41     ` Alan Cox
2002-04-27 16:03   ` Richard Thrapp
2002-04-27 16:28   ` Bob_Tracy
2002-04-27 16:57   ` Robert Love
2002-04-29 16:59     ` Brian Beattie
2002-04-29 17:15       ` tomas szepe
2002-04-29 17:43         ` Ian Molton
2002-04-29 17:41           ` Thomas 'Dent' Mirlacher
2002-04-29 18:16             ` Ian Molton
2002-04-29 18:14               ` tomas szepe
2002-04-29 17:42           ` tomas szepe
2002-04-29 19:11             ` John Alvord
2002-04-29 19:21               ` tomas szepe
2002-04-29 18:41                 ` Sandy Harris
2002-04-29 20:00                   ` tomas szepe [this message]
2002-04-29 23:06                 ` Keith Owens
2002-04-29 23:53                   ` tomas szepe
2002-04-30 13:37                   ` john slee
2002-04-30 13:44                     ` Keith Owens
2002-04-29 18:14           ` Christian Bornträger
2002-04-29 17:34             ` Sandy Harris
2002-04-27 19:22   ` Chris Abbey
2002-04-27 19:50     ` Alan Cox
2002-04-28  0:27   ` Keith Owens
2002-04-28  1:27     ` Richard Thrapp
2002-04-28  1:41       ` Keith Owens
2002-04-28  2:14         ` Richard Thrapp
2002-04-28  2:00       ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2002-04-30  8:36 Martin Knoblauch
2002-05-02  7:35 Martin Knoblauch
2002-05-02 11:55 ` Keith Owens
2002-05-02 13:08   ` Martin Knoblauch

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=20020429200035.GA26567@louise.pinerecords.com \
    --to=kala@pinerecords.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pashley@storm.ca \
    /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.