From: Eric Anholt <eric@anholt.net>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [PATCH i-g-t v2 2/6] meson: Drop -Wdeclaration-after-statement.
Date: Thu, 15 Nov 2018 10:57:33 -0800 [thread overview]
Message-ID: <20181115185737.19311-2-eric@anholt.net> (raw)
In-Reply-To: <20181115185737.19311-1-eric@anholt.net>
Being able to move declarations later is very useful in making clear,
concise code.
Signed-off-by: Eric Anholt <eric@anholt.net>
---
meson.build | 1 -
1 file changed, 1 deletion(-)
diff --git a/meson.build b/meson.build
index 469723dc4633..c5aab78716d5 100644
--- a/meson.build
+++ b/meson.build
@@ -11,7 +11,6 @@ cc = meson.get_compiler('c')
cc_args = [
'-Wbad-function-cast',
- '-Wdeclaration-after-statement',
'-Wformat=2',
# igt_assert(0) in switch statements triggers a bunch of this.
'-Wimplicit-fallthrough=0',
--
2.19.1
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2018-11-15 18:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-15 18:57 [igt-dev] [PATCH i-g-t v2 1/6] kms_content_protection: Fix log bug on 32-bit platforms Eric Anholt
2018-11-15 18:57 ` Eric Anholt [this message]
2018-11-15 18:57 ` [igt-dev] [PATCH i-g-t v2 3/6] v3d: Import the V3D DRM UAPI header Eric Anholt
2018-11-15 18:57 ` [igt-dev] [PATCH i-g-t v2 4/6] v3d: Add a helper library Eric Anholt
2018-11-15 18:57 ` [igt-dev] [PATCH i-g-t v2 5/6] v3d_*: Add new tests for the V3D UABI Eric Anholt
2018-11-15 18:57 ` [igt-dev] [PATCH i-g-t v2 6/6] v3d: Add tests for hanging V3D using an RCL Eric Anholt
2018-11-15 19:41 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,v2,1/6] kms_content_protection: Fix log bug on 32-bit platforms Patchwork
2018-11-15 20:39 ` [igt-dev] [PATCH i-g-t v2 1/6] " Ville Syrjälä
2018-11-15 21:35 ` [igt-dev] ✓ Fi.CI.IGT: success for series starting with [i-g-t,v2,1/6] " Patchwork
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=20181115185737.19311-2-eric@anholt.net \
--to=eric@anholt.net \
--cc=igt-dev@lists.freedesktop.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