[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <51B59DE3.2000907@itdev.co.uk>
Date: Mon, 10 Jun 2013 10:35:31 +0100
From: Nick Dyer <nick.dyer@...ev.co.uk>
To: Yufeng Shen <miletus@...omium.org>
CC: Dmitry Torokhov <dmitry.torokhov@...il.com>,
Daniel Kurtz <djkurtz@...omium.org>,
Henrik Rydberg <rydberg@...omail.se>,
Joonyoung Shim <jy0922.shim@...sung.com>,
Alan Bowens <Alan.Bowens@...el.com>,
linux-input@...r.kernel.org, linux-kernel@...r.kernel.org,
Peter Meerwald <pmeerw@...erw.net>,
Benson Leung <bleung@...omium.org>,
Olof Johansson <olofj@...omium.org>
Subject: Re: [PATCH 44/53] Input: atmel_mxt_ts - Verify Information Block
checksum on probe
Yufeng Shen wrote:
>> + dev_info(&client->dev,
>> + "Family: %u Variant: %u Firmware V%u.%u.%02X Objects: %u\n",
>> + info->family_id, info->variant_id, info->version >> 4,
>> + info->version & 0xf, info->build, info->object_num);
>> +
>
> Use data->info->XXX here, info was pointing to buf which could have
> changed after krealloc.
Thank you, that's a really good spot. Caused when I merged the dev_info
line into that function. It actually explains a report I had about getting
junk in this output but the info_crc check succeeding, hadn't had time to
investigate yet.
I will fix.
--
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