From: robert.foss@collabora.com
To: daniel.vetter@ffwll.ch, daniel.stone@collabora.com,
marius.c.vlad@intel.com, tomeu.vizoso@collabora.com,
emil.velikov@collabora.com, chris@chris-wilson.co.uk
Cc: intel-gfx@lists.freedesktop.org
Subject: [RFC i-g-t 5/7] tools/Makefile: Format whitespace.
Date: Wed, 25 May 2016 14:18:54 -0400 [thread overview]
Message-ID: <1464200336-15671-6-git-send-email-robert.foss@collabora.com> (raw)
In-Reply-To: <1464200336-15671-1-git-send-email-robert.foss@collabora.com>
From: Robert Foss <robert.foss@collabora.com>
Harmonize tabs/spaces etc.
Signed-off-by: Robert Foss <robert.foss@collabora.com>
---
tools/Makefile.sources | 57 +++++++++++++++++++++++++-------------------------
1 file changed, 29 insertions(+), 28 deletions(-)
diff --git a/tools/Makefile.sources b/tools/Makefile.sources
index 07d8d9b..7ed5fe5 100644
--- a/tools/Makefile.sources
+++ b/tools/Makefile.sources
@@ -1,33 +1,34 @@
-noinst_PROGRAMS = \
- hsw_compute_wrpll \
- skl_compute_wrpll \
- skl_ddb_allocation \
+noinst_PROGRAMS = \
+ hsw_compute_wrpll \
+ skl_compute_wrpll \
+ skl_ddb_allocation \
$(NULL)
-bin_PROGRAMS = \
- igt_stats \
- intel_audio_dump \
- intel_reg \
- intel_backlight \
- intel_bios_dumper \
- intel_bios_reader \
- intel_display_crc \
- intel_display_poller \
- intel_forcewaked \
- intel_gpu_frequency \
- intel_firmware_decode \
- intel_gpu_time \
- intel_gpu_top \
- intel_gtt \
- intel_infoframes \
- intel_l3_parity \
- intel_lid \
- intel_opregion_decode \
- intel_panel_fitter \
- intel_reg_checker \
- intel_residency \
- intel_stepping \
- intel_watermark
+bin_PROGRAMS = \
+ igt_stats \
+ intel_audio_dump \
+ intel_reg \
+ intel_backlight \
+ intel_bios_dumper \
+ intel_bios_reader \
+ intel_display_crc \
+ intel_display_poller \
+ intel_forcewaked \
+ intel_gpu_frequency \
+ intel_firmware_decode \
+ intel_gpu_time \
+ intel_gpu_top \
+ intel_gtt \
+ intel_infoframes \
+ intel_l3_parity \
+ intel_lid \
+ intel_opregion_decode \
+ intel_panel_fitter \
+ intel_reg_checker \
+ intel_residency \
+ intel_stepping \
+ intel_watermark \
+ $(NULL)
dist_bin_SCRIPTS = intel_gpu_abrt
--
2.7.4
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-05-25 18:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-25 18:18 [RFC i-g-t 0/7] Remove compile time depencencies on libdrm_intel robert.foss
2016-05-25 18:18 ` [RFC i-g-t 1/7] configure.ac: Test for libdrm_intel and build for it if present robert.foss
2016-05-25 21:50 ` Rémi Cardona
2016-05-25 18:18 ` [RFC i-g-t 2/7] configure.ac: Harmonize HAVE_XXX flag for all drm platforms to HAVE_LIBDRM_XXX robert.foss
2016-05-25 18:18 ` [RFC i-g-t 3/7] benchmarks/Makefile: Don't build benchmarks that depend on libdrm_intel robert.foss
2016-05-25 18:18 ` [RFC i-g-t 4/7] tools/Makefile: Don't build tools " robert.foss
2016-05-25 18:18 ` robert.foss [this message]
2016-05-25 18:18 ` [RFC i-g-t 6/7] demos/Makefile: " robert.foss
2016-05-25 18:18 ` [RFC i-g-t 7/7] lib/stubs: Add stubs for intel_bufmgr robert.foss
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=1464200336-15671-6-git-send-email-robert.foss@collabora.com \
--to=robert.foss@collabora.com \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.stone@collabora.com \
--cc=daniel.vetter@ffwll.ch \
--cc=emil.velikov@collabora.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=marius.c.vlad@intel.com \
--cc=tomeu.vizoso@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).