From: Andrew Morton <akpm@linux-foundation.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Takashi Iwai <tiwai@suse.de>,
sedat.dilek@gmail.com, Jiri Kosina <jkosina@suse.cz>,
linux-fbdev@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
alan@lxorguk.ukuu.org.uk, "Rafael J. Wysocki" <rjw@sisk.pl>,
Jiri Slaby <jslaby@suse.cz>
Subject: Re: 3.8-rc2 lockdep complains about console_lock vs. fb_notifier_list.rwsem
Date: Thu, 17 Jan 2013 03:54:16 +0000 [thread overview]
Message-ID: <20130116195416.c2d9a107.akpm@linux-foundation.org> (raw)
In-Reply-To: <20130117024246.GF20928@kroah.com>
On Wed, 16 Jan 2013 18:42:46 -0800 Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
> > FWIW, Andrew took my patch in mm:
> > http://ozlabs.org/~akpm/mmots/broken-out/fb-rework-locking-to-fix-lock-ordering-on-takeover.patch
> > http://ozlabs.org/~akpm/mmots/broken-out/fb-yet-another-band-aid-for-fixing-lockdep-mess.patch
>
>
> Ok, so, which one should I take for 3.8? And ideally the fb maintainer
> should do this, not I, right?
Please see http://www.spinics.net/lists/linux-fbdev/msg08954.html
Tomi might be able to review the above for us. I think we need both.
If nothing else happens I intend to send both Linuswards for 3.8 in a
week or two.
next prev parent reply other threads:[~2013-01-17 3:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-05 12:13 3.8-rc2 lockdep complains about console_lock vs. fb_notifier_list.rwsem Sedat Dilek
2013-01-15 14:25 ` Takashi Iwai
2013-01-15 14:47 ` Takashi Iwai
2013-01-15 16:46 ` Takashi Iwai
2013-01-16 9:21 ` Sedat Dilek
2013-01-16 9:35 ` Takashi Iwai
2013-01-16 9:52 ` Sedat Dilek
2013-01-16 9:59 ` Sedat Dilek
[not found] ` <CA+icZUVviNP_BHBNQXo35W1Ge121_89argJ2NN1+rLOWgoYBtQ@mail.gmail.com>
2013-01-16 12:51 ` Sedat Dilek
2013-01-17 2:42 ` Greg Kroah-Hartman
2013-01-17 3:54 ` Andrew Morton [this message]
2013-01-17 4:16 ` Greg Kroah-Hartman
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=20130116195416.c2d9a107.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=gregkh@linuxfoundation.org \
--cc=jkosina@suse.cz \
--cc=jslaby@suse.cz \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=sedat.dilek@gmail.com \
--cc=tiwai@suse.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 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).