All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Frans Pop <elendil@planet.nl>
Cc: linux-kernel@vger.kernel.org,
	Arjan van de Ven <arjan@infradead.org>,
	tglx@tglx.de, mingo@elte.hu
Subject: Re: Warning/Oops report of the week of September 16th, 2008
Date: Wed, 24 Sep 2008 16:18:31 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LFD.1.10.0809241616080.3265@nehalem.linux-foundation.org> (raw)
In-Reply-To: <200809250112.40661.elendil@planet.nl>



On Thu, 25 Sep 2008, Frans Pop wrote:
> 
> If no other solution is found soon, would a patch to just skip the sysctl 
> table check for this particular case be acceptable?

Well, it would be even _more_ acceptable to have a new Kconfig option that 
just disables the insane parport registrations.

Them you could turn off the /proc files, and if it turns out you don't 
have anything that uses it, you can avoid the warning by actually having a 
smaller kernel with less crap, rather than adding more crap to hide the 
crap. Wouldn't that be nicer?

It would have to be a Kconfig option since we don't _know_ that it's not 
used by anything..

		Linus

  reply	other threads:[~2008-09-24 23:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-16 16:22 Warning/Oops report of the week of September 16th, 2008 Arjan van de Ven
2008-09-17  0:40 ` Jay Cliburn
2008-09-24 22:36 ` Frans Pop
2008-09-24 22:45   ` Linus Torvalds
2008-09-24 22:57     ` Arjan van de Ven
2008-09-24 23:00     ` Linus Torvalds
2008-09-24 23:12     ` Frans Pop
2008-09-24 23:18       ` Linus Torvalds [this message]
2008-09-26 10:28     ` Alan Cox
2008-09-27 15:21       ` Frans Pop

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=alpine.LFD.1.10.0809241616080.3265@nehalem.linux-foundation.org \
    --to=torvalds@linux-foundation.org \
    --cc=arjan@infradead.org \
    --cc=elendil@planet.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@tglx.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 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.