mirror of https://lore.kernel.org/lkml/
 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:00:27 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LFD.1.10.0809241559100.3265@nehalem.linux-foundation.org> (raw)
In-Reply-To: <alpine.LFD.1.10.0809241541320.3265@nehalem.linux-foundation.org>



On Wed, 24 Sep 2008, Linus Torvalds wrote:
> 
> Or rather, it's a warnign about the parport /proc interface. The fact is, 
> the parport code can generate multiple "instances" of things that 
> time-slice on the port, but they have all ended up always just registering 
> under the same name. IOW, it's a bug in the _user_ interface, not the 
> kernel.

Side note: the reason nobody cares is that the files exported there are 
likely never used anyway. But we don't _know_ that. Maybe somebody depends 
on the totally broken things that get registered in /proc. I doubt it, 
but..

		Linus

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

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-16 16:22 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 [this message]
2008-09-24 23:12     ` Frans Pop
2008-09-24 23:18       ` Linus Torvalds
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.0809241559100.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®