linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Scot Doyle <lkml14@scotdoyle.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Tomi Valkeinen <tomi.valkeinen@ti.com>,
	Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Alistair Popple <alistair@popple.id.au>,
	Pavel Machek <pavel@ucw.cz>,
	airlied@redhat.com, linux-fbdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fbcon: initialize blink interval before calling fb_set_par
Date: Tue, 20 Oct 2015 22:04:22 +0000	[thread overview]
Message-ID: <alpine.DEB.2.11.1510202110060.1573@local> (raw)
In-Reply-To: <1445374804.3025.16.camel@kernel.crashing.org>

On Wed, 21 Oct 2015, Benjamin Herrenschmidt wrote:
> On Fri, 2015-10-09 at 15:08 +0000, Scot Doyle wrote:
> > Since commit 27a4c827c34ac4256a190cc9d24607f953c1c459
> >     fbcon: use the cursor blink interval provided by vt
> > 
> > a PPC64LE kernel fails to boot when fbcon_add_cursor_timer uses an
> > uninitialized ops->cur_blink_jiffies. Prevent by initializing
> > in fbcon_init before the call to info->fbops->fb_set_par.
> 
> Any reason that hasn't hit upstream (and stable) yet ? This is pretty
> major...

It's currently in the tty-linus branch of Greg's tty tree, so should be 
included in the next rc.

      reply	other threads:[~2015-10-20 22:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-03  1:38 [BUG] RCU stall in cursor_timer_handler Alistair Popple
2015-10-03  5:12 ` Scot Doyle
2015-10-09  5:31   ` Alistair Popple
2015-10-09 15:08     ` [PATCH] fbcon: initialize blink interval before calling fb_set_par Scot Doyle
2015-10-09 20:48       ` Benjamin Herrenschmidt
2015-10-20 21:00       ` Benjamin Herrenschmidt
2015-10-20 22:04         ` Scot Doyle [this message]

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=alpine.DEB.2.11.1510202110060.1573@local \
    --to=lkml14@scotdoyle.com \
    --cc=airlied@redhat.com \
    --cc=alistair@popple.id.au \
    --cc=benh@kernel.crashing.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=plagnioj@jcrosoft.com \
    --cc=tomi.valkeinen@ti.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).