lkml.org 
[lkml]   [2012]   [Apr]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH 1/2] HID: hid-lg4ff: Use Private Data
On 04/02/2012 07:01 PM, simon@mungewell.org wrote:
>
>>> + struct lg4ff_device_entry *uninitialized_var(entry);
>>> + struct lg_drv_data *uninitialized_var(drv_data);
>>
>> You don't need uninitialized_var bloat anymroe, right?
>
> I guess I don't fully understand the 'unitialized_var()' macro, and was
> just following the previous uses in the code.
>
> Google'ing doesn't really help either. Is there a definitive guide as when
> to use and not?

The simple answer is: never.

It serves the purpose to shut up the compiler when it complains that the
variable might be uninitialized, but the programmer is sure it cannot.
In your case, the compiler should not even complain about that.

Advantage of the macro is that it adds no assembly, but still silents
the compiler.

thanks,
--
js
suse labs




\
 
 \ /
  Last update: 2012-04-02 19:33    [from the cache]
©2003-2014 Jasper Spaans. Advertise on this site