From: Jani Nikula <jani.nikula@linux.intel.com>
To: Emil Velikov <emil.l.velikov@gmail.com>, Daniel Vetter <daniel@ffwll.ch>
Cc: Maxime Ripard <maxime.ripard@bootlin.com>,
David Airlie <airlied@linux.ie>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
Sam Ravnborg <sam@ravnborg.org>,
ML dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH v1 0/2] drm: drop uapi dependencies from include/drm
Date: Mon, 24 Jun 2019 13:55:35 +0300 [thread overview]
Message-ID: <87mui7s15k.fsf@intel.com> (raw)
In-Reply-To: <CACvgo53j8XEiTO3+g_692GkcvzHAViMzhh_ZuK+-6W4kHm0pgw@mail.gmail.com>
On Mon, 24 Jun 2019, Emil Velikov <emil.l.velikov@gmail.com> wrote:
> On Mon, 24 Jun 2019 at 09:21, Daniel Vetter <daniel@ffwll.ch> wrote:
>
>> > drm_legacy.h
>> > - needs drm_map_type and drm_map_flags. Seems legit.
>>
>> enum in uapi, sweet (never do this, it's not portable across compilers,
>> #defines all the way).
>
> Don't look too closely then
> $ git grep enum -- include/uapi/drm/ | wc -l
> 96
>
> A handful of those are legacy stuff, yet quite a few are not :-\
Enums are just fine for *values* as long as they're not used as types in
struct members or function parameters or return types, right?
So we do have some we've screwed up, but it's not nearly as bad as the
git grep above would lead you to believe.
The ones in question are used in struct drm_map which is used in
DRM_IOCTL_GET_MAP, DRM_IOCTL_ADD_MAP, and DRM_IOCTL_RM_MAP.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-06-24 10:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-22 12:11 [PATCH v1 0/2] drm: drop uapi dependencies from include/drm Sam Ravnborg
2019-06-22 12:11 ` [PATCH v1 1/2] drm: drop uapi dependency from drm_print.h Sam Ravnborg
2019-06-22 12:11 ` [PATCH v1 2/2] drm: drop uapi dependency from drm_vblank.h Sam Ravnborg
2019-06-22 12:44 ` ✓ Fi.CI.BAT: success for drm: drop uapi dependencies from include/drm Patchwork
2019-06-22 14:05 ` ✓ Fi.CI.IGT: " Patchwork
2019-06-24 8:21 ` [PATCH v1 0/2] " Daniel Vetter
2019-06-24 10:07 ` Emil Velikov
2019-06-24 10:55 ` Jani Nikula [this message]
2019-06-24 20:39 ` Sam Ravnborg
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=87mui7s15k.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=emil.l.velikov@gmail.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=maxime.ripard@bootlin.com \
--cc=sam@ravnborg.org \
/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