From: Thomas Zimmermann <tzimmermann@suse.de>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: javierm@redhat.com, deller@gmx.de, airlied@gmail.com,
dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org
Subject: Re: [PATCH v2 0/3] video: Simplify Kconfig options
Date: Tue, 23 Jan 2024 10:23:49 +0100 [thread overview]
Message-ID: <2e7de6c3-43a1-4511-b910-b25eb80a5bfe@suse.de> (raw)
In-Reply-To: <Zaky46R04of5mPRX@phenom.ffwll.local>
[-- Attachment #1.1: Type: text/plain, Size: 2204 bytes --]
Hi
Am 18.01.24 um 15:17 schrieb Daniel Vetter:
> On Thu, Jan 18, 2024 at 10:05:25AM +0100, Thomas Zimmermann wrote:
>> Replace CONFIG_VIDEO_CMDLINE and CONFIG_VIDEO_NOMODESET by the single
>> option CONFIG_VIDEO. Select the latter for DRM or fbdev. Both original
>> options used to be selected in most cases, so this change simplifies
>> the Kconfig rules.
>>
>> Since commit ca6c080eef42 ("arch/parisc: Detect primary video device
>> from device instance") architecture helpers for fbdev do not longer
>> require fbdev in their implementation and could be used for non-fbdev
>> code as well. Eventually guarding them with CONFIG_VIDEO will make
>> them available to any subsystem.
>>
>> v2:
>> * support CONFIG_FB_CORE=m via IS_ENABLED() (kernel test robot)
>>
>> Thomas Zimmermann (3):
>> video/cmdline: Introduce CONFIG_VIDEO for video= parameter
>> video/cmdline: Hide __video_get_options() behind CONFIG_FB_CORE
>> video/nomodeset: Select nomodeset= parameter with CONFIG_VIDEO
>
> On the series:
>
> Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Pushed to drm-misc-next. Thanks a lot. FYI there's a conflict with
commit 689237ab37c5 ("fbdev/intelfb: Remove driver").
Best regards
Thomas
>
>>
>> drivers/gpu/drm/Kconfig | 3 +--
>> drivers/staging/sm750fb/Kconfig | 1 -
>> drivers/video/Kconfig | 5 +----
>> drivers/video/Makefile | 3 +--
>> drivers/video/cmdline.c | 2 ++
>> drivers/video/fbdev/Kconfig | 37 -------------------------------
>> drivers/video/fbdev/core/Kconfig | 2 +-
>> drivers/video/fbdev/core/fbmem.c | 2 --
>> drivers/video/fbdev/geode/Kconfig | 3 ---
>> include/linux/fb.h | 7 ------
>> include/video/cmdline.h | 8 ++-----
>> 11 files changed, 8 insertions(+), 65 deletions(-)
>>
>>
>> base-commit: 05b317e8457c8e2bd1a797c9440ec07b7f341584
>> --
>> 2.43.0
>>
>
--
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)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
prev parent reply other threads:[~2024-01-23 9:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-18 9:05 [PATCH v2 0/3] video: Simplify Kconfig options Thomas Zimmermann
2024-01-18 9:05 ` [PATCH v2 1/3] video/cmdline: Introduce CONFIG_VIDEO for video= parameter Thomas Zimmermann
2024-01-18 9:05 ` [PATCH v2 2/3] video/cmdline: Hide __video_get_options() behind CONFIG_FB_CORE Thomas Zimmermann
2024-01-18 9:05 ` [PATCH v2 3/3] video/nomodeset: Select nomodeset= parameter with CONFIG_VIDEO Thomas Zimmermann
2024-01-18 14:17 ` [PATCH v2 0/3] video: Simplify Kconfig options Daniel Vetter
2024-01-23 9:23 ` Thomas Zimmermann [this message]
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=2e7de6c3-43a1-4511-b910-b25eb80a5bfe@suse.de \
--to=tzimmermann@suse.de \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).