linux-kernel - Re: [PATCH 2.6.29.2] PXA I2C: Define log level for i2c PXA error report

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090511122319.GB20283@sirena.org.uk>
Date:	Mon, 11 May 2009 13:23:19 +0100
From:	Mark Brown <broonie@...ena.org.uk>
To:	Michael Abbott <michael@...neidae.co.uk>
Cc:	???? <wxc200@...il.com>, linux-i2c@...r.kernel.org,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 2.6.29.2] PXA I2C: Define log level for i2c PXA error
	report

On Mon, May 11, 2009 at 01:16:38PM +0100, Michael Abbott wrote:

> However, then, does it make sense for the PXA i2c bus prober to be calling 
> the "scream blue murder" routine in this frankly routine case?  I guess it 
> could just say "no device found at address xx"

You should really convert your board to specify explicitly which chips
are on the board rather than using the old style probe routines.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/