From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Hamza Mahfooz <someguy@effective-light.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
Thomas Zimmermann <tzimmermann@suse.de>,
Peilin Ye <yepeilin.cs@gmail.com>,
Jing Xiangfeng <jingxiangfeng@huawei.com>,
George Kennedy <george.kennedy@oracle.com>,
Sam Ravnborg <sam@ravnborg.org>,
DRI Development <dri-devel@lists.freedesktop.org>,
Linux Fbdev development list <linux-fbdev@vger.kernel.org>,
Pavel Machek <pavel@ucw.cz>
Subject: Re: [PATCH] fbcon: garbage collect fbdev scrolling acceleration
Date: Fri, 9 Jul 2021 09:49:02 +0200 [thread overview]
Message-ID: <CAMuHMdWhs4en-yR9ic+d4V9M_0BUFX40rP0M=tZRGMaUy2wv3g@mail.gmail.com> (raw)
In-Reply-To: <20210709010055.86663-1-someguy@effective-light.com>
On Fri, Jul 9, 2021 at 3:04 AM Hamza Mahfooz
<someguy@effective-light.com> wrote:
> As per commit 39aead8373b3 ("fbcon: Disable accelerated scrolling"), we can
> now remove all of the code that was made redundant by disabling scrolling
> acceleration.
Bummer, more code to revert to re-enable acceleration in the _56_
fbdev drivers using acceleration (some of them unusable without),
despite commit 39aead8373b3 claiming "No other driver supportes
accelerated fbcon"...
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2021-07-09 7:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-09 1:00 [PATCH] fbcon: garbage collect fbdev scrolling acceleration Hamza Mahfooz
2021-07-09 7:49 ` Geert Uytterhoeven [this message]
2021-07-09 21:28 ` Hamza Mahfooz
2021-07-12 11:16 ` Geert Uytterhoeven
2021-07-09 8:04 ` Daniel Vetter
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='CAMuHMdWhs4en-yR9ic+d4V9M_0BUFX40rP0M=tZRGMaUy2wv3g@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=george.kennedy@oracle.com \
--cc=gregkh@linuxfoundation.org \
--cc=jingxiangfeng@huawei.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=sam@ravnborg.org \
--cc=someguy@effective-light.com \
--cc=tzimmermann@suse.de \
--cc=yepeilin.cs@gmail.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;
as well as URLs for NNTP newsgroup(s).