From: Peter Zijlstra <peterz@infradead.org>
To: Dave Airlie <airlied@redhat.com>
Cc: linux-fbdev@vger.kernel.org, dri-devel@lists.sf.net,
linux-kernel@vger.kernel.org,
Linus <torvalds@linux-foundation.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Randy Dunlap <rdunlap@xenotime.net>,
Josh Boyer <jwboyer@gmail.com>
Subject: Re: [PATCH] fbcon: fix race condition between console lock and cursor timer
Date: Tue, 21 Aug 2012 12:14:43 +0000 [thread overview]
Message-ID: <1345551283.23018.106.camel@twins> (raw)
In-Reply-To: <1345531207-24926-1-git-send-email-airlied@redhat.com>
On Tue, 2012-08-21 at 16:40 +1000, Dave Airlie wrote:
> So after much tracing with direct netconsole writes (printks
> under console_lock not so useful)
I always use earlyprintk on serial..
next prev parent reply other threads:[~2012-08-21 12:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-21 6:40 [PATCH] fbcon: fix race condition between console lock and cursor timer Dave Airlie
2012-08-21 9:15 ` Alan Cox
2012-08-21 12:15 ` Peter Zijlstra
2012-08-22 4:00 ` Dave Airlie
2012-08-21 12:14 ` Peter Zijlstra [this message]
2012-08-21 13:19 ` Josh Boyer
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=1345551283.23018.106.camel@twins \
--to=peterz@infradead.org \
--cc=airlied@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dri-devel@lists.sf.net \
--cc=jwboyer@gmail.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=torvalds@linux-foundation.org \
/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).