From: Borislav Petkov <bp@alien8.de>
To: Jiri Kosina <jkosina@suse.cz>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: Shawn Guo <shawn.guo@linaro.org>,
Sasha Levin <levinsasha928@gmail.com>,
Cong Wang <xiyou.wangcong@gmail.com>,
Josh Boyer <jwboyer@gmail.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
LKML <linux-kernel@vger.kernel.org>,
Florian Tobias Schandinat <florianSchandinat@gmx.de>
Subject: Re: [PATCH] fb: Rework locking to fix lock ordering on takeover
Date: Sat, 12 Jan 2013 19:36:19 +0100 [thread overview]
Message-ID: <20130112183619.GC10630@liondog.tnic> (raw)
In-Reply-To: <alpine.LRH.2.00.1301071037010.5443@twin.jikos.cz>
On Mon, Jan 07, 2013 at 10:37:15AM +0100, Jiri Kosina wrote:
> Still seeing it with current Linus' tree.
>
> Tested-by: Jiri Kosina <jkosina@suse.cz>
>
> Anyone applying this, please?
Yeah, I'm still seeing it in -rc3. Linus, can you pick up Alan's patch
from https://patchwork.kernel.org/patch/1757061/ please?
Thanks.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next prev parent reply other threads:[~2013-01-12 18:36 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 [this message]
2013-01-12 20:51 ` Linus Torvalds
2013-01-12 21:05 ` Alan Cox
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=20130112183619.GC10630@liondog.tnic \
--to=bp@alien8.de \
--cc=alan@lxorguk.ukuu.org.uk \
--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
all inboxes | Powered by JetHome®