dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Emil Velikov <emil.l.velikov@gmail.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	DRI Development <dri-devel@lists.freedesktop.org>,
	Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [PATCH 2/2] drm: Make uapi headers C89 pendantic compliant
Date: Thu, 31 Mar 2016 07:58:19 +0200	[thread overview]
Message-ID: <20160331055819.GW2510@phenom.ffwll.local> (raw)
In-Reply-To: <CACvgo50_978kx0Rt7TSjSzgndbSiQV=G73xWDrjW0m4yfHcyvQ@mail.gmail.com>

On Wed, Mar 30, 2016 at 09:06:33PM +0100, Emil Velikov wrote:
> On 30 March 2016 at 15:42, Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
> > This ports the below libdrm commit to the kernel
> >
> > commit 0f4452bb51306024fbf4cbf77d8baab20cefba67
> > Author: Daniel Kurtz <djkurtz@chromium.org>
> > Date:   Mon Aug 26 23:39:16 2013 +0800
> >
> >     libdrm: Make some drm headers compatible with gcc -std=c89 -pedantic
> >
> >     The following minor changes were needed to these headers:
> >      * Convert // comments to /* */
> >      * No , after final member of enum
> >
> >     With these changes, these header files can be included by a program that
> >     is built with gcc options:
> >       -std=c89 -Werror -pedantic
> >
> >     Signed-off-by: Daniel Kurtz <djkurtz@chromium.org>
> >     Signed-off-by: Eric Anholt <eric@anholt.net>
> >     Reviewed-by: Eric Anholt <eric@anholt.net>
> >
> > Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
> Yes, please :-)
> 
> Reviewed-by: Emil Velikov <emil.l.velikov@gmail.com>

Also applied, thanks for your review.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2016-03-31  5:58 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-30 14:19 [PATCH 1/3] drm: Make drm.h uapi header safe for C++ Daniel Vetter
2016-03-30 14:19 ` [PATCH 2/3] drm: align #include directives with libdrm in uapi headers Daniel Vetter
2016-03-30 15:05   ` Emil Velikov
2016-03-30 15:11     ` Daniel Vetter
2016-03-30 15:22       ` Emil Velikov
2016-03-30 15:54   ` [PATCH] " Daniel Vetter
2016-03-30 16:08     ` Emil Velikov
2016-03-30 14:19 ` [PATCH 3/3] drm: Move DRM_MODE_OBJECT_* to " Daniel Vetter
2016-03-30 16:07   ` Emil Velikov
2016-03-30 17:55     ` Paulo Zanoni
2016-03-30 19:07       ` Daniel Vetter
2016-03-30 14:42 ` [PATCH 1/2] drm: Untangle __KERNEL__ guards Daniel Vetter
2016-03-30 14:42   ` [PATCH 2/2] drm: Make uapi headers C89 pendantic compliant Daniel Vetter
2016-03-30 20:06     ` Emil Velikov
2016-03-31  5:58       ` Daniel Vetter [this message]
2016-03-30 15:56   ` [PATCH 1/2] drm: Untangle __KERNEL__ guards Emil Velikov
2016-03-30 19:11     ` Daniel Vetter
2016-03-30 15:12 ` [PATCH] drm: Make drm.h uapi header safe for C++ Daniel Vetter
2016-03-30 15:56   ` Emil Velikov
2016-04-06 15:58 ` [PATCH 1/3] " Gabriel Laskar
2016-04-06 16:35   ` Emil Velikov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160331055819.GW2510@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=daniel.vetter@ffwll.ch \
    --cc=daniel.vetter@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=emil.l.velikov@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox