From: Andrew Morton <akpm@linux-foundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Daniel J Blueman <daniel@quora.org>,
Peter Jones <pjones@redhat.com>,
"linux-fbdev@vger.kernel.org" <linux-fbdev@vger.kernel.org>,
nouveau@lists.freedesktop.org,
Linux Kernel <linux-kernel@vger.kernel.org>,
Florian Tobias Schandinat <FlorianSchandinat@gmx.de>
Subject: Re: 3.8-rc2: EFI framebuffer lock inversion...
Date: Thu, 03 Jan 2013 20:06:03 +0000 [thread overview]
Message-ID: <20130103120603.6f8e94a7.akpm@linux-foundation.org> (raw)
In-Reply-To: <CA+55aFyseLhQj-u7XOdCayMN2dJ+LaKKxSN2NrfqFA98o1WW+A@mail.gmail.com>
On Thu, 3 Jan 2013 11:40:47 -0800
Linus Torvalds <torvalds@linux-foundation.org> wrote:
> On Thu, Jan 3, 2013 at 5:11 AM, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> >
> > The fb layer locking was broken. I posted patches early December which
> > should have fixed the ones we know about. ('fb: Rework locking to fix
> > lock ordering on takeover').
>
> That patch causes compile errors with "allmodconfig":
>
> ERROR: "do_take_over_console" [drivers/video/console/fbcon.ko] undefined!
> make[1]: *** [__modpost] Error 1
> make: *** [modules] Error 2
> make: *** Waiting for unfinished jobs....
>
> Hmm?
I have a couple of fixes against
fb-rework-locking-to-fix-lock-ordering-on-takeover.patch:
http://ozlabs.org/~akpm/mmots/broken-out/fb-rework-locking-to-fix-lock-ordering-on-takeover-fix.patch
http://ozlabs.org/~akpm/mmots/broken-out/fb-rework-locking-to-fix-lock-ordering-on-takeover-fix-2.patch
Florian has been busy for a month or two - I've been waiting for him to
reappear to consider this patch.
next prev parent reply other threads:[~2013-01-03 20:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-03 12:56 3.8-rc2: EFI framebuffer lock inversion Daniel J Blueman
2013-01-03 13:11 ` Alan Cox
2013-01-03 13:42 ` Daniel J Blueman
2013-01-03 14:28 ` Alan Cox
2013-01-03 19:40 ` Linus Torvalds
2013-01-03 20:06 ` Andrew Morton [this message]
2013-01-03 14:11 ` Sedat Dilek
2013-01-03 14:39 ` Daniel J Blueman
2013-01-03 15:09 ` Sedat Dilek
2013-01-04 10:49 ` Sedat Dilek
2013-01-03 15:36 ` Sedat Dilek
2013-01-03 15:12 ` Sedat Dilek
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=20130103120603.6f8e94a7.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=FlorianSchandinat@gmx.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=daniel@quora.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nouveau@lists.freedesktop.org \
--cc=pjones@redhat.com \
--cc=torvalds@linux-foundation.org \
/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;
as well as URLs for NNTP newsgroup(s).