From mboxrd@z Thu Jan 1 00:00:00 1970 From: Scot Doyle Date: Fri, 20 May 2016 16:27:17 +0000 Subject: Re: [PATCH] fbcon: warn on invalid cursor blink intervals Message-Id: List-Id: References: <1463510464-28124-1-git-send-email-ddaney.cavm@gmail.com> <20160517204912.GA29719@amd> <573DE2D0.1050402@caviumnetworks.com> <573E75CD.6050202@ozlabs.org> <573E9AE5.1020206@ozlabs.org> In-Reply-To: <573E9AE5.1020206@ozlabs.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Tomi Valkeinen , Jean-Christophe Plagniol-Villard , Greg Kroah-Hartman Cc: Jeremy Kerr , Ming Lei , David Daney , Dann Frazier , Peter Hurley , Pavel Machek , Jonathan Liu , Alistair Popple , Jean-Philippe Brucker , "Chintakuntla, Radha" , Jiri Slaby , David Airlie , David Daney , Scot Doyle , dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org, Linux Kernel Mailing List , stable On Fri, 20 May 2016, Jeremy Kerr wrote: > Hi Ming, > > >Then looks there are two fix patches acked & tested: > > > > - the patch in this thread > > - another one "[PATCH] tty: vt: Fix soft lockup in fbcon cursor > >blink timer." > > https://lkml.org/lkml/2016/5/17/455 > > > >So which one will be pushed to linus? > > Not that it's my call, but we may want both; the first as a safety > measure to prevent an invalid cur_blink_jiffies ever being set, and the > second one to actually fix the initialisation of vc_cur_blink_ms (and > address the warning introduced by the first). Tomi / Greg, I'd suggest - applying "tty: vt: Fix soft lockup in fbcon cursor blink timer." to 4.7 and stable[4.2] - applying "fbcon: warn on invalid cursor blink intervals" to 4.7 - ignoring "fbcon: use default if cursor blink interval is not valid" Note: the patches don't depend on each other > I guess we could just go with the latter for stable... > > Cheers, > > Jeremy