On Wed, Dec 14, 2016 at 03:46:03PM +, Emil Velikov wrote:
> On 12 December 2016 at 23:28, Grazvydas Ignotas wrote:
> > On Mon, Dec 12, 2016 at 3:59 PM, Emil Velikov
> > wrote:
> >> On 11 December 2016 at 18:03, Grazvydas Ignotas
> >> wrote:
> >>> Just tell the compiler that drm_event will
On 12 December 2016 at 23:28, Grazvydas Ignotas wrote:
> On Mon, Dec 12, 2016 at 3:59 PM, Emil Velikov
> wrote:
>> On 11 December 2016 at 18:03, Grazvydas Ignotas wrote:
>>> Just tell the compiler that drm_event will alias the char buffer,
>>> so that it has no excuse to warn or generate bad co
On Mon, Dec 12, 2016 at 3:59 PM, Emil Velikov
wrote:
> On 11 December 2016 at 18:03, Grazvydas Ignotas wrote:
>> Just tell the compiler that drm_event will alias the char buffer,
>> so that it has no excuse to warn or generate bad code.
>>
> Afacit this patch [1] from Thierry should correctly ad
On 11 December 2016 at 18:03, Grazvydas Ignotas wrote:
> Just tell the compiler that drm_event will alias the char buffer,
> so that it has no excuse to warn or generate bad code.
>
Afacit this patch [1] from Thierry should correctly address the issue, correct ?
I've been meaning to parse through
Just tell the compiler that drm_event will alias the char buffer,
so that it has no excuse to warn or generate bad code.
Signed-off-by: Grazvydas Ignotas
---
Android.mk | 1 +
configure.ac| 9 +
libdrm_macros.h | 6 ++
xf86drmMode.c | 11 +++
4 files changed, 23
