From: Javier Martinez Canillas <javierm@redhat.com>
To: Thomas Zimmermann <tzimmermann@suse.de>,
robh+dt@kernel.org, frowand.list@gmail.com, daniel@ffwll.ch,
deller@gmx.de, sam@ravnborg.org, linux@roeck-us.net,
mpe@ellerman.id.au, benh@kernel.crashing.org, paulus@samba.org
Cc: devicetree@vger.kernel.org, linux-fbdev@vger.kernel.org,
dri-devel@lists.freedesktop.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v2 2/2] fbdev: Warn in hot-unplug workaround for framebuffers without device
Date: Wed, 20 Apr 2022 09:35:47 +0200 [thread overview]
Message-ID: <621dcf6a-c23d-24cd-951e-26227f465ab0@redhat.com> (raw)
In-Reply-To: <20220419100405.12600-3-tzimmermann@suse.de>
Hello Thomas,
Thanks a lot for re-spinning your series.
On 4/19/22 12:04, Thomas Zimmermann wrote:
> A workaround makes fbdev hot-unplugging work for framebuffers without
> device. The only user for this feature was offb. As each OF framebuffer
> now has an associated platform device, the workaround hould no longer
> be triggered. Update it with a warning and rewrite the comment. Fbdev
> drivers that trigger the hot-unplug workaround really need to be fixed.
>
> Signed-off-by: Thomas Zimmermann <tzimmermann@suse.de>
> Suggested-by: Javier Martinez Canillas <javierm@redhat.com>
> ---
Reviewed-by: Javier Martinez Canillas <javierm@redhat.com>
--
Best regards,
Javier Martinez Canillas
Linux Engineering
Red Hat
prev parent reply other threads:[~2022-04-20 7:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-19 10:04 [PATCH v2 0/2] of: Register platform device for each framebuffer Thomas Zimmermann
2022-04-19 10:04 ` [PATCH v2 1/2] of: Create platform devices for OF framebuffers Thomas Zimmermann
2022-04-19 13:30 ` Rob Herring
2022-04-19 13:41 ` Thomas Zimmermann
2022-04-19 10:04 ` [PATCH v2 2/2] fbdev: Warn in hot-unplug workaround for framebuffers without device Thomas Zimmermann
2022-04-20 7:35 ` 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=621dcf6a-c23d-24cd-951e-26227f465ab0@redhat.com \
--to=javierm@redhat.com \
--cc=benh@kernel.crashing.org \
--cc=daniel@ffwll.ch \
--cc=deller@gmx.de \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=frowand.list@gmail.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=robh+dt@kernel.org \
--cc=sam@ravnborg.org \
--cc=tzimmermann@suse.de \
/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).