linux-kernel - Re: [PATCH] Incremental i2c-mpc driver fix for multi-master i2c busses.

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]

Date:	Mon, 12 Jan 2009 14:12:00 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Clifford Wolf <clifford@...fford.at>
Cc:	linux-kernel@...r.kernel.org, i2c@...sensors.org,
	khali@...ux-fr.org, adrian@...boldt.co.uk,
	linux-i2c@...r.kernel.org, Ben Dooks <ben-linux@...ff.org>
Subject: Re: [PATCH] Incremental i2c-mpc driver fix for multi-master i2c
 busses.

On Mon, 5 Jan 2009 14:21:02 +0100
Clifford Wolf <clifford@...fford.at> wrote:

> Incremental i2c-mpc driver fix for multi-master i2c busses.
> 
> This is an incremental bugfix for the i2c-mpc driver. It is based
> on the bugfix I've sent on 2008-12-22:
> 
> 	http://lkml.org/lkml/2008/12/22/99
> 
> There still was a remaining problem with multi-master i2c busses
> when an i2c bus access is interrupted by a unix signal while
> waiting for bus arbitration.
> 
> This is an extreamly rare case but I managed to stumble over it in
> multi master i2c performance tests.
> 
> Tested with a freescale MPC8349E host cpu.

That's not a very good changelog - it has basically no information,
apart from the linked-to original changelog.

And the linked-to changelog has no description of the bug which is
being fixed.

> --- drivers/i2c/busses/i2c-mpc.c	(revision 2216)
> +++ drivers/i2c/busses/i2c-mpc.c	(working copy)

Please prepare patches in `patch -p1' form:

--- a/drivers/i2c/busses/i2c-mpc.c
+++ a/drivers/i2c/busses/i2c-mpc.c

--
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/