mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Javier Martinez Canillas <javierm@redhat.com>
To: Johannes Stezenbach <js@sig21.net>
Cc: linux-kernel@vger.kernel.org, "Daniel Vetter" <daniel@ffwll.ch>,
	"Ville Syrjälä" <ville.syrjala@linux.intel.com>,
	"David Airlie" <airlied@linux.ie>,
	"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
	"Maxime Ripard" <mripard@kernel.org>,
	"Thomas Zimmermann" <tzimmermann@suse.de>,
	dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v2] Revert "drm/fb-helper: improve DRM fbdev emulation device names"
Date: Thu, 9 Dec 2021 13:27:59 +0100	[thread overview]
Message-ID: <408dd9d0-22bb-f5de-b578-9fd20df89a98@redhat.com> (raw)
In-Reply-To: <Yath6T5ET17GbkI7@sig21.net>

Hello Johannes,

Sorry for the late response. I was on holidays for a week and just came back.

On 12/4/21 13:41, Johannes Stezenbach wrote:
> Hi,
> 
> On Wed, Oct 20, 2021 at 06:57:40PM +0200, Javier Martinez Canillas wrote:
>> This reverts commit b3484d2b03e4c940a9598aa841a52d69729c582a.
>>
>> That change attempted to improve the DRM drivers fbdev emulation device
>> names to avoid having confusing names like "simpledrmdrmfb" in /proc/fb.
>>
>> But unfortunately, there are user-space programs such as pm-utils that
>> match against the fbdev names and so broke after the mentioned commit.
>>
>> Since the names in /proc/fb are used by tools that consider it an uAPI,
>> let's restore the old names even when this lead to silly names like the
>> one mentioned above.
> 
> I would like to ask about the fate of this patch. It doesn't
> seem to have been picked up by anyone, does it?
>

Thanks for the reminder. I've just pushed this to the drm-misc-fixes branch.
 
> 
> Thanks,
> Johannes
> 
Best regards,
-- 
Javier Martinez Canillas
Linux Engineering
Red Hat


      reply	other threads:[~2021-12-09 12:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-20 16:57 Javier Martinez Canillas
2021-12-04 12:41 ` Johannes Stezenbach
2021-12-09 12:27   ` Javier Martinez Canillas [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=408dd9d0-22bb-f5de-b578-9fd20df89a98@redhat.com \
    --to=javierm@redhat.com \
    --cc=airlied@linux.ie \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=js@sig21.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=tzimmermann@suse.de \
    --cc=ville.syrjala@linux.intel.com \
    /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

all inboxes | Powered by JetHome®