From: Jani Nikula <jani.nikula@linux.intel.com>
To: Javier Martinez Canillas <javierm@redhat.com>,
Thomas Zimmermann <tzimmermann@suse.de>,
linux-kernel@vger.kernel.org
Cc: "Pan, Xinhui" <Xinhui.Pan@amd.com>,
"Pekka Paalanen" <pekka.paalanen@collabora.com>,
"Hans de Goede" <hdegoede@redhat.com>,
"David Airlie" <airlied@linux.ie>,
"Daniel Vetter" <daniel.vetter@ffwll.ch>,
dri-devel@lists.freedesktop.org,
"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
amd-gfx@lists.freedesktop.org,
"Gurchetan Singh" <gurchetansingh@chromium.org>,
"Ben Skeggs" <bskeggs@redhat.com>,
"VMware Graphics" <linux-graphics-maintainer@vmware.com>,
"Gerd Hoffmann" <kraxel@redhat.com>,
spice-devel@lists.freedesktop.org, nouveau@lists.freedesktop.org,
"Alex Deucher" <alexander.deucher@amd.com>,
"Dave Airlie" <airlied@redhat.com>,
"Christian König" <christian.koenig@amd.com>,
virtualization@lists.linux-foundation.org,
intel-gfx@lists.freedesktop.org,
"Michel Dänzer" <michel@daenzer.net>,
"Peter Robinson" <pbrobinson@gmail.com>
Subject: Re: [PATCH v2 1/2] drm: Add a drm_drv_enabled() to check if drivers should be enabled
Date: Fri, 05 Nov 2021 12:04:48 +0200 [thread overview]
Message-ID: <877ddmapfj.fsf@intel.com> (raw)
In-Reply-To: <38dbcc8f-2f95-6846-537f-9b85468bfa87@redhat.com>
On Fri, 05 Nov 2021, Javier Martinez Canillas <javierm@redhat.com> wrote:
> Hello Thomas,
>
> On 11/5/21 09:43, Thomas Zimmermann wrote:
>> Hi
>>
>> Am 04.11.21 um 21:09 schrieb Javier Martinez Canillas:
>>> Hello Jani,
>>>
>>> On 11/4/21 20:57, Jani Nikula wrote:
>>>> On Thu, 04 Nov 2021, Javier Martinez Canillas <javierm@redhat.com> wrote:
>>>>> +/**
>>>>> + * drm_drv_enabled - Checks if a DRM driver can be enabled
>>>>> + * @driver: DRM driver to check
>>>>> + *
>>>>> + * Checks whether a DRM driver can be enabled or not. This may be the case
>>>>> + * if the "nomodeset" kernel command line parameter is used.
>>>>> + *
>>>>> + * Return: 0 on success or a negative error code on failure.
>>>>> + */
>>>>> +int drm_drv_enabled(const struct drm_driver *driver)
>>
>> Jani mentioned that i915 absolutely wants this to run from the
>> module_init function. Best is to drop the parameter.
>>
>
> Ok. I now wonder though how much value would add this function since
> it will just be a wrapper around the nomodeset check.
>
> We talked about adding a new DRIVER_GENERIC feature flag and check for
> this, but as danvet mentioned that is not really needed. We just need
> to avoid testing for nomodeset in the simpledrm driver.
>
> Do you envision other condition that could be added later to disable a
> DRM driver ? Or do you think that just from a code readability point of
> view makes worth it ?
Taking a step back for perspective.
I think there's broad consensus in moving the parameter to drm, naming
the check function to drm_something_something(), and breaking the ties
to CONFIG_VGA_CONSOLE. I appreciate the work you're doing to that
effect.
I think everything beyond that is still a bit vague and/or
contentious. So how about making the first 2-3 patches just that?
Something we can all agree on, makes good progress, improves the kernel,
and gives us something to build on?
BR,
Jani.
>
>>>>> +{
>>>>> + if (vgacon_text_force()) {
>>>>> + DRM_INFO("%s driver is disabled\n", driver->name);
>>>>> + return -ENODEV;
>>>>> + }
>>
>> If we run this from within a module_init function, we'd get plenty of
>> these warnings if drivers are compiled into the kernel. Maybe simply
>> remove the message. There's already a warning printed by the nomodeset
>> handler.
>>
>
> Indeed. I'll just drop it.
>
>>>>> +
>>>>> + return 0;
>>>>> +}
>>>>> +EXPORT_SYMBOL(drm_drv_enabled);
>>>>
>>>> The name implies a bool return, but it's not.
>>>>
>>>> if (drm_drv_enabled(...)) {
>>>> /* surprise, it's disabled! */
>>>> }
>>>>
>>>
>>> It used to return a bool in v2 but Thomas suggested an int instead to
>>> have consistency on the errno code that was returned by the callers.
>>>
>>> I should probably name that function differently to avoid confusion.
>>
>> Yes, please.
>>
>
> drm_driver_check() maybe ?
>
> Best regards,
--
Jani Nikula, Intel Open Source Graphics Center
WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Javier Martinez Canillas <javierm@redhat.com>,
Thomas Zimmermann <tzimmermann@suse.de>,
linux-kernel@vger.kernel.org
Cc: "Pan, Xinhui" <Xinhui.Pan@amd.com>,
"Pekka Paalanen" <pekka.paalanen@collabora.com>,
"David Airlie" <airlied@linux.ie>,
"Daniel Vetter" <daniel.vetter@ffwll.ch>,
dri-devel@lists.freedesktop.org, amd-gfx@lists.freedesktop.org,
"Gurchetan Singh" <gurchetansingh@chromium.org>,
"Ben Skeggs" <bskeggs@redhat.com>,
"VMware Graphics" <linux-graphics-maintainer@vmware.com>,
"Gerd Hoffmann" <kraxel@redhat.com>,
spice-devel@lists.freedesktop.org, nouveau@lists.freedesktop.org,
"Alex Deucher" <alexander.deucher@amd.com>,
"Dave Airlie" <airlied@redhat.com>,
"Christian König" <christian.koenig@amd.com>,
virtualization@lists.linux-foundation.org,
intel-gfx@lists.freedesktop.org,
"Michel Dänzer" <michel@daenzer.net>,
"Peter Robinson" <pbrobinson@gmail.com>
Subject: Re: [Intel-gfx] [PATCH v2 1/2] drm: Add a drm_drv_enabled() to check if drivers should be enabled
Date: Fri, 05 Nov 2021 12:04:48 +0200 [thread overview]
Message-ID: <877ddmapfj.fsf@intel.com> (raw)
In-Reply-To: <38dbcc8f-2f95-6846-537f-9b85468bfa87@redhat.com>
On Fri, 05 Nov 2021, Javier Martinez Canillas <javierm@redhat.com> wrote:
> Hello Thomas,
>
> On 11/5/21 09:43, Thomas Zimmermann wrote:
>> Hi
>>
>> Am 04.11.21 um 21:09 schrieb Javier Martinez Canillas:
>>> Hello Jani,
>>>
>>> On 11/4/21 20:57, Jani Nikula wrote:
>>>> On Thu, 04 Nov 2021, Javier Martinez Canillas <javierm@redhat.com> wrote:
>>>>> +/**
>>>>> + * drm_drv_enabled - Checks if a DRM driver can be enabled
>>>>> + * @driver: DRM driver to check
>>>>> + *
>>>>> + * Checks whether a DRM driver can be enabled or not. This may be the case
>>>>> + * if the "nomodeset" kernel command line parameter is used.
>>>>> + *
>>>>> + * Return: 0 on success or a negative error code on failure.
>>>>> + */
>>>>> +int drm_drv_enabled(const struct drm_driver *driver)
>>
>> Jani mentioned that i915 absolutely wants this to run from the
>> module_init function. Best is to drop the parameter.
>>
>
> Ok. I now wonder though how much value would add this function since
> it will just be a wrapper around the nomodeset check.
>
> We talked about adding a new DRIVER_GENERIC feature flag and check for
> this, but as danvet mentioned that is not really needed. We just need
> to avoid testing for nomodeset in the simpledrm driver.
>
> Do you envision other condition that could be added later to disable a
> DRM driver ? Or do you think that just from a code readability point of
> view makes worth it ?
Taking a step back for perspective.
I think there's broad consensus in moving the parameter to drm, naming
the check function to drm_something_something(), and breaking the ties
to CONFIG_VGA_CONSOLE. I appreciate the work you're doing to that
effect.
I think everything beyond that is still a bit vague and/or
contentious. So how about making the first 2-3 patches just that?
Something we can all agree on, makes good progress, improves the kernel,
and gives us something to build on?
BR,
Jani.
>
>>>>> +{
>>>>> + if (vgacon_text_force()) {
>>>>> + DRM_INFO("%s driver is disabled\n", driver->name);
>>>>> + return -ENODEV;
>>>>> + }
>>
>> If we run this from within a module_init function, we'd get plenty of
>> these warnings if drivers are compiled into the kernel. Maybe simply
>> remove the message. There's already a warning printed by the nomodeset
>> handler.
>>
>
> Indeed. I'll just drop it.
>
>>>>> +
>>>>> + return 0;
>>>>> +}
>>>>> +EXPORT_SYMBOL(drm_drv_enabled);
>>>>
>>>> The name implies a bool return, but it's not.
>>>>
>>>> if (drm_drv_enabled(...)) {
>>>> /* surprise, it's disabled! */
>>>> }
>>>>
>>>
>>> It used to return a bool in v2 but Thomas suggested an int instead to
>>> have consistency on the errno code that was returned by the callers.
>>>
>>> I should probably name that function differently to avoid confusion.
>>
>> Yes, please.
>>
>
> drm_driver_check() maybe ?
>
> Best regards,
--
Jani Nikula, Intel Open Source Graphics Center
WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Javier Martinez Canillas <javierm@redhat.com>,
Thomas Zimmermann <tzimmermann@suse.de>,
linux-kernel@vger.kernel.org
Cc: "Pan, Xinhui" <Xinhui.Pan@amd.com>,
"Pekka Paalanen" <pekka.paalanen@collabora.com>,
"Hans de Goede" <hdegoede@redhat.com>,
"David Airlie" <airlied@linux.ie>,
dri-devel@lists.freedesktop.org,
"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
amd-gfx@lists.freedesktop.org,
"Gurchetan Singh" <gurchetansingh@chromium.org>,
"Ben Skeggs" <bskeggs@redhat.com>,
"VMware Graphics" <linux-graphics-maintainer@vmware.com>,
"Gerd Hoffmann" <kraxel@redhat.com>,
spice-devel@lists.freedesktop.org, nouveau@lists.freedesktop.org,
"Alex Deucher" <alexander.deucher@amd.com>,
"Dave Airlie" <airlied@redhat.com>,
"Christian König" <christian.koenig@amd.com>,
virtualization@lists.linux-foundation.org,
intel-gfx@lists.freedesktop.org,
"Michel Dänzer" <michel@daenzer.net>,
"Peter Robinson" <pbrobinson@gmail.com>
Subject: Re: [Nouveau] [PATCH v2 1/2] drm: Add a drm_drv_enabled() to check if drivers should be enabled
Date: Fri, 05 Nov 2021 12:04:48 +0200 [thread overview]
Message-ID: <877ddmapfj.fsf@intel.com> (raw)
In-Reply-To: <38dbcc8f-2f95-6846-537f-9b85468bfa87@redhat.com>
On Fri, 05 Nov 2021, Javier Martinez Canillas <javierm@redhat.com> wrote:
> Hello Thomas,
>
> On 11/5/21 09:43, Thomas Zimmermann wrote:
>> Hi
>>
>> Am 04.11.21 um 21:09 schrieb Javier Martinez Canillas:
>>> Hello Jani,
>>>
>>> On 11/4/21 20:57, Jani Nikula wrote:
>>>> On Thu, 04 Nov 2021, Javier Martinez Canillas <javierm@redhat.com> wrote:
>>>>> +/**
>>>>> + * drm_drv_enabled - Checks if a DRM driver can be enabled
>>>>> + * @driver: DRM driver to check
>>>>> + *
>>>>> + * Checks whether a DRM driver can be enabled or not. This may be the case
>>>>> + * if the "nomodeset" kernel command line parameter is used.
>>>>> + *
>>>>> + * Return: 0 on success or a negative error code on failure.
>>>>> + */
>>>>> +int drm_drv_enabled(const struct drm_driver *driver)
>>
>> Jani mentioned that i915 absolutely wants this to run from the
>> module_init function. Best is to drop the parameter.
>>
>
> Ok. I now wonder though how much value would add this function since
> it will just be a wrapper around the nomodeset check.
>
> We talked about adding a new DRIVER_GENERIC feature flag and check for
> this, but as danvet mentioned that is not really needed. We just need
> to avoid testing for nomodeset in the simpledrm driver.
>
> Do you envision other condition that could be added later to disable a
> DRM driver ? Or do you think that just from a code readability point of
> view makes worth it ?
Taking a step back for perspective.
I think there's broad consensus in moving the parameter to drm, naming
the check function to drm_something_something(), and breaking the ties
to CONFIG_VGA_CONSOLE. I appreciate the work you're doing to that
effect.
I think everything beyond that is still a bit vague and/or
contentious. So how about making the first 2-3 patches just that?
Something we can all agree on, makes good progress, improves the kernel,
and gives us something to build on?
BR,
Jani.
>
>>>>> +{
>>>>> + if (vgacon_text_force()) {
>>>>> + DRM_INFO("%s driver is disabled\n", driver->name);
>>>>> + return -ENODEV;
>>>>> + }
>>
>> If we run this from within a module_init function, we'd get plenty of
>> these warnings if drivers are compiled into the kernel. Maybe simply
>> remove the message. There's already a warning printed by the nomodeset
>> handler.
>>
>
> Indeed. I'll just drop it.
>
>>>>> +
>>>>> + return 0;
>>>>> +}
>>>>> +EXPORT_SYMBOL(drm_drv_enabled);
>>>>
>>>> The name implies a bool return, but it's not.
>>>>
>>>> if (drm_drv_enabled(...)) {
>>>> /* surprise, it's disabled! */
>>>> }
>>>>
>>>
>>> It used to return a bool in v2 but Thomas suggested an int instead to
>>> have consistency on the errno code that was returned by the callers.
>>>
>>> I should probably name that function differently to avoid confusion.
>>
>> Yes, please.
>>
>
> drm_driver_check() maybe ?
>
> Best regards,
--
Jani Nikula, Intel Open Source Graphics Center
WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Javier Martinez Canillas <javierm@redhat.com>,
Thomas Zimmermann <tzimmermann@suse.de>,
linux-kernel@vger.kernel.org
Cc: "Pan, Xinhui" <Xinhui.Pan@amd.com>,
"Pekka Paalanen" <pekka.paalanen@collabora.com>,
"Hans de Goede" <hdegoede@redhat.com>,
"David Airlie" <airlied@linux.ie>,
"Daniel Vetter" <daniel.vetter@ffwll.ch>,
dri-devel@lists.freedesktop.org,
"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
amd-gfx@lists.freedesktop.org,
"Gurchetan Singh" <gurchetansingh@chromium.org>,
"Ben Skeggs" <bskeggs@redhat.com>,
"VMware Graphics" <linux-graphics-maintainer@vmware.com>,
spice-devel@lists.freedesktop.org, nouveau@lists.freedesktop.org,
"Alex Deucher" <alexander.deucher@amd.com>,
"Dave Airlie" <airlied@redhat.com>,
"Christian König" <christian.koenig@amd.com>,
virtualization@lists.linux-foundation.org,
intel-gfx@lists.freedesktop.org,
"Michel Dänzer" <michel@daenzer.net>,
"Peter Robinson" <pbrobinson@gmail.com>
Subject: Re: [PATCH v2 1/2] drm: Add a drm_drv_enabled() to check if drivers should be enabled
Date: Fri, 05 Nov 2021 12:04:48 +0200 [thread overview]
Message-ID: <877ddmapfj.fsf@intel.com> (raw)
In-Reply-To: <38dbcc8f-2f95-6846-537f-9b85468bfa87@redhat.com>
On Fri, 05 Nov 2021, Javier Martinez Canillas <javierm@redhat.com> wrote:
> Hello Thomas,
>
> On 11/5/21 09:43, Thomas Zimmermann wrote:
>> Hi
>>
>> Am 04.11.21 um 21:09 schrieb Javier Martinez Canillas:
>>> Hello Jani,
>>>
>>> On 11/4/21 20:57, Jani Nikula wrote:
>>>> On Thu, 04 Nov 2021, Javier Martinez Canillas <javierm@redhat.com> wrote:
>>>>> +/**
>>>>> + * drm_drv_enabled - Checks if a DRM driver can be enabled
>>>>> + * @driver: DRM driver to check
>>>>> + *
>>>>> + * Checks whether a DRM driver can be enabled or not. This may be the case
>>>>> + * if the "nomodeset" kernel command line parameter is used.
>>>>> + *
>>>>> + * Return: 0 on success or a negative error code on failure.
>>>>> + */
>>>>> +int drm_drv_enabled(const struct drm_driver *driver)
>>
>> Jani mentioned that i915 absolutely wants this to run from the
>> module_init function. Best is to drop the parameter.
>>
>
> Ok. I now wonder though how much value would add this function since
> it will just be a wrapper around the nomodeset check.
>
> We talked about adding a new DRIVER_GENERIC feature flag and check for
> this, but as danvet mentioned that is not really needed. We just need
> to avoid testing for nomodeset in the simpledrm driver.
>
> Do you envision other condition that could be added later to disable a
> DRM driver ? Or do you think that just from a code readability point of
> view makes worth it ?
Taking a step back for perspective.
I think there's broad consensus in moving the parameter to drm, naming
the check function to drm_something_something(), and breaking the ties
to CONFIG_VGA_CONSOLE. I appreciate the work you're doing to that
effect.
I think everything beyond that is still a bit vague and/or
contentious. So how about making the first 2-3 patches just that?
Something we can all agree on, makes good progress, improves the kernel,
and gives us something to build on?
BR,
Jani.
>
>>>>> +{
>>>>> + if (vgacon_text_force()) {
>>>>> + DRM_INFO("%s driver is disabled\n", driver->name);
>>>>> + return -ENODEV;
>>>>> + }
>>
>> If we run this from within a module_init function, we'd get plenty of
>> these warnings if drivers are compiled into the kernel. Maybe simply
>> remove the message. There's already a warning printed by the nomodeset
>> handler.
>>
>
> Indeed. I'll just drop it.
>
>>>>> +
>>>>> + return 0;
>>>>> +}
>>>>> +EXPORT_SYMBOL(drm_drv_enabled);
>>>>
>>>> The name implies a bool return, but it's not.
>>>>
>>>> if (drm_drv_enabled(...)) {
>>>> /* surprise, it's disabled! */
>>>> }
>>>>
>>>
>>> It used to return a bool in v2 but Thomas suggested an int instead to
>>> have consistency on the errno code that was returned by the callers.
>>>
>>> I should probably name that function differently to avoid confusion.
>>
>> Yes, please.
>>
>
> drm_driver_check() maybe ?
>
> Best regards,
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Javier Martinez Canillas <javierm@redhat.com>,
Thomas Zimmermann <tzimmermann@suse.de>,
linux-kernel@vger.kernel.org
Cc: "David Airlie" <airlied@linux.ie>,
"Daniel Vetter" <daniel.vetter@ffwll.ch>,
dri-devel@lists.freedesktop.org,
"Gurchetan Singh" <gurchetansingh@chromium.org>,
"Gerd Hoffmann" <kraxel@redhat.com>,
amd-gfx@lists.freedesktop.org,
"VMware Graphics" <linux-graphics-maintainer@vmware.com>,
"Peter Robinson" <pbrobinson@gmail.com>,
nouveau@lists.freedesktop.org, "Dave Airlie" <airlied@redhat.com>,
"Ben Skeggs" <bskeggs@redhat.com>,
"Michel Dänzer" <michel@daenzer.net>,
"Hans de Goede" <hdegoede@redhat.com>,
"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
virtualization@lists.linux-foundation.org,
"Pekka Paalanen" <pekka.paalanen@collabora.com>,
"Pan, Xinhui" <Xinhui.Pan@amd.com>,
spice-devel@lists.freedesktop.org,
"Alex Deucher" <alexander.deucher@amd.com>,
intel-gfx@lists.freedesktop.org,
"Christian König" <christian.koenig@amd.com>
Subject: Re: [PATCH v2 1/2] drm: Add a drm_drv_enabled() to check if drivers should be enabled
Date: Fri, 05 Nov 2021 12:04:48 +0200 [thread overview]
Message-ID: <877ddmapfj.fsf@intel.com> (raw)
In-Reply-To: <38dbcc8f-2f95-6846-537f-9b85468bfa87@redhat.com>
On Fri, 05 Nov 2021, Javier Martinez Canillas <javierm@redhat.com> wrote:
> Hello Thomas,
>
> On 11/5/21 09:43, Thomas Zimmermann wrote:
>> Hi
>>
>> Am 04.11.21 um 21:09 schrieb Javier Martinez Canillas:
>>> Hello Jani,
>>>
>>> On 11/4/21 20:57, Jani Nikula wrote:
>>>> On Thu, 04 Nov 2021, Javier Martinez Canillas <javierm@redhat.com> wrote:
>>>>> +/**
>>>>> + * drm_drv_enabled - Checks if a DRM driver can be enabled
>>>>> + * @driver: DRM driver to check
>>>>> + *
>>>>> + * Checks whether a DRM driver can be enabled or not. This may be the case
>>>>> + * if the "nomodeset" kernel command line parameter is used.
>>>>> + *
>>>>> + * Return: 0 on success or a negative error code on failure.
>>>>> + */
>>>>> +int drm_drv_enabled(const struct drm_driver *driver)
>>
>> Jani mentioned that i915 absolutely wants this to run from the
>> module_init function. Best is to drop the parameter.
>>
>
> Ok. I now wonder though how much value would add this function since
> it will just be a wrapper around the nomodeset check.
>
> We talked about adding a new DRIVER_GENERIC feature flag and check for
> this, but as danvet mentioned that is not really needed. We just need
> to avoid testing for nomodeset in the simpledrm driver.
>
> Do you envision other condition that could be added later to disable a
> DRM driver ? Or do you think that just from a code readability point of
> view makes worth it ?
Taking a step back for perspective.
I think there's broad consensus in moving the parameter to drm, naming
the check function to drm_something_something(), and breaking the ties
to CONFIG_VGA_CONSOLE. I appreciate the work you're doing to that
effect.
I think everything beyond that is still a bit vague and/or
contentious. So how about making the first 2-3 patches just that?
Something we can all agree on, makes good progress, improves the kernel,
and gives us something to build on?
BR,
Jani.
>
>>>>> +{
>>>>> + if (vgacon_text_force()) {
>>>>> + DRM_INFO("%s driver is disabled\n", driver->name);
>>>>> + return -ENODEV;
>>>>> + }
>>
>> If we run this from within a module_init function, we'd get plenty of
>> these warnings if drivers are compiled into the kernel. Maybe simply
>> remove the message. There's already a warning printed by the nomodeset
>> handler.
>>
>
> Indeed. I'll just drop it.
>
>>>>> +
>>>>> + return 0;
>>>>> +}
>>>>> +EXPORT_SYMBOL(drm_drv_enabled);
>>>>
>>>> The name implies a bool return, but it's not.
>>>>
>>>> if (drm_drv_enabled(...)) {
>>>> /* surprise, it's disabled! */
>>>> }
>>>>
>>>
>>> It used to return a bool in v2 but Thomas suggested an int instead to
>>> have consistency on the errno code that was returned by the callers.
>>>
>>> I should probably name that function differently to avoid confusion.
>>
>> Yes, please.
>>
>
> drm_driver_check() maybe ?
>
> Best regards,
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2021-11-05 10:05 UTC|newest]
Thread overview: 117+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-04 16:07 [PATCH v2 0/2] Cleanups for the nomodeset kernel command line parameter logic Javier Martinez Canillas
2021-11-04 16:07 ` Javier Martinez Canillas
2021-11-04 16:07 ` [Nouveau] " Javier Martinez Canillas
2021-11-04 16:07 ` Javier Martinez Canillas
2021-11-04 16:07 ` [Intel-gfx] " Javier Martinez Canillas
2021-11-04 16:07 ` [PATCH v2 1/2] drm: Add a drm_drv_enabled() to check if drivers should be enabled Javier Martinez Canillas
2021-11-04 16:07 ` Javier Martinez Canillas
2021-11-04 16:07 ` Javier Martinez Canillas
2021-11-04 16:07 ` [Nouveau] " Javier Martinez Canillas
2021-11-04 16:07 ` [Intel-gfx] " Javier Martinez Canillas
2021-11-04 16:24 ` Jani Nikula
2021-11-04 16:24 ` Jani Nikula
2021-11-04 16:24 ` Jani Nikula
2021-11-04 16:24 ` Jani Nikula
2021-11-04 16:24 ` [Nouveau] " Jani Nikula
2021-11-04 16:24 ` [Intel-gfx] " Jani Nikula
2021-11-04 16:44 ` Javier Martinez Canillas
2021-11-04 16:44 ` Javier Martinez Canillas
2021-11-04 16:44 ` Javier Martinez Canillas
2021-11-04 16:44 ` [Nouveau] " Javier Martinez Canillas
2021-11-04 16:44 ` [Intel-gfx] " Javier Martinez Canillas
2021-11-04 17:37 ` Sam Ravnborg
2021-11-04 17:37 ` Sam Ravnborg
2021-11-04 17:37 ` [Nouveau] " Sam Ravnborg
2021-11-04 17:37 ` [Intel-gfx] " Sam Ravnborg
2021-11-04 17:57 ` Jani Nikula
2021-11-04 17:57 ` Jani Nikula
2021-11-04 17:57 ` Jani Nikula
2021-11-04 17:57 ` [Nouveau] " Jani Nikula
2021-11-04 17:57 ` [Intel-gfx] " Jani Nikula
2021-11-04 18:20 ` Javier Martinez Canillas
2021-11-04 18:20 ` Javier Martinez Canillas
2021-11-04 18:20 ` [Nouveau] " Javier Martinez Canillas
2021-11-04 18:20 ` [Intel-gfx] " Javier Martinez Canillas
2021-11-04 19:28 ` Sam Ravnborg
2021-11-04 19:28 ` Sam Ravnborg
2021-11-04 19:28 ` Sam Ravnborg
2021-11-04 19:28 ` [Nouveau] " Sam Ravnborg
2021-11-04 19:28 ` [Intel-gfx] " Sam Ravnborg
2021-11-04 19:54 ` Jani Nikula
2021-11-04 19:54 ` Jani Nikula
2021-11-04 19:54 ` Jani Nikula
2021-11-04 19:54 ` [Nouveau] " Jani Nikula
2021-11-04 19:54 ` [Intel-gfx] " Jani Nikula
2021-11-04 19:57 ` Jani Nikula
2021-11-04 19:57 ` Jani Nikula
2021-11-04 19:57 ` Jani Nikula
2021-11-04 19:57 ` Jani Nikula
2021-11-04 19:57 ` [Nouveau] " Jani Nikula
2021-11-04 19:57 ` [Intel-gfx] " Jani Nikula
2021-11-04 20:09 ` Javier Martinez Canillas
2021-11-04 20:09 ` Javier Martinez Canillas
2021-11-04 20:09 ` Javier Martinez Canillas
2021-11-04 20:09 ` [Nouveau] " Javier Martinez Canillas
2021-11-04 20:09 ` [Intel-gfx] " Javier Martinez Canillas
2021-11-05 8:43 ` Thomas Zimmermann
2021-11-05 8:43 ` Thomas Zimmermann
2021-11-05 8:43 ` Thomas Zimmermann
2021-11-05 8:43 ` [Nouveau] " Thomas Zimmermann
2021-11-05 8:43 ` [Intel-gfx] " Thomas Zimmermann
2021-11-05 9:48 ` Javier Martinez Canillas
2021-11-05 9:48 ` Javier Martinez Canillas
2021-11-05 9:48 ` [Nouveau] " Javier Martinez Canillas
2021-11-05 9:48 ` [Intel-gfx] " Javier Martinez Canillas
2021-11-05 10:04 ` Jani Nikula [this message]
2021-11-05 10:04 ` Jani Nikula
2021-11-05 10:04 ` Jani Nikula
2021-11-05 10:04 ` [Nouveau] " Jani Nikula
2021-11-05 10:04 ` [Intel-gfx] " Jani Nikula
2021-11-05 12:00 ` Javier Martinez Canillas
2021-11-05 12:00 ` Javier Martinez Canillas
2021-11-05 12:00 ` [Nouveau] " Javier Martinez Canillas
2021-11-05 12:00 ` [Intel-gfx] " Javier Martinez Canillas
2021-11-05 13:00 ` Thomas Zimmermann
2021-11-05 13:00 ` Thomas Zimmermann
2021-11-05 13:00 ` Thomas Zimmermann
2021-11-05 13:00 ` [Nouveau] " Thomas Zimmermann
2021-11-05 13:00 ` [Intel-gfx] " Thomas Zimmermann
2021-11-05 10:15 ` Thomas Zimmermann
2021-11-05 10:15 ` Thomas Zimmermann
2021-11-05 10:15 ` Thomas Zimmermann
2021-11-05 10:15 ` [Nouveau] " Thomas Zimmermann
2021-11-05 10:15 ` [Intel-gfx] " Thomas Zimmermann
2021-11-04 16:07 ` [PATCH v2 2/2] drm: Move nomodeset kernel parameter to the DRM subsystem Javier Martinez Canillas
2021-11-04 16:07 ` Javier Martinez Canillas
2021-11-04 16:07 ` [Nouveau] " Javier Martinez Canillas
2021-11-04 16:07 ` Javier Martinez Canillas
2021-11-04 16:07 ` [Intel-gfx] " Javier Martinez Canillas
2021-11-05 9:00 ` Thomas Zimmermann
2021-11-05 9:00 ` Thomas Zimmermann
2021-11-05 9:00 ` Thomas Zimmermann
2021-11-05 9:00 ` [Nouveau] " Thomas Zimmermann
2021-11-05 9:00 ` Thomas Zimmermann
2021-11-05 9:00 ` [Intel-gfx] " Thomas Zimmermann
2021-11-05 9:22 ` Jani Nikula
2021-11-05 9:22 ` Jani Nikula
2021-11-05 9:22 ` Jani Nikula
2021-11-05 9:22 ` [Nouveau] " Jani Nikula
2021-11-05 9:22 ` Jani Nikula
2021-11-05 9:22 ` [Intel-gfx] " Jani Nikula
2021-11-05 9:39 ` Thomas Zimmermann
2021-11-05 9:39 ` Thomas Zimmermann
2021-11-05 9:39 ` Thomas Zimmermann
2021-11-05 9:39 ` [Nouveau] " Thomas Zimmermann
2021-11-05 9:39 ` Thomas Zimmermann
2021-11-05 9:39 ` [Intel-gfx] " Thomas Zimmermann
2021-11-05 9:58 ` Javier Martinez Canillas
2021-11-05 9:58 ` Javier Martinez Canillas
2021-11-05 9:58 ` [Nouveau] " Javier Martinez Canillas
2021-11-05 9:58 ` Javier Martinez Canillas
2021-11-05 9:58 ` [Intel-gfx] " Javier Martinez Canillas
2021-11-05 9:55 ` Javier Martinez Canillas
2021-11-05 9:55 ` Javier Martinez Canillas
2021-11-05 9:55 ` [Nouveau] " Javier Martinez Canillas
2021-11-05 9:55 ` Javier Martinez Canillas
2021-11-05 9:55 ` [Intel-gfx] " Javier Martinez Canillas
2021-11-04 19:50 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for Cleanups for the nomodeset kernel command line parameter logic (rev4) Patchwork
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=877ddmapfj.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=Xinhui.Pan@amd.com \
--cc=airlied@linux.ie \
--cc=airlied@redhat.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=bskeggs@redhat.com \
--cc=christian.koenig@amd.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=gurchetansingh@chromium.org \
--cc=hdegoede@redhat.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=javierm@redhat.com \
--cc=kraxel@redhat.com \
--cc=linux-graphics-maintainer@vmware.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michel@daenzer.net \
--cc=nouveau@lists.freedesktop.org \
--cc=pbrobinson@gmail.com \
--cc=pekka.paalanen@collabora.com \
--cc=rodrigo.vivi@intel.com \
--cc=spice-devel@lists.freedesktop.org \
--cc=tzimmermann@suse.de \
--cc=virtualization@lists.linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.