[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <47A1A441-952C-4AC3-859C-5A8E405767E0@gmail.com>
Date: Mon, 24 Nov 2014 22:39:42 +0300
From: Alexander Kochetkov <al.kochet@...il.com>
To: Kevin Hilman <khilman@...nel.org>
Cc: Felipe Balbi <balbi@...com>, Wolfram Sang <wsa@...-dreams.de>,
Alexander Kochetkov <al.kochet@...il.com>,
Kevin Hilman <khilman@...nel.org>,
Tony Lindgren <tony@...mide.com>,
linux-omap <linux-omap@...r.kernel.org>,
linux-i2c@...r.kernel.org, lkml <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3 2/4] i2c: omap: implement workaround for handling invalid BB-bit values
24 нояб. 2014 г., в 22:08, Kevin Hilman <khilman@...nel.org> написал(а):
> This patch recently hit linux-next (as commit 903c3859f77f) and boot
> breakage[1] in next-20141124 on OMAP3530 Beagle and Overo/Tobi boards
> was bisected down to this commit.
>
> Kevin
>
> [1] http://status.armcloud.us/boot/?next-20141124&omap
Could someone advice with debugging on OMAP3530?
I'd like to apply one one more commit to see events during boot and
see actual signals on wire (during of timeout)?
Otherwise, commit must dropped (or rewritten such way it is disabled by default).
24 нояб. 2014 г., в 22:13, Wolfram Sang <wsa@...-dreams.de> написал(а):
> OK, giving Alexander some time for a fix. If it can't be found, I'll
> revert this patch. Thanks!
What deadline?
Alexander.
--
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/
Powered by blists - more mailing lists