From: Thomas Zimmermann <tzimmermann@suse.de>
To: Helge Deller <deller@gmx.de>, arnd@arndb.de, javierm@redhat.com
Cc: dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org
Subject: Re: [PATCH 2/2] video: Make global edid_info depend on CONFIG_FIRMWARE_EDID
Date: Tue, 3 Jun 2025 18:18:41 +0200 [thread overview]
Message-ID: <cd3e5ccb-3bdb-4a2b-a67e-3e97f06df433@suse.de> (raw)
In-Reply-To: <4e3f9936-0d0f-4e93-888f-738daa345905@gmx.de>
Hi
Am 03.06.25 um 18:08 schrieb Helge Deller:
> On 6/2/25 09:51, Thomas Zimmermann wrote:
>> Protect global edid_info behind CONFIG_FIRMWARE_EDID and remove
>> the config tests for CONFIG_X86. Makes edid_info available iff
>> its option has been enabled.
>>
>> Signed-off-by: Thomas Zimmermann <tzimmermann@suse.de>
>> ---
>> arch/x86/kernel/setup.c | 4 ++++
>> drivers/gpu/drm/sysfb/efidrm.c | 2 +-
>> drivers/gpu/drm/sysfb/vesadrm.c | 2 +-
>> include/video/edid.h | 3 ++-
>> 4 files changed, 8 insertions(+), 3 deletions(-)
>
> Reviewed-by: Helge Deller <deller@gmx.de>
Thanks for reviewing. I'd like to merge the series via drm-misc for some
other patches I have for DRM. Ok?
Best regards
Thomas
--
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Frankenstrasse 146, 90461 Nuernberg, Germany
GF: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman
HRB 36809 (AG Nuernberg)
next prev parent reply other threads:[~2025-06-03 16:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-02 7:51 [PATCH 0/2] video: Make edid_info generally available in x86 Thomas Zimmermann
2025-06-02 7:51 ` [PATCH 1/2] video: Make CONFIG_FIRMWARE_EDID generally available Thomas Zimmermann
2025-06-03 16:08 ` Helge Deller
2025-06-02 7:51 ` [PATCH 2/2] video: Make global edid_info depend on CONFIG_FIRMWARE_EDID Thomas Zimmermann
2025-06-03 16:08 ` Helge Deller
2025-06-03 16:18 ` Thomas Zimmermann [this message]
2025-06-03 16:42 ` Helge Deller
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=cd3e5ccb-3bdb-4a2b-a67e-3e97f06df433@suse.de \
--to=tzimmermann@suse.de \
--cc=arnd@arndb.de \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=javierm@redhat.com \
--cc=linux-fbdev@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).