From: Damien Lespiau <damien.lespiau@intel.com>
To: intel-gfx@lists.freedesktop.org, daniel.vetter@ffwll.ch,
Chris Wilson <chris@chris-wilson.co.uk>
Subject: Re: [PATCH i-g-t] benchmarks/, overlay/, demos/, tools/, tests/: Add Werror by default.
Date: Mon, 9 May 2016 16:57:14 +0100 [thread overview]
Message-ID: <20160509155714.GA15880@strange.ger.corp.intel.com> (raw)
In-Reply-To: <20160509155511.GB29124@mcvlad-wk.rb.intel.com>
On Mon, May 09, 2016 at 06:55:12PM +0300, Marius Vlad wrote:
> > Adding a test (with patchwork integration!) that ensures each commit
> > posted on this mailing-list compiles without new warning with a chosen
> > toolchain (and even passes distcheck!) would be nice.
> We have this for check and distcheck internally. The whole point of
> Werror was to catch warnings as well when building, and letting us know
> so we can fix it. The problem is (unfortunately) that not all patches
> arrive thru m-l. Don't really know how much traction some CI/buildbot
> for i-g-t will have.
Oh, CI for i-g-t patches is a must have and on the roadmap. Can't really
keep on testing kernel patches if we can just regress everything with
random i-g-t patches.
Doing the distcheck for every patch on the ml would already be a nice
thing.
Alternatively, you could have an --enable-werror configure flag
developers may wish to use.
--
Damien
_______________________________________________
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-09 15:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-09 13:23 [PATCH i-g-t] benchmarks/, overlay/, demos/, tools/, tests/: Add Werror by default Marius Vlad
2016-05-09 15:25 ` Damien Lespiau
2016-05-09 15:55 ` Marius Vlad
2016-05-09 15:57 ` Damien Lespiau [this message]
2016-05-09 16:01 ` Morton, Derek J
2016-05-10 14:32 ` [PATCH i-g-t] benchmarks/, overlay/, demos/, tools/, tests/: Add optional Werror Marius Vlad
2016-05-10 15:42 ` Damien Lespiau
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=20160509155714.GA15880@strange.ger.corp.intel.com \
--to=damien.lespiau@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
/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.