From: Daniel Vetter <daniel@ffwll.ch>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
LKML <linux-kernel@vger.kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
DRI Development <dri-devel@lists.freedesktop.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH 2/2] [RESEND] console: implement lockdep support for console_lock
Date: Wed, 19 Sep 2012 09:30:27 +0200 [thread overview]
Message-ID: <20120919073027.GB1676@bremse> (raw)
In-Reply-To: <87627b9453.fsf@intel.com>
On Tue, Sep 18, 2012 at 10:33:28AM +0300, Jani Nikula wrote:
> On Tue, 18 Sep 2012, Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
> > +#ifdef CONFIG_LOCKDEP
> > +struct lockdep_map console_lock_dep_map = {
> > + .name = "console_lock"
> > +};
> > +#endif
>
> static?
Yeah, static. I'm travelling atm, so will take a while to resend ...
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2012-09-19 7:30 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 [this message]
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
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=20120919073027.GB1676@bremse \
--to=daniel@ffwll.ch \
--cc=a.p.zijlstra@chello.nl \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--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.