[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <ZvoClJ8lqwH0Bdbj@google.com>
Date: Mon, 30 Sep 2024 01:44:52 +0000
From: Tzung-Bi Shih <tzungbi@...nel.org>
To: Javier Martinez Canillas <javierm@...hat.com>
Cc: linux-kernel@...r.kernel.org, Brian Norris <briannorris@...omium.org>,
dri-devel@...ts.freedesktop.org, Borislav Petkov <bp@...en8.de>,
Julius Werner <jwerner@...omium.org>,
Thomas Zimmermann <tzimmermann@...e.de>,
chrome-platform@...ts.linux.dev, intel-gfx@...ts.freedesktop.org,
Hugues Bruant <hugues.bruant@...il.com>,
Alex Deucher <alexander.deucher@....com>,
Dan Carpenter <dan.carpenter@...aro.org>,
Helge Deller <deller@....de>, Jani Nikula <jani.nikula@...el.com>
Subject: Re: [PATCH v4 0/2] firmware: Avoid coreboot and sysfb to register a
pdev for same framebuffer
On Mon, Sep 16, 2024 at 01:00:24PM +0200, Javier Martinez Canillas wrote:
> This is v4 of a fix to prevent both coreboot and sysfb drivers to register
> a platform device to setup a system framebuffer. It has been converted to
> a series since contains changes for both drivers, to prevent build issues
> on architectures that don't define a global struct screen_info.
>
> Patch #1 adds a sysfb_handles_screen_info() helper that can be used by
> drivers to check whether sysfb can use the data set in screen_info or not.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux.git for-firmware-next
[1/2] firmware: sysfb: Add a sysfb_handles_screen_info() helper function
commit: 6074e905023d09f64f2c896f475820a5623deb2c
[2/2] firmware: coreboot: Don't register a pdev if screen_info data is present
commit: 67f488dff17e535ac3a8a52b47ff1363d8134983
Thanks!
Powered by blists - more mailing lists