From: "davej@codemonkey.org.uk" <davej@codemonkey.org.uk>
To: Dave Airlie <airlied@gmail.com>
Cc: "airlied@linux.ie" <airlied@linux.ie>,
"torvalds@linux-foundation.org" <torvalds@linux-foundation.org>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"Vetter, Daniel" <daniel.vetter@intel.com>,
"Lankhorst, Maarten" <maarten.lankhorst@intel.com>
Subject: Re: [regression] [git pull] drm for 4.3
Date: Tue, 20 Oct 2015 10:42:29 -0400 [thread overview]
Message-ID: <20151020144229.GA25889@codemonkey.org.uk> (raw)
In-Reply-To: <CAPM=9ty4Nxynnr+fkCK7H85MTyuXgj+OrgvT6zPv2c8xTMKOJw@mail.gmail.com>
On Tue, Oct 20, 2015 at 03:33:27PM +1000, Dave Airlie wrote:
> On 20 October 2015 at 07:54, Daniel Vetter <daniel@ffwll.ch> wrote:
> > On Mon, Oct 19, 2015 at 04:19:08PM -0400, davej@codemonkey.org.uk wrote:
> >> On Wed, Sep 30, 2015 at 08:56:26AM +0200, Daniel Vetter wrote:
> >>
> >> > > The warning on boot seems to be gone as of rc3, but I can now trigger this pretty easily..
> >> >
> >> > http://patchwork.freedesktop.org/patch/60618/
> >>
> >> Back from several weeks of travel.. I tried again with rc6, and
> >> I'm still seeing the same traces.
> >
> > Oh crap, applied patch to wrong tree. We need to cherry-pick
> >
> > commit 621bd0f6982badd6483acb191eb7b6226a578328
> > Author: Daniel Vetter <daniel.vetter@ffwll.ch>
> > Date: Tue Sep 29 09:56:53 2015 +0200
> >
> > drm: Fix locking for sysfs dpms file
> >
> > to drm-fixes. Sorry about that screw-up. Dave, can you pls do that one? It
> > even comes with the needed cc: stable included (since the locking breakage
> > was done in 4.0, it only surface due to a new warning in 4.3).
>
> That is already in Linus's tree, I picked it last week I think.
Yeah, that's in the tree I'm testing.
Dave
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
WARNING: multiple messages have this Message-ID (diff)
From: "davej@codemonkey.org.uk" <davej@codemonkey.org.uk>
To: Dave Airlie <airlied@gmail.com>
Cc: Jani Nikula <jani.nikula@linux.intel.com>,
"Lankhorst, Maarten" <maarten.lankhorst@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"torvalds@linux-foundation.org" <torvalds@linux-foundation.org>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"Roper, Matthew D" <matthew.d.roper@intel.com>,
"Vetter, Daniel" <daniel.vetter@intel.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"jbarnes@virtuousgeek.org" <jbarnes@virtuousgeek.org>,
"airlied@linux.ie" <airlied@linux.ie>,
"Miramontes Caton,
Jairo Daniel" <jairo.daniel.miramontes.caton@intel.com>
Subject: Re: [Intel-gfx] [regression] [git pull] drm for 4.3
Date: Tue, 20 Oct 2015 10:42:29 -0400 [thread overview]
Message-ID: <20151020144229.GA25889@codemonkey.org.uk> (raw)
In-Reply-To: <CAPM=9ty4Nxynnr+fkCK7H85MTyuXgj+OrgvT6zPv2c8xTMKOJw@mail.gmail.com>
On Tue, Oct 20, 2015 at 03:33:27PM +1000, Dave Airlie wrote:
> On 20 October 2015 at 07:54, Daniel Vetter <daniel@ffwll.ch> wrote:
> > On Mon, Oct 19, 2015 at 04:19:08PM -0400, davej@codemonkey.org.uk wrote:
> >> On Wed, Sep 30, 2015 at 08:56:26AM +0200, Daniel Vetter wrote:
> >>
> >> > > The warning on boot seems to be gone as of rc3, but I can now trigger this pretty easily..
> >> >
> >> > http://patchwork.freedesktop.org/patch/60618/
> >>
> >> Back from several weeks of travel.. I tried again with rc6, and
> >> I'm still seeing the same traces.
> >
> > Oh crap, applied patch to wrong tree. We need to cherry-pick
> >
> > commit 621bd0f6982badd6483acb191eb7b6226a578328
> > Author: Daniel Vetter <daniel.vetter@ffwll.ch>
> > Date: Tue Sep 29 09:56:53 2015 +0200
> >
> > drm: Fix locking for sysfs dpms file
> >
> > to drm-fixes. Sorry about that screw-up. Dave, can you pls do that one? It
> > even comes with the needed cc: stable included (since the locking breakage
> > was done in 4.0, it only surface due to a new warning in 4.3).
>
> That is already in Linus's tree, I picked it last week I think.
Yeah, that's in the tree I'm testing.
Dave
next prev parent reply other threads:[~2015-10-20 14:42 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-04 22:40 [git pull] drm for 4.3 Dave Airlie
2015-09-04 22:40 ` Dave Airlie
2015-09-07 18:45 ` Dave Jones
2015-09-07 18:45 ` Dave Jones
2015-09-21 18:48 ` Dave Jones
2015-09-21 18:48 ` Dave Jones
2015-09-22 15:00 ` Jesse Barnes
2015-09-22 15:00 ` [Intel-gfx] " Jesse Barnes
2015-09-22 15:13 ` [regression] " Daniel Vetter
2015-09-22 15:13 ` Daniel Vetter
2015-09-22 16:15 ` Matt Roper
2015-09-22 16:15 ` Matt Roper
2015-09-23 1:49 ` Dave Jones
2015-09-23 1:49 ` Dave Jones
2015-09-23 11:07 ` Lankhorst, Maarten
2015-09-23 11:07 ` Lankhorst, Maarten
2015-09-24 3:51 ` davej
2015-09-24 3:51 ` davej
2015-09-24 13:26 ` Jani Nikula
2015-09-24 13:26 ` Jani Nikula
2015-09-30 1:07 ` davej
2015-09-30 1:07 ` davej
2015-09-30 6:56 ` Daniel Vetter
2015-09-30 6:56 ` Daniel Vetter
2015-10-19 20:19 ` davej
2015-10-19 20:19 ` davej
2015-10-19 21:54 ` Daniel Vetter
2015-10-19 21:54 ` [Intel-gfx] " Daniel Vetter
2015-10-20 5:33 ` Dave Airlie
2015-10-20 5:33 ` [Intel-gfx] " Dave Airlie
2015-10-20 14:42 ` davej [this message]
2015-10-20 14:42 ` davej
2015-09-29 6:43 ` [regression] boot to the blackscreen with the kernel 4.3 zhuhuachun
2015-09-29 6:43 ` [Intel-gfx] " zhuhuachun
2015-09-08 2:03 ` [git pull] drm for 4.3 Stephen Rothwell
2015-09-08 2:03 ` Stephen Rothwell
2015-09-08 3:01 ` Dave Airlie
2015-09-08 3:01 ` Dave Airlie
2015-09-08 4:04 ` Stephen Rothwell
2015-09-08 4:04 ` Stephen Rothwell
2015-09-08 4:56 ` Dave Airlie
2015-09-08 4:56 ` Dave Airlie
2015-09-08 18:19 ` Linus Torvalds
2015-09-08 18:19 ` Linus Torvalds
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=20151020144229.GA25889@codemonkey.org.uk \
--to=davej@codemonkey.org.uk \
--cc=airlied@gmail.com \
--cc=airlied@linux.ie \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.