From: Mike Frysinger <vapier@gentoo.org>
To: Petri Latvala <petri.latvala@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH i-g-t] include inttypes.h for PRI defines
Date: Wed, 10 Jan 2018 17:12:33 -0500 [thread overview]
Message-ID: <20180110221233.GC7217@vapier> (raw)
In-Reply-To: <20180110104224.rf2s4c2y26drvwf6@platvala-desk.ger.corp.intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 979 bytes --]
On 10 Jan 2018 12:42, Petri Latvala wrote:
> On Tue, Jan 09, 2018 at 10:50:53PM -0500, Mike Frysinger wrote:
> > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=96620
> > Signed-off-by: Mike Frysinger <vapier@gentoo.org>
> > ---
> > lib/igt_fb.c | 1 +
> > 1 file changed, 1 insertion(+)
>
>
> Files matching "PRI[diuoxX]" but not "inttypes.h":
>
> lib/igt_fb.c
> lib/igt_kms.c
> lib/intel_os.c
> tests/prime_nv_pcopy.c
> tools/hsw_compute_wrpll.c
> tools/intel_gpu_top.c
> tools/intel_opregion_decode.c
> tools/intel_residency.c
> tools/intel_watermark.c
>
> Looks like they get inttypes.h here via
>
> igt.h and pals -> intel_chipset.h -> pciaccess.h -> inttypes.h
>
> The mystery is why the other files haven't slapped you with the same
> issue. Regardless, same change should be done in all of those. Can you
> expand this patch?
yeah i patched the one that was failing rather than looking deeper.
i can update them all.
-mike
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-01-10 22:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-10 3:50 [PATCH i-g-t] include inttypes.h for PRI defines Mike Frysinger
2018-01-10 4:09 ` ✓ Fi.CI.BAT: success for include inttypes.h for PRI defines (rev2) Patchwork
2018-01-10 4:55 ` ✗ Fi.CI.IGT: failure " Patchwork
2018-01-10 10:42 ` [PATCH i-g-t] include inttypes.h for PRI defines Petri Latvala
2018-01-10 22:12 ` Mike Frysinger [this message]
2018-01-10 22:12 ` [PATCH i-g-t v2] " Mike Frysinger
2018-01-11 9:12 ` Petri Latvala
2018-01-10 22:32 ` ✓ Fi.CI.BAT: success for include inttypes.h for PRI defines (rev3) Patchwork
-- strict thread matches above, loose matches on Subject: below --
2016-06-22 11:08 [PATCH i-g-t] include inttypes.h for PRI defines Mike Frysinger
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=20180110221233.GC7217@vapier \
--to=vapier@gentoo.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