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;
MIME-Version: 1.0
References: <CGME20190314114511epcas2p2a9669714177b00989bd3195300f7d3a6@epcas2p2.samsung.com>
 <20190314114500.8336-1-kraxel@redhat.com> <33cf37dc-8456-0316-0b48-fca7c92caa28@samsung.com>
In-Reply-To: <33cf37dc-8456-0316-0b48-fca7c92caa28@samsung.com>
From:   Daniel Vetter <daniel.vetter@ffwll.ch>
Date:   Tue, 2 Apr 2019 14:09:45 +0200
Message-ID: <CAKMK7uEs+OaoiEmd9Dp6K_v5Pz4pf197DP8KFkvhNMYXv9tYxA@mail.gmail.com>
Subject: Re: [PATCH] fbdev: list all pci memory bars as conflicting apertures
To:     Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Cc:     Gerd Hoffmann <kraxel@redhat.com>,
        dri-devel <dri-devel@lists.freedesktop.org>,
        "open list:FRAMEBUFFER LAYER" <linux-fbdev@vger.kernel.org>,
        open list <linux-kernel@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Mon, Apr 1, 2019 at 4:00 PM Bartlomiej Zolnierkiewicz
<b.zolnierkie@samsung.com> wrote:
>
>
> On 03/14/2019 12:45 PM, Gerd Hoffmann wrote:
> > Simply add all pci memory bars to struct apertures_struct in
> > remove_conflicting_pci_framebuffers(), without depending on the
> > res_id parameter.
> >
> > The plan is to drop the res_id parameter later on.  For now keep the
> > parameter, use it for sanity-checking and warn on inconsistencies.
> >
> > Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
> > Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
>
> Patch queued for v5.2, thanks.

Might be good to also stuff this into drm (double merge or topic
branch, whatever you prefer), since that's where all the users are.
Gerd also has some follow-up patches to apply on top of this one iirc.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch