>> @@ -42,10 +42,9 @@ static int emi26_writememory (struct usb_device *dev, int
>> address,
>> int result;
>> unsigned char *buffer = kmemdup(data, length, GFP_KERNEL);
>>
>> - if (!buffer) {
>> - dev_err(&dev->dev, "kmalloc(%d) failed.\n", length);
>
> I guess the length information would not be so easy to find in the backtrace.
Why do you “guess”?
>> + if (!buffer)
>> return -ENOMEM;
>> - }
Would we like to achieve another consensus on the data which are provided by
a default Linux allocation failure report?
Regards,
Markus
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
