On Mon, Jul 6, 2015 at 9:59 AM, Samuel Ortiz <sameo@xxxxxxxxxxxxxxx> wrote:
>
> Ok, if you can suspend after this modprobe we're looking at some
> potential mei bus or mei core issues.
Just looking at the mei/bus.c code to match the driver, and it looks just odd.
Before the commit that breaks for me, it used to have this loop:
- while (id->name[0]) {
and now it has
+ while (uuid_le_cmp(NULL_UUID_LE, uuid_le_cast(id->uuid))) {
which seems to mean that together with my change to make a working
kernel (just removing the UUID entirely) means that now the
device_driver isn't matched against anything at all any more.
So I'm not sure "modprobe pn544_mei" ends up actually triggering
anything at all with my change to make it not lock up for me.
Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-api" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
