DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=iUByHvLuXwi+/5hDC0qqkQe/4WJGyVna0M5pi5yD5ljef1yubixeLuOF8ok72hHwvmLxhowjy5SyyZ4wXhluY2oZVQDHNu3n0Nwel3BBLJ2cjRJ/nzLjXZi6lo+whINFGRINvyP6eSjRP3lBBE51mwYTJDtC3NtwjaHkVqpFPJ4=
Message-ID: <d120d5000512131248j79a93d5ex8667ca6a38452a1d@mail.gmail.com>
Date: Tue, 13 Dec 2005 15:48:47 -0500
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Reply-To: dtor_core@ameritech.net
To: Stelian Pop <stelian@popies.net>
Subject: Re: sonypi searching new maintainer (Was: Re: [RFT] Sonypi: convert to the new platform device interface)
Cc: Mattia Dongili <malattia@linux.it>, LKML <linux-kernel@vger.kernel.org>
In-Reply-To: <1134505855.9642.28.camel@deep-space-9.dsnet>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8BIT
Content-Disposition: inline
References: <200512130219.41034.dtor_core@ameritech.net>
	 <20051213183248.GA3606@inferi.kami.home>
	 <d120d5000512131104x260fdbf2mcc58fb953559fec5@mail.gmail.com>
	 <1134505855.9642.28.camel@deep-space-9.dsnet>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1284
Lines: 30

On 12/13/05, Stelian Pop <stelian@popies.net> wrote:
> Le mardi 13 d?cembre 2005 ? 14:04 -0500, Dmitry Torokhov a >
> > > sonypi: unknown event port1=0x0f,port2=0x05
> [...]
> > > Oh, there seems to be a spurious interrupt happening at modules
> > > insertion (I suspect sonypi_enable triggering and ignoring it), but this
> > > happens with the old module too and I never noticed it before. Wouldn't
> > > make more sense to print the warning even if verbose=0 to be able to
> > > catch it timely? I mean it's since 2.4 times I don't enable verbose mode
> > > in sonypi...
> > >
> > Probably, let's see what Stelian will say.
>
> This is the "ok I'm loaded" event. I am not sure this event is available
> on all the sonypi supported platforms, that's why it hasn't been defined
> as a known event. And it doesn't make much sense to forward it anyways.
>
> I would leave it like it is now.
>

But when it is reported is it the same event? If so we could just not
warn when we see it (but still dont forward it to the userspace).

--
Dmitry
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/