[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20191206122750.4z7vlr52wthxtucf@sirius.home.kraxel.org>
Date: Fri, 6 Dec 2019 13:27:50 +0100
From: Gerd Hoffmann <kraxel@...hat.com>
To: Daniel Vetter <daniel@...ll.ch>
Cc: dri-devel <dri-devel@...ts.freedesktop.org>,
Rob Herring <robh@...nel.org>,
intel-gfx <intel-gfx@...ts.freedesktop.org>,
Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
Maxime Ripard <mripard@...nel.org>,
David Airlie <airlied@...ux.ie>,
Christian Koenig <christian.koenig@....com>,
Huang Rui <ray.huang@....com>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [Intel-gfx] [PATCH v3 1/2] drm: call drm_gem_object_funcs.mmap
with fake offset
On Fri, Dec 06, 2019 at 12:10:15PM +0100, Daniel Vetter wrote:
> On Fri, Dec 6, 2019 at 11:22 AM Gerd Hoffmann <kraxel@...hat.com> wrote:
> >
> > > Guess you kicked CI? Just got CI mails, now reporting success, without
> > > doing anything. So I'll go push v3 to misc-next.
> >
> > Oops, spoke too soon. Next mail arrived. Fi.CI.BAT works, but
> > Fi.CI.IGT still fails.
> >
> > Where is the "test again" button? Can I re-run the tests on v2? Right
> > now I tend to commit v2 to have a fix committed, then go figure why v3
> > fails ...
>
> Top of the mail you get from CI is the link to the patchwork series.
> That contains all the same info like in the mail, plus the coveted
> button. If failures look similar then yes I guess v3 is somehow
> broken. But I've looked, looks like just 2x unrelated noise and you
> being unlucky, so imo totally fine to push v3. I'll give CI folks a
> heads-up (best done over irc usually).
Ok. Pushed now.
cheers,
Gerd
Powered by blists - more mailing lists