From: Daniel Vetter <daniel.vetter@ffwll.ch>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: 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>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [Intel-gfx] [PATCH] console: implement lockdep support for console_lock
Date: Tue, 2 Oct 2012 15:31:28 +0200 [thread overview]
Message-ID: <CAKMK7uHDwoLbXCUbWyJr9NX7g0MN_8B=sV-6w=tYGWYk+GN4tg@mail.gmail.com> (raw)
In-Reply-To: <20121002132805.GA30187@kroah.com>
On Tue, Oct 2, 2012 at 3:28 PM, Greg KH <gregkh@linuxfoundation.org> wrote:
> No, as it hasn't been in linux-next already, I can't send it in for 3.7,
> sorry, you know that. I'll be glad to queue it up for 3.8 if you want me to.
Hey, was worth a shot ;-) Yeah, if you can pick it up for 3.8, that
would be nice, since the patches have been floating for a while by now
...
Thanks, Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2012-10-02 13:31 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 ` Daniel Vetter [this message]
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='CAKMK7uHDwoLbXCUbWyJr9NX7g0MN_8B=sV-6w=tYGWYk+GN4tg@mail.gmail.com' \
--to=daniel.vetter@ffwll.ch \
--cc=a.p.zijlstra@chello.nl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=intel-gfx@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.