From: Daniel Vetter <daniel@ffwll.ch>
To: Daniel Vetter <daniel@ffwll.ch>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
IGT development <igt-dev@lists.freedesktop.org>,
Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t 1/7] automake: Drop gtkdoc build remnants
Date: Tue, 29 Jan 2019 11:11:41 +0100 [thread overview]
Message-ID: <20190129101141.GQ3271@phenom.ffwll.local> (raw)
In-Reply-To: <20190123121527.GD4038@platvala-desk.ger.corp.intel.com>
On Wed, Jan 23, 2019 at 02:15:27PM +0200, Petri Latvala wrote:
> On Wed, Jan 23, 2019 at 12:42:01PM +0100, Daniel Vetter wrote:
> > On Wed, Jan 23, 2019 at 01:10:49PM +0200, Petri Latvala wrote:
> > > On Tue, Jan 22, 2019 at 02:42:09PM +0100, Daniel Vetter wrote:
> > > > If you have gtkdoc installed, then autogen.sh stopped working ever
> > > > since:
> > > >
> > > > commit ad821d1dc5d0eea4ac3a0e8e29c56c7f66191108
> > > > Author: Daniel Vetter <daniel.vetter@ffwll.ch>
> > > > Date: Thu Dec 13 13:43:55 2018 +0100
> > > >
> > > > autoconf: Drop gtkdoc support
> > > >
> > > > Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
> > >
> > > Series is
> > >
> > > Acked-by: Petri Latvala <petri.latvala@intel.com>
> > >
> > > Do you have this in a gitlab fork, does it pass its CI?
> >
> > I forgt, and ofc it fails:
> >
> > https://gitlab.freedesktop.org/danvet/igt-gpu-tools/-/jobs/87726
> >
> > I think just changing the test scrip to ignore vc4/v3d tests should get
> > this covered?
>
>
> Yeah, that sounds good.
Ok, pushed the entire pile, thanks for taking a look.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-01-29 10:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-22 13:42 [igt-dev] [PATCH i-g-t 1/7] automake: Drop gtkdoc build remnants Daniel Vetter
2019-01-22 13:42 ` [igt-dev] [PATCH i-g-t 2/7] automake: Drop manpage build support Daniel Vetter
2019-01-22 13:42 ` [igt-dev] [PATCH i-g-t 3/7] automake: drop assembler/shader-debugger automake support Daniel Vetter
2019-01-22 13:42 ` [igt-dev] [PATCH i-g-t 4/7] automake: Point builders at meson Daniel Vetter
2019-01-22 13:42 ` [igt-dev] [PATCH i-g-t 5/7] automake: Drop runner build support Daniel Vetter
2019-01-22 13:42 ` [igt-dev] [PATCH i-g-t 6/7] automake: Ditch all EXTRA_DIST directives Daniel Vetter
2019-01-22 13:42 ` [igt-dev] [PATCH i-g-t 7/7] automake: Remove VC4/V3D build support Daniel Vetter
2019-01-22 18:50 ` Eric Anholt
2019-01-23 11:38 ` Daniel Vetter
2019-01-23 11:54 ` Jani Nikula
2019-01-23 12:49 ` [igt-dev] [PATCH i-g-t] " Daniel Vetter
2019-01-22 14:32 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/7] automake: Drop gtkdoc build remnants Patchwork
2019-01-22 17:11 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2019-01-23 11:10 ` [igt-dev] [PATCH i-g-t 1/7] " Petri Latvala
2019-01-23 11:42 ` Daniel Vetter
2019-01-23 12:15 ` Petri Latvala
2019-01-29 10:11 ` Daniel Vetter [this message]
2019-01-23 13:19 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/7] automake: Drop gtkdoc build remnants (rev2) Patchwork
2019-01-23 15:32 ` [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=20190129101141.GQ3271@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=igt-dev@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.