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: Re: [igt-dev] [PATCH v2 i-g-t 0/2] Fix some GCC warnings
Date: Mon, 20 Aug 2018 10:39:46 -0300 [thread overview]
Message-ID: <20180820133946.3nuvatpqpy4gywjr@smtp.gmail.com> (raw)
In-Reply-To: <cover.1532867044.git.rodrigosiqueiramelo@gmail.com>
Hi,
I would like to know if there is any improvement that I can do for this
patchset.
Thanks
On 07/29, Rodrigo Siqueira wrote:
> During the compilation, some GCC (8.1) warnings are shown. This patchset
> address some of the warnings problems.
>
> Changes since v2:
> - Reduce the total amount of bytes allocated during command handling
> operation
> - Remove unnecessary memset operation
> - Improved commit message
>
> Rodrigo Siqueira (2):
> Make string commands dynamic allocate
> Fix truncate string in the snprintf
>
> tools/intel_gvtg_test.c | 25 ++++++++++++++++---------
> tools/intel_reg.c | 2 +-
> 2 files changed, 17 insertions(+), 10 deletions(-)
>
> --
> 2.17.0
>
--
Rodrigo Siqueira
http://siqueira.tech
Graduate Student
Department of Computer Science
University of São Paulo
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
prev parent reply other threads:[~2018-08-20 13:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-29 12:41 [igt-dev] [PATCH v2 i-g-t 0/2] Fix some GCC warnings Rodrigo Siqueira
2018-07-29 12:41 ` [Intel-gfx] [PATCH v2 i-g-t 1/2] Make string commands dynamic allocate Rodrigo Siqueira
2018-07-29 12:41 ` [igt-dev] [PATCH v2 i-g-t 2/2] Fix truncate string in the snprintf Rodrigo Siqueira
2018-07-29 13:41 ` [igt-dev] ✓ Fi.CI.BAT: success for Fix some GCC warnings (rev2) Patchwork
2018-07-29 15:00 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2018-08-20 13:39 ` Rodrigo Siqueira [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=20180820133946.3nuvatpqpy4gywjr@smtp.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;
as well as URLs for NNTP newsgroup(s).