* Re: [PATCH] Incremental i2c-mpc driver fix for multi-master i2c busses.
[not found] ` <20090105132102.GA27855-cPpHkPqGOEfk7+2FdBfRIA@public.gmane.org>
@ 2009-01-12 22:12 ` Andrew Morton
0 siblings, 0 replies; only message in thread
From: Andrew Morton @ 2009-01-12 22:12 UTC (permalink / raw)
To: Clifford Wolf
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA, i2c-GZX6beZjE8VD60Wz+7aTrA,
khali-PUYAD+kWke1g9hUCZPvPmw, adrian-nKrwMtk+6Wm9FHfhHBbuYA,
linux-i2c-u79uwXL29TY76Z2rM5mHXA, Ben Dooks
On Mon, 5 Jan 2009 14:21:02 +0100
Clifford Wolf <clifford-cPpHkPqGOEfk7+2FdBfRIA@public.gmane.org> 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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2009-01-12 22:12 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <20090105132102.GA27855@clifford.at>
[not found] ` <20090105132102.GA27855-cPpHkPqGOEfk7+2FdBfRIA@public.gmane.org>
2009-01-12 22:12 ` [PATCH] Incremental i2c-mpc driver fix for multi-master i2c busses Andrew Morton
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox