From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Brownell Subject: Re: [PATCH] i2c: Match dummy devices by type Date: Mon, 5 May 2008 10:06:20 -0700 Message-ID: <200805051006.21123.david-b@pacbell.net> References: <20080505112858.5101c99a@hyperion.delvare> <200805050833.55242.david-b@pacbell.net> <20080505184319.462b0ce6@hyperion.delvare> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20080505184319.462b0ce6-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org> Content-Disposition: inline List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: i2c-bounces-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org Errors-To: i2c-bounces-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org To: Jean Delvare Cc: Linux I2C List-Id: linux-i2c@vger.kernel.org On Monday 05 May 2008, Jean Delvare wrote: > On Mon, 5 May 2008 08:33:54 -0700, David Brownell wrote: > > On Monday 05 May 2008, Jean Delvare wrote: > > > little reason to use these i2c clients to log messages. > > = > > I'd assume the opposite, actually. =A0Any i2c_client should > > be sensible to use for message logging. > = > I'd expect drivers to use the main i2c_client for that. That is, you're expecting drivers to invest *extra* work to keep track of such stuff ... Probably not a big deal, since the messages will at least be labeled according to the device address. And not many drivers need such stuff. But I still think it's better not to expect "busy work" like that. - Dave _______________________________________________ i2c mailing list i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org http://lists.lm-sensors.org/mailman/listinfo/i2c