Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Fri, 6 Dec 2019 11:07:24 +0100
From:   Gerd Hoffmann <kraxel@redhat.com>
To:     dri-devel@lists.freedesktop.org, robh@kernel.org,
        intel-gfx@lists.freedesktop.org,
        Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
        Maxime Ripard <mripard@kernel.org>,
        David Airlie <airlied@linux.ie>,
        Christian Koenig <christian.koenig@amd.com>,
        Huang Rui <ray.huang@amd.com>,
        open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 1/2] drm: call drm_gem_object_funcs.mmap with fake
 offset
Message-ID: <20191206100724.ukzdyaym3ltcyfaa@sirius.home.kraxel.org>
References: <20191127092523.5620-1-kraxel@redhat.com>
 <20191127092523.5620-2-kraxel@redhat.com>
 <20191128113930.yhckvneecpvfhlls@sirius.home.kraxel.org>
 <20191205221523.GN624164@phenom.ffwll.local>
MIME-Version: 1.0
In-Reply-To: <20191205221523.GN624164@phenom.ffwll.local>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Thu, Dec 05, 2019 at 11:15:23PM +0100, Daniel Vetter wrote:
> On Thu, Nov 28, 2019 at 12:39:30PM +0100, Gerd Hoffmann wrote:
> > On Wed, Nov 27, 2019 at 10:25:22AM +0100, Gerd Hoffmann wrote:
> > > The fake offset is going to stay, so change the calling convention fo=
r
> > > drm_gem_object_funcs.mmap to include the fake offset.  Update all use=
rs
> > > accordingly.
> > >=20
> > > Note that this reverts 83b8a6f242ea ("drm/gem: Fix mmap fake offset
> > > handling for drm_gem_object_funcs.mmap") and on top then adds the fak=
e
> > > offset to  drm_gem_prime_mmap to make sure all paths leading to
> > > obj->funcs->mmap are consistent.
> > >=20
> > > v3: move fake-offset tweak in drm_gem_prime_mmap() so we have this co=
de
> > >     only once in the function (Rob Herring).
> >=20
> > Now this series fails in Intel CI.  Can't see why though.  The
> > difference between v2 and v3 is just the place where vma->vm_pgoff gets
> > updated, and no code between the v2 and v3 location touches vma ...
>=20
> Looks like unrelated flukes, this happens occasionally. If you're paranoi=
d
> hit the retest button on patchwork to double-check.
> -Daniel

Guess you kicked CI?  Just got CI mails, now reporting success, without
doing anything.  So I'll go push v3 to misc-next.

cheers,
  Gerd