linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: public@timruffing.de
To: Javier Martinez Canillas <javierm@redhat.com>
Cc: Thomas Zimmermann <tzimmermann@suse.de>,
	Maxime Ripard <maxime@cerno.tech>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	Daniel Vetter <daniel@ffwll.ch>, Helge Deller <deller@gmx.de>,
	dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, public@timruffing.de
Subject: Re: [PATCH v2] Revert "fbdev: Make fb_release() return -ENODEV if fbdev was unregistered"
Date: Mon,  9 May 2022 16:01:49 +0200	[thread overview]
Message-ID: <20220509140149.34734-1-public@timruffing.de> (raw)
In-Reply-To: <642f515e-aa71-7c90-a715-e49dcf12baee@redhat.com>

Thanks for this patch. Do you think this can be backported to LTS 5.17.y and
5.15.y, which are still buggy? It's not a big deal for me but others might
profit.

Background:
The patch solves a regression from 5.17.1 to 5.17.2 or 5.15.32 and
5.15.33 I was about to report. On my Thinkpad T570, I got random "BUG", "Oops"
or even panics when during booting with efifb and plymouthd (and then sometimes
also problems when shutting down because). I had bisected the issue to commit
27599aacbaef. I could provide more info but I don't think it's necessary given
that either aafa025c76dcc7d1a8c8f0bdefcbe4eb480b2f6a or your better patch now
fixes the issue (I tested both, both work for me).

Best,
Tim Ruffing


  reply	other threads:[~2022-05-09 14:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-04 11:59 [PATCH v2] Revert "fbdev: Make fb_release() return -ENODEV if fbdev was unregistered" Javier Martinez Canillas
2022-05-06  7:32 ` Javier Martinez Canillas
2022-05-09 14:01   ` public [this message]
2022-05-09 14:36     ` Javier Martinez Canillas

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=20220509140149.34734-1-public@timruffing.de \
    --to=public@timruffing.de \
    --cc=daniel.vetter@ffwll.ch \
    --cc=daniel@ffwll.ch \
    --cc=deller@gmx.de \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=javierm@redhat.com \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maxime@cerno.tech \
    --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).