From: Emil Velikov <emil.l.velikov@gmail.com>
To: Simon Ser <contact@emersion.fr>
Cc: Pekka Paalanen <pekka.paalanen@collabora.com>,
dri-devel <dri-devel@lists.freedesktop.org>,
James Park <james.park@lagfreegames.com>
Subject: Re: [PATCH] drm/fourcc: introduce DRM_FOURCC_STANDALONE guard
Date: Wed, 3 Feb 2021 11:03:59 +0000 [thread overview]
Message-ID: <CACvgo51PDiXPQ=gfChZw2LQmg=NmvshTqw5F3HgkV_9vGYs=5w@mail.gmail.com> (raw)
In-Reply-To: <_L67Dl3bTZirFqSulhWUeN215npWnjsPyUzg7Rb-2iffHxMbZ1-H6ex7R14gdkDqZfpRw9xLoiol8m5WtPKuJxiBN_FcnailoQHvW02qNI0=@emersion.fr>
On Wed, 3 Feb 2021 at 10:15, Simon Ser <contact@emersion.fr> wrote:
>
> On Wednesday, February 3rd, 2021 at 11:08 AM, Emil Velikov <emil.l.velikov@gmail.com> wrote:
>
> > On Wed, 3 Feb 2021 at 09:27, Simon Ser <contact@emersion.fr> wrote:
> > >
> > > On Wednesday, February 3rd, 2021 at 1:56 AM, Emil Velikov emil.l.velikov@gmail.com wrote:
> > >
> > > > As summed in the commit message the burden is only applicable when all
> > > > of the following are set:
> > > > - non-linux
> > > > - force DRM_FOURCC_STANDALONE
> > > > - c99 -pedantic
> > >
> > > Oh, and FWIW, this is not a theoretical situation at all. All of these
> > > conditions happen to be true on my compositor. It has FreeBSD CI,
> > > -Werror, and will use DRM_FOURCC_STANDALONE when available.
> >
> > There are ways to disable [1] or silence [2] this - are you
> > intentionally ignoring them?
>
> We have a policy against pragma. However we already use -std=c11, so in fact
> wouldn't be affected by this change.
>
No issue then, great. Let's merge this trivial solution and move on to
other things.
-Emil
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2021-02-03 11:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-02 22:47 [PATCH] drm/fourcc: introduce DRM_FOURCC_STANDALONE guard Emil Velikov
2021-02-02 23:24 ` James Park
2021-02-03 0:56 ` Emil Velikov
2021-02-03 1:20 ` James Park
2021-02-03 9:24 ` Simon Ser
2021-02-03 9:27 ` Simon Ser
2021-02-03 10:08 ` Emil Velikov
2021-02-03 10:15 ` Simon Ser
2021-02-03 11:03 ` Emil Velikov [this message]
2021-02-03 13:47 ` Simon Ser
2021-02-03 14:13 ` Emil Velikov
2021-02-03 14:20 ` Simon Ser
2021-02-04 4:24 ` James Park
2021-02-04 4:25 ` James Park
2021-02-04 11:52 ` 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='CACvgo51PDiXPQ=gfChZw2LQmg=NmvshTqw5F3HgkV_9vGYs=5w@mail.gmail.com' \
--to=emil.l.velikov@gmail.com \
--cc=contact@emersion.fr \
--cc=dri-devel@lists.freedesktop.org \
--cc=james.park@lagfreegames.com \
--cc=pekka.paalanen@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).