From: Jani Nikula <jani.nikula@intel.com>
To: Greg KH <gregkh@linuxfoundation.org>,
Saeed Mirzamohammadi <saeed.mirzamohammadi@oracle.com>
Cc: linux-fbdev@vger.kernel.org, b.zolnierkie@samsung.com,
daniel.vetter@ffwll.ch, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, gustavoars@kernel.org,
dri-devel@lists.freedesktop.org,
Thomas Zimmermann <tzimmermann@suse.de>,
akpm@linux-foundation.org, rppt@kernel.org
Subject: Re: [PATCH 1/1] video: fbdev: fix divide error in fbcon_switch
Date: Thu, 29 Oct 2020 13:13:01 +0200 [thread overview]
Message-ID: <874kmdi8ua.fsf@intel.com> (raw)
In-Reply-To: <20201029110326.GC3840801@kroah.com>
On Thu, 29 Oct 2020, Greg KH <gregkh@linuxfoundation.org> wrote:
> On Tue, Oct 27, 2020 at 10:12:49AM -0700, Saeed Mirzamohammadi wrote:
>> Hi Greg,
>>
>> Sorry for the confusion. I’m requesting stable maintainers to cherry-pick this patch into stable 5.4 and 5.8.
>> commit cc07057c7c88fb8eff3b1991131ded0f0bcfa7e3
>> Author: Saeed Mirzamohammadi <saeed.mirzamohammadi@oracle.com>
>> Date: Wed Oct 21 16:57:58 2020 -0700
>>
>> video: fbdev: fix divide error in fbcon_switch
>
> I do not see that commit in Linus's tree, do you?
It's in drm-misc-next, IIUC heading for Linus' tree in the next merge
window in 6-8 weeks. Which is to say this should probably have been
applied to drm-misc-fixes branch heading for v5.10-rcX, with a Cc:
stable tag, to begin with.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2020-10-29 11:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-21 23:57 [PATCH 1/1] video: fbdev: fix divide error in fbcon_switch saeed.mirzamohammadi
2020-10-22 0:33 ` Saeed Mirzamohammadi
2020-10-22 7:28 ` Thomas Zimmermann
2020-10-22 7:34 ` Thomas Zimmermann
2020-10-26 17:00 ` Saeed Mirzamohammadi
2020-10-27 6:22 ` Greg KH
[not found] ` <2DA9AE6D-93D6-4142-9FC4-EEACB92B7203@oracle.com>
2020-10-29 11:03 ` Greg KH
2020-10-29 11:13 ` Jani Nikula [this message]
2020-10-29 11:30 ` Greg KH
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=874kmdi8ua.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=akpm@linux-foundation.org \
--cc=b.zolnierkie@samsung.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=gustavoars@kernel.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rppt@kernel.org \
--cc=saeed.mirzamohammadi@oracle.com \
--cc=stable@vger.kernel.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).