linux-kernel - Re: [alsa-devel] [PATCH v3 2/3] ECI: introducing ECI bus driver

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] [day] [month] [year] [list]

Message-ID: <4D2429F3.80004@nokia.com>
Date:	Wed, 05 Jan 2011 10:21:07 +0200
From:	Peter Ujfalusi <peter.ujfalusi@...ia.com>
To:	"ext tapio.vihuri@...ia.com" <tapio.vihuri@...ia.com>
CC:	dmitry.torokhov@...il.com, randy.dunlap@...cle.com,
	alsa-devel@...a-project.org, ilkka.koskinen@...ia.com,
	linux-kernel@...r.kernel.org, samu.p.onkalo@...ia.com
Subject: Re: [alsa-devel] [PATCH v3 2/3] ECI: introducing ECI bus driver

Hi,

On 01/04/11 16:02, ext tapio.vihuri@...ia.com wrote:
> From: Tapio Vihuri <tapio.vihuri@...ia.com>
> 
> ECI bus controller is kind of bridge between host CPU I2C and ECI accessory
> ECI communication.

There seams to be no change between v2 and v3 in regards to this micro
controller driver, so my comments on the v2 applies here as well.

Would you rename the driver (to something other than ecibus)?
If the intention is to make this driver only work on Intel's Moorestown
platform, then be it, but you should mention it explicitly in the
Kconfig, and the driver name shall reflect the same as well.

My comments on the intel specific intel_scu_ipc_iowrite8, and the i2c
part still holds.

Thanks,
Péter
--
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/