From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: =?unknown-8bit?Q?J=F6rn?= Engel <joern@wohnheim.fh-wedel.de>
Cc: Pavel Machek <pavel@ucw.cz>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Deepak Saxena <deepak@plexity.net>
Subject: Re: 2.5.64: i2c-proc kills machine at boot
Date: 12 Mar 2003 16:03:19 +0000 [thread overview]
Message-ID: <1047484999.22696.7.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <20030312125631.GA27966@wohnheim.fh-wedel.de>
On Wed, 2003-03-12 at 12:56, =?unknown-8bit?Q?J=F6rn?= Engel wrote:
> On Tue, 11 March 2003 11:47:22 +0100, Pavel Machek wrote:
> >
> > If I turn #ifdef DEBUG in i2c_register_entry() into #if 1, it prints
> >
> > i2c-proc.o: NULL pointer when trying to install fill_inode fix!\n
> >
> > but boots.
>
> That file need a lot of work anyway. On the shitlist of top stack
> users, it holds ranks 3 and 9-11. Impressive.
His problem is i2c not i2o. Also the i2o proc stuff while ugly isnt a
deep call nest or in irq context so not a big problem. It does want
fixing but thats a seperate matter
> It also isn't listed in the current MAINTAINERS file. Is i2o currently
> unmaintained?
Its kind of mine. Maintained is an overly strong word for it however, but I
do take patches 8)
next prev parent reply other threads:[~2003-03-12 14:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-11 10:47 Pavel Machek
2003-03-12 12:56 ` =?unknown-8bit?Q?J=F6rn?= Engel
2003-03-12 13:31 ` Vojtech Pavlik
2003-03-12 13:38 ` =?unknown-8bit?Q?J=F6rn?= Engel
2003-03-12 16:03 ` Alan Cox [this message]
2003-03-12 16:14 ` =?unknown-8bit?Q?J=F6rn?= Engel
[not found] ` <20030312110650.7c4b8571.akpm@digeo.com>
2003-03-12 19:22 ` Joern Engel
2003-03-12 21:55 ` Alan Cox
2003-03-12 15:00 ` Christoph Hellwig
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=1047484999.22696.7.camel@irongate.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=deepak@plexity.net \
--cc=joern@wohnheim.fh-wedel.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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®