From: Peter Zijlstra <peterz@infradead.org>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: LKML <linux-kernel@vger.kernel.org>,
DRI Development <dri-devel@lists.freedesktop.org>,
Dave Airlie <airlied@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH 2/2] [RESEND] console: implement lockdep support for console_lock
Date: Mon, 24 Sep 2012 15:10:17 +0200 [thread overview]
Message-ID: <1348492217.11847.60.camel@twins> (raw)
In-Reply-To: <CAKMK7uGyDOhCtP_fCRa-oirQ8edQcSiW8L_vSE9M29LU3EUoqg@mail.gmail.com>
On Mon, 2012-09-24 at 14:54 +0200, Daniel Vetter wrote:
> I've read through the patches and I'm hoping you don't volunteer me to
> pick these up ... ;-)
Worth a try, right? :-)
> But there doesn't seem to be anything that would
> get worse through this lockdep annotation patch, right?
No indeed, your patch looks fine, I just wanted to comment on the
printk() thing.
prev parent reply other threads:[~2012-09-24 13:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-17 23:03 [PATCH 1/2] [RESEND] console: use might_sleep in console_lock Daniel Vetter
2012-09-17 23:03 ` [PATCH 2/2] [RESEND] console: implement lockdep support for console_lock Daniel Vetter
2012-09-18 7:33 ` Jani Nikula
2012-09-18 7:33 ` Jani Nikula
2012-09-19 7:30 ` Daniel Vetter
2012-09-22 17:52 ` [PATCH] " Daniel Vetter
2012-09-22 20:06 ` [Intel-gfx] " Greg KH
2012-09-22 20:06 ` Greg KH
2012-09-24 11:36 ` [Intel-gfx] " Daniel Vetter
2012-10-02 12:56 ` Daniel Vetter
2012-10-02 13:28 ` Greg KH
2012-10-02 13:28 ` Greg KH
2012-10-02 13:31 ` [Intel-gfx] " Daniel Vetter
2012-09-24 12:17 ` [PATCH 2/2] [RESEND] " Peter Zijlstra
2012-09-24 12:24 ` Peter Zijlstra
2012-09-24 12:54 ` Daniel Vetter
2012-09-24 13:10 ` Peter Zijlstra [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=1348492217.11847.60.camel@twins \
--to=peterz@infradead.org \
--cc=airlied@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.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.