From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Borislav Petkov <bp@alien8.de>, Jiri Kosina <jkosina@suse.cz>,
Shawn Guo <shawn.guo@linaro.org>,
Sasha Levin <levinsasha928@gmail.com>,
Cong Wang <xiyou.wangcong@gmail.com>,
Josh Boyer <jwboyer@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
Florian Tobias Schandinat <florianSchandinat@gmx.de>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] fb: Rework locking to fix lock ordering on takeover
Date: Sat, 12 Jan 2013 21:05:15 +0000 [thread overview]
Message-ID: <cf1e4936-c572-48b0-9fac-1d2cf418bae2@email.android.com> (raw)
In-Reply-To: <CA+55aFw163CwK_MmUKY7zGFeck+Rxk_xs=BDrCAFpg-xac3vmQ@mail.gmail.com>
Alan is dealing with family stuff that is far more important. Someone who has the time needs to own this and the fb layer. Not a don't care - a don't have time.
Alan
next prev parent reply other threads:[~2013-01-12 21:06 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-16 19:27 Alan Cox
2012-11-21 12:45 ` Josh Boyer
2012-11-21 12:53 ` Alan Cox
2012-12-18 15:20 ` Josh Boyer
2012-12-25 16:08 ` Sasha Levin
2012-12-26 2:41 ` Cong Wang
2012-12-26 18:09 ` Sasha Levin
2012-12-27 4:53 ` Borislav Petkov
2012-12-28 11:50 ` Shawn Guo
2012-12-28 12:40 ` Borislav Petkov
2013-01-04 12:50 ` Alexander Holler
2013-01-04 13:25 ` Alan Cox
2013-01-04 13:36 ` Alexander Holler
2013-01-05 11:41 ` Alexander Holler
2013-01-05 11:42 ` [PATCH] fb: udlfb: fix scheduling while atomic Alexander Holler
2013-01-06 12:46 ` Alexander Holler
2013-01-09 13:47 ` [PATCH v2] " Alexander Holler
2013-01-05 12:07 ` [PATCH] fb: Rework locking to fix lock ordering on takeover Alan Cox
2013-01-05 12:06 ` Alexander Holler
2013-01-07 9:37 ` Jiri Kosina
2013-01-12 18:36 ` Borislav Petkov
2013-01-12 20:51 ` Linus Torvalds
2013-01-12 21:05 ` Alan Cox [this message]
2013-01-12 21:13 ` Andrew Morton
2013-01-13 0:02 ` Borislav Petkov
2013-01-15 12:06 ` Maarten Lankhorst
2013-01-15 15:12 ` Alan Cox
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=cf1e4936-c572-48b0-9fac-1d2cf418bae2@email.android.com \
--to=alan@lxorguk.ukuu.org.uk \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=florianSchandinat@gmx.de \
--cc=jkosina@suse.cz \
--cc=jwboyer@gmail.com \
--cc=levinsasha928@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shawn.guo@linaro.org \
--cc=torvalds@linux-foundation.org \
--cc=xiyou.wangcong@gmail.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
Powered by JetHome