[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4BABB2DB.8030305@redhat.com>
Date: Thu, 25 Mar 2010 16:00:43 -0300
From: Mauro Carvalho Chehab <mchehab@...hat.com>
To: Pavel Machek <pavel@....cz>
CC: Jon Smirl <jonsmirl@...il.com>,
Dmitry Torokhov <dmitry.torokhov@...il.com>,
Krzysztof Halasa <khc@...waw.pl>,
hermann pitton <hermann-pitton@...or.de>,
Christoph Bartelmus <lirc@...telmus.de>, awalls@...ix.net,
j@...nau.net, jarod@...hat.com, jarod@...sonet.com,
kraxel@...hat.com, linux-input@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-media@...r.kernel.org,
superm1@...ntu.com
Subject: Re: [RFC] What are the goals for the architecture of an in-kernel
IR system?
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-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