From: Rodrigo Siqueira <rodrigosiqueiramelo@gmail.com>
To: Petri Latvala <petri.latvala@intel.com>,
Arkadiusz Hiler <arkadiusz.hiler@intel.com>
Cc: igt-dev@lists.freedesktop.org, gustavo@padovan.org,
intel-gfx@lists.freedesktop.org
Subject: [igt-dev] [PATCH i-g-t 0/3] Fix some GCC warnings
Date: Tue, 29 May 2018 21:46:21 -0300 [thread overview]
Message-ID: <cover.1527639529.git.rodrigosiqueiramelo@gmail.com> (raw)
During the compilation, some GCC (8.1) warnings are shown. This patchset
address some of the warnings problems.
Rodrigo Siqueira (3):
Avoid truncate string in __igt_lsof_fds
Remove extra '\0' in strncpy in igt_save_module_param
Move declaration to the top of the code
lib/igt_aux.c | 4 ++--
lib/igt_color_encoding.c | 16 ++++++----------
tests/kms_frontbuffer_tracking.c | 2 +-
3 files changed, 9 insertions(+), 13 deletions(-)
--
2.17.0
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next reply other threads:[~2018-05-30 0:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-30 0:46 Rodrigo Siqueira [this message]
2018-05-30 0:46 ` [igt-dev] [PATCH i-g-t 1/3] Avoid truncate string in __igt_lsof_fds Rodrigo Siqueira
2018-06-04 10:40 ` [Intel-gfx] " Arkadiusz Hiler
2018-06-05 1:45 ` [igt-dev] " Rodrigo Siqueira
2018-05-30 0:46 ` [igt-dev] [PATCH i-g-t 2/3] Remove extra '\0' in strncpy in igt_save_module_param Rodrigo Siqueira
2018-06-04 11:04 ` [Intel-gfx] " Arkadiusz Hiler
2018-05-30 0:47 ` [igt-dev] [PATCH i-g-t 3/3] Move declaration to the top of the code Rodrigo Siqueira
2018-06-04 10:54 ` Arkadiusz Hiler
2018-05-30 2:25 ` [igt-dev] ✓ Fi.CI.BAT: success for Fix some GCC warnings Patchwork
2018-05-30 4:26 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2018-06-04 8:39 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2018-06-04 9:54 ` [igt-dev] ✓ Fi.CI.IGT: " 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=cover.1527639529.git.rodrigosiqueiramelo@gmail.com \
--to=rodrigosiqueiramelo@gmail.com \
--cc=arkadiusz.hiler@intel.com \
--cc=gustavo@padovan.org \
--cc=igt-dev@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=petri.latvala@intel.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