From: Eric Engestrom <eric.engestrom@intel.com>
To: Emil Velikov <emil.l.velikov@gmail.com>
Cc: dri-devel <dri-devel@lists.freedesktop.org>,
Christopher James Halse Rogers
<christopher.halse.rogers@canonical.com>,
Emil Velikov <emil.velikov@collabora.com>
Subject: Re: [PATCH libdrm] xf86drm: fix return type for drmIsMaster()
Date: Fri, 8 Feb 2019 18:50:18 +0000 [thread overview]
Message-ID: <20190208185018.ocalcp7twgryimjq@intel.com> (raw)
In-Reply-To: <CACvgo52LPdnoYpRZAO96fzbuqfR8Uc34DUUR-VWDhh1rNaJx2A@mail.gmail.com>
On Friday, 2019-02-08 16:50:44 +0000, Emil Velikov wrote:
> On Fri, 8 Feb 2019 at 16:51, Daniel Stone <daniel@fooishbar.org> wrote:
> >
> > Hi Eric,
> >
> > On Fri, 8 Feb 2019 at 15:03, Eric Engestrom <eric.engestrom@intel.com> wrote:
> > > Xserver has struct members named `bool`, which means the last commit
> > > breaks its build with errors like this:
> > >
> > > error: two or more data types in declaration specifiers
> > > Bool bool;
> > > ^
> > >
> > > Fix this by making it return a 0/1 integer, with the same semantic as
> > > the boolean it was before.
> >
> > Don't you need to drop the stdbool.h include for this to fix compilation?
Ahem... /me looks for his brown paper bag :]
> >
> Thanks Eric. With Dan's comment
> Reviewed-by: Emil Velikov <emil.velikov@collabora.com>
>
> I really wonder if we cannot fix these trivial X nuisances? As-is
> every project used has to either work around X mistakes :-(
> Wrt libdrm that is fine, yet other projects might be less happy.
Agreed :/
The issue is that you still won't be able to have bools in libdrm,
because a new libdrm might be used with an old xserver...
>
> Thanks
> -Emil
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2019-02-08 18:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-08 15:02 [PATCH libdrm] xf86drm: fix return type for drmIsMaster() Eric Engestrom
2019-02-08 16:51 ` Daniel Stone
2019-02-08 16:50 ` Emil Velikov
2019-02-08 18:50 ` Eric Engestrom [this message]
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=20190208185018.ocalcp7twgryimjq@intel.com \
--to=eric.engestrom@intel.com \
--cc=christopher.halse.rogers@canonical.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=emil.l.velikov@gmail.com \
--cc=emil.velikov@collabora.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.