Pavel Machek wrote:
> Hi!
>
>> This were the original plan we've discussed, back in December:
> ....
>
> Seems sane.
>
>> struct keycode_table_entry {
>> unsigned keycode;
>> char scancode[32]; /* 32 is just an arbitrary long array - maybe shorter */
>> int len;
>> }
>
> What about
>
> struct keycode_table_entry {
> unsigned keycode;
> int len;
> char scancode[];
> }
>
> ? gcc extension, but commonly used around kernel.
Seems fine. Maybe we could just use "char *scancode" to avoid using a
gcc extension on a public interface.
--
Cheers,
Mauro
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
