dri-devel Archive on lore.kernel.org
 help / color / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Dave Airlie <airlied@gmail.com>
Cc: DRI mailing list <dri-devel@lists.freedesktop.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [git pull] drm urgent fix
Date: Wed, 25 Mar 2015 20:04:41 -0700
Message-ID: <CA+55aFweWR=nDzc2Y=rCtL_H8JfdprQiCimN5dwc+TgyD4Bjsg@mail.gmail.com> (raw)
In-Reply-To: <CA+55aFxp_ouRmFsw+qUgdmoNFQ50C9XhmpAFB27c=1y8OKW60Q@mail.gmail.com>

On Wed, Mar 25, 2015 at 3:43 PM, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
> I'm going to wait a bit more with this, since clearly things are still
> in flux, and these two commits don't actually fix everything at all.
>
> There's apparently at least one more fix necessary.

Indeed. I can see the problem myself.

With current git I get two warnings:

   WARNING: CPU: 3 PID: 325 at include/linux/kref.h:47
drm_framebuffer_reference+0x72/0x80 [drm]()
   WARNING: CPU: 4 PID: 107 at drivers/gpu/drm/drm_atomic.c:482
drm_atomic_check_only+0x32d/0x4f0 [drm]()

and testing the pull it gets rid of the first one, but no tthe second one.

So that urgent fix is very much still lacking.

                           Linus
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply index

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-24  2:11 Dave Airlie
2015-03-24 23:48 ` Linus Torvalds
2015-03-25  0:04   ` Dave Airlie
2015-03-25  9:06     ` Daniel Vetter
2015-03-25 22:43     ` Linus Torvalds
2015-03-26  3:04       ` Linus Torvalds [this message]
2015-03-26  3:29         ` Dave Airlie
2015-03-26  7:59           ` Daniel Vetter
2015-03-26 12:13             ` Jani Nikula
  -- strict thread matches above, loose matches on Subject: below --
2012-12-19 21:56 Dave Airlie

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='CA+55aFweWR=nDzc2Y=rCtL_H8JfdprQiCimN5dwc+TgyD4Bjsg@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=airlied@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.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

dri-devel Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/dri-devel/0 dri-devel/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 dri-devel dri-devel/ https://lore.kernel.org/dri-devel \
		dri-devel@lists.freedesktop.org
	public-inbox-index dri-devel

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.freedesktop.lists.dri-devel


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git