From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Jérémy Lefaure" <jeremy.lefaure@lse.epita.fr>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✓ Fi.CI.BAT: success for drm/i915: fix compilation warnings on maybe uninitialized pointers
Date: Tue, 29 Nov 2016 00:19:02 -0000 [thread overview]
Message-ID: <20161129001902.30699.30432@emeril.freedesktop.org> (raw)
In-Reply-To: <20161128234319.20800-1-jeremy.lefaure@lse.epita.fr>
== Series Details ==
Series: drm/i915: fix compilation warnings on maybe uninitialized pointers
URL : https://patchwork.freedesktop.org/series/16061/
State : success
== Summary ==
Series 16061v1 drm/i915: fix compilation warnings on maybe uninitialized pointers
https://patchwork.freedesktop.org/api/1.0/series/16061/revisions/1/mbox/
fi-bdw-5557u total:245 pass:230 dwarn:0 dfail:0 fail:0 skip:15
fi-byt-n2820 total:245 pass:213 dwarn:0 dfail:0 fail:0 skip:32
fi-ilk-650 total:245 pass:192 dwarn:0 dfail:0 fail:0 skip:53
fi-skl-6260u total:245 pass:231 dwarn:0 dfail:0 fail:0 skip:14
fi-skl-6700k total:245 pass:223 dwarn:1 dfail:0 fail:0 skip:21
fi-snb-2520m total:245 pass:213 dwarn:0 dfail:0 fail:0 skip:32
477cc06f6ef4842fd63e28ff30d721462af199a6 drm-tip: 2016y-11m-28d-16h-17m-39s UTC integration manifest
adeefab drm/i915: fix compilation warnings on maybe uninitialized pointers
== Logs ==
For more details see: https://intel-gfx-ci.01.org/CI/Patchwork_3130/
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-11-29 0:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-28 23:43 [PATCH] drm/i915: fix compilation warnings on maybe uninitialized pointers Jérémy Lefaure
2016-11-29 0:19 ` Patchwork [this message]
2016-11-29 8:56 ` [Intel-gfx] " Daniel Vetter
2016-11-29 9:10 ` Tvrtko Ursulin
2016-11-29 10:45 ` ✓ Fi.CI.BAT: success for " 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=20161129001902.30699.30432@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jeremy.lefaure@lse.epita.fr \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.