From: Jani Nikula <jani.nikula@linux.intel.com>
To: Helge Deller <deller@gmx.de>, Daniel Vetter <daniel@ffwll.ch>,
Sven Schnelle <svens@stackframe.org>
Cc: Linux Fbdev development list <linux-fbdev@vger.kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
Daniel Vetter <daniel.vetter@intel.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Javier Martinez Canillas <javierm@redhat.com>,
DRI Development <dri-devel@lists.freedesktop.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Tomi Valkeinen <tomi.valkeinen@ti.com>,
Claudio Suarez <cssk@net-c.es>, Gerd Hoffmann <kraxel@redhat.com>,
Pavel Machek <pavel@ucw.cz>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Sam Ravnborg <sam@ravnborg.org>
Subject: Re: [PATCH 2/2] Revert "fbcon: Disable accelerated scrolling"
Date: Wed, 19 Jan 2022 18:13:39 +0200 [thread overview]
Message-ID: <87ilufbt58.fsf@intel.com> (raw)
In-Reply-To: <40d39363-bae8-93f2-71c6-7d5531f144bf@gmx.de>
On Wed, 19 Jan 2022, Helge Deller <deller@gmx.de> wrote:
> On 1/19/22 16:42, Daniel Vetter wrote:
>> If otoh you get the maintainership first to be able to cram in reverts
>> without discussions, then it's very backwards.
> I'm working on the Linux kernel since at least 23 years and am a maintainer of parts of it.
> I know that and would never push something which is controversal without discussions.
I think the entire MAINTAINERS change was controversial and rushed to
Linus without discussion over a weekend.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Helge Deller <deller@gmx.de>, Daniel Vetter <daniel@ffwll.ch>,
Sven Schnelle <svens@stackframe.org>
Cc: Linux Fbdev development list <linux-fbdev@vger.kernel.org>,
Pavel Machek <pavel@ucw.cz>, Sam Ravnborg <sam@ravnborg.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Javier Martinez Canillas <javierm@redhat.com>,
DRI Development <dri-devel@lists.freedesktop.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Tomi Valkeinen <tomi.valkeinen@ti.com>,
Claudio Suarez <cssk@net-c.es>, Gerd Hoffmann <kraxel@redhat.com>,
Thomas Zimmermann <tzimmermann@suse.de>,
Daniel Vetter <daniel.vetter@intel.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH 2/2] Revert "fbcon: Disable accelerated scrolling"
Date: Wed, 19 Jan 2022 18:13:39 +0200 [thread overview]
Message-ID: <87ilufbt58.fsf@intel.com> (raw)
In-Reply-To: <40d39363-bae8-93f2-71c6-7d5531f144bf@gmx.de>
On Wed, 19 Jan 2022, Helge Deller <deller@gmx.de> wrote:
> On 1/19/22 16:42, Daniel Vetter wrote:
>> If otoh you get the maintainership first to be able to cram in reverts
>> without discussions, then it's very backwards.
> I'm working on the Linux kernel since at least 23 years and am a maintainer of parts of it.
> I know that and would never push something which is controversal without discussions.
I think the entire MAINTAINERS change was controversial and rushed to
Linus without discussion over a weekend.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2022-01-19 16:13 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-19 11:08 [PATCH 0/2] Fix regression introduced by disabling accelerated scrolling in fbcon Helge Deller
2022-01-19 11:08 ` [PATCH 1/2] Revert "fbdev: Garbage collect fbdev scrolling acceleration, part 1 (from TODO list)" Helge Deller
2022-01-19 11:08 ` [PATCH 2/2] Revert "fbcon: Disable accelerated scrolling" Helge Deller
2022-01-19 11:22 ` Greg Kroah-Hartman
2022-01-19 11:22 ` Greg Kroah-Hartman
2022-01-19 11:28 ` Greg Kroah-Hartman
2022-01-19 11:28 ` Greg Kroah-Hartman
2022-01-19 11:47 ` Geert Uytterhoeven
2022-01-19 11:47 ` Geert Uytterhoeven
2022-01-19 12:28 ` Helge Deller
2022-01-19 12:28 ` Helge Deller
2022-01-19 14:01 ` Linus Torvalds
2022-01-19 14:01 ` Linus Torvalds
2022-01-19 14:11 ` Helge Deller
2022-01-19 14:11 ` Helge Deller
2022-01-19 14:34 ` Daniel Vetter
2022-01-19 14:34 ` Daniel Vetter
2022-01-19 15:05 ` Sven Schnelle
2022-01-19 15:05 ` Sven Schnelle
2022-01-19 15:37 ` Thomas Zimmermann
2022-01-19 15:37 ` Thomas Zimmermann
2022-01-19 16:55 ` Helge Deller
2022-01-19 16:55 ` Helge Deller
2022-01-19 15:42 ` Daniel Vetter
2022-01-19 15:42 ` Daniel Vetter
2022-01-19 15:54 ` Helge Deller
2022-01-19 15:54 ` Helge Deller
2022-01-19 16:13 ` Jani Nikula [this message]
2022-01-19 16:13 ` Jani Nikula
2022-01-19 16:31 ` Daniel Vetter
2022-01-19 16:31 ` Daniel Vetter
2022-01-19 15:18 ` Helge Deller
2022-01-19 15:18 ` Helge Deller
2022-01-19 13:01 ` Sven Schnelle
2022-01-19 13:01 ` Sven Schnelle
2022-01-19 13:35 ` Greg Kroah-Hartman
2022-01-19 13:35 ` Greg Kroah-Hartman
2022-01-20 14:30 ` Daniel Vetter
2022-01-20 14:30 ` Daniel Vetter
2022-01-20 17:01 ` Helge Deller
2022-01-21 7:20 ` Gerd Hoffmann
2022-01-21 7:20 ` Gerd Hoffmann
2022-01-24 11:10 ` Helge Deller
2022-01-24 11:10 ` Helge Deller
2022-01-24 11:28 ` Javier Martinez Canillas
2022-01-24 11:28 ` Javier Martinez Canillas
2022-01-24 11:33 ` Thomas Zimmermann
2022-01-24 11:33 ` Thomas Zimmermann
2022-01-24 11:50 ` Javier Martinez Canillas
2022-01-24 11:50 ` Javier Martinez Canillas
2022-01-24 15:29 ` Helge Deller
2022-01-24 15:29 ` Helge Deller
2022-01-24 15:45 ` Thomas Zimmermann
2022-01-24 15:45 ` Thomas Zimmermann
2022-01-24 15:50 ` Geert Uytterhoeven
2022-01-24 15:50 ` Geert Uytterhoeven
2022-01-24 15:58 ` Daniel Vetter
2022-01-24 15:58 ` Daniel Vetter
2022-01-24 15:50 ` Geert Uytterhoeven
2022-01-24 15:50 ` Geert Uytterhoeven
2022-01-24 16:11 ` Thomas Zimmermann
2022-01-24 16:11 ` Thomas Zimmermann
2022-01-19 12:45 ` [PATCH 0/2] Fix regression introduced by disabling accelerated scrolling in fbcon Geert Uytterhoeven
2022-01-19 12:45 ` Geert Uytterhoeven
2022-01-19 13:02 ` Sven Schnelle
2022-01-19 13:02 ` Sven Schnelle
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=87ilufbt58.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=cssk@net-c.es \
--cc=daniel.vetter@intel.com \
--cc=daniel@ffwll.ch \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=javierm@redhat.com \
--cc=kraxel@redhat.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=sam@ravnborg.org \
--cc=svens@stackframe.org \
--cc=tomi.valkeinen@ti.com \
--cc=torvalds@linux-foundation.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 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.