From: Daniel Vetter <daniel@ffwll.ch>
To: Dave Airlie <airlied@gmail.com>
Cc: DRI mailing list <dri-devel@lists.freedesktop.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [git pull] drm urgent fix
Date: Wed, 25 Mar 2015 10:06:28 +0100 [thread overview]
Message-ID: <20150325090628.GS1349@phenom.ffwll.local> (raw)
In-Reply-To: <CAPM=9twguSqnJN0eGRPL87bYZ92XTnd3-Jvf=nVvwm_zXP47hg@mail.gmail.com>
On Wed, Mar 25, 2015 at 10:04:09AM +1000, Dave Airlie wrote:
> On 25 March 2015 at 09:48, Linus Torvalds <torvalds@linux-foundation.org> wrote:
> > drm/i915: Don't try to reference the fb in get_initial_plane_config()
> >
> > On Mon, Mar 23, 2015 at 7:11 PM, Dave Airlie <airlied@linux.ie> wrote:
> >>
> >> a few people reported an oops that looks to be fixed in drm-next already,
> >> so I've pulled the patch back.
> >
> > Hmm. At least from Josh's report, he also needs
> >
> > drm/i915: Don't try to reference the fb in get_initial_plane_config()
> >
> > in addition to the commit you have.
> >
> > Should I perhaps wait for that one too? Daniel?
>
> Yes, Daniel indicated to Jani this morning we should pull this, so
> I'll sidestep the middle man here for expediency.
There's going to be one more (waiting for confirmation since I can't repro
here). But with these I think we have at least the oopses under control,
the remaining one is just paranoid state self-checks. I hope ;-)
And since this is all a bit unpleasant for -rc5 I've thought a bit about
what needs to be improved:
- I'll be more broken record about correctly referencing commits that have
introduced an issue. Some of the fixes in -next didn't have these
references, so when we cherry-picked the first one it was hard to find
the follow-up fixups.
- I'm stitching together a short scriptlet for cherry-picking to make sure
we don't forget to look for all the fixup commits next time around.
- I'll start a drm-fixes branch to make sure drm core fixes don't get lost
when I "temporarily" stash them in my drm-misc -next branch.
Cheers, Daniel
>
> updated pull:
>
> The following changes since commit 90a5a895cc8b284ac522757a01de15e36710c2b9:
>
> Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net
> (2015-03-23 10:16:13 -0700)
>
> are available in the git repository at:
>
> git://people.freedesktop.org/~airlied/linux drm-fixes
>
> for you to fetch changes up to 59a58cb34d3fe73e6c899cc5d9a87428ca662925:
>
> drm/i915: Don't try to reference the fb in
> get_initial_plane_config() (2015-03-25 10:01:46 +1000)
>
> ----------------------------------------------------------------
> Damien Lespiau (1):
> drm/i915: Don't try to reference the fb in get_initial_plane_config()
>
> Daniel Vetter (1):
> drm: Fixup racy refcounting in plane_force_disable
>
> drivers/gpu/drm/drm_crtc.c | 13 +------------
> drivers/gpu/drm/i915/intel_display.c | 7 +++----
> 2 files changed, 4 insertions(+), 16 deletions(-)
>
>
> Dave.
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: Daniel Vetter <daniel@ffwll.ch>
To: Dave Airlie <airlied@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Dave Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
DRI mailing list <dri-devel@lists.freedesktop.org>
Subject: Re: [git pull] drm urgent fix
Date: Wed, 25 Mar 2015 10:06:28 +0100 [thread overview]
Message-ID: <20150325090628.GS1349@phenom.ffwll.local> (raw)
In-Reply-To: <CAPM=9twguSqnJN0eGRPL87bYZ92XTnd3-Jvf=nVvwm_zXP47hg@mail.gmail.com>
On Wed, Mar 25, 2015 at 10:04:09AM +1000, Dave Airlie wrote:
> On 25 March 2015 at 09:48, Linus Torvalds <torvalds@linux-foundation.org> wrote:
> > drm/i915: Don't try to reference the fb in get_initial_plane_config()
> >
> > On Mon, Mar 23, 2015 at 7:11 PM, Dave Airlie <airlied@linux.ie> wrote:
> >>
> >> a few people reported an oops that looks to be fixed in drm-next already,
> >> so I've pulled the patch back.
> >
> > Hmm. At least from Josh's report, he also needs
> >
> > drm/i915: Don't try to reference the fb in get_initial_plane_config()
> >
> > in addition to the commit you have.
> >
> > Should I perhaps wait for that one too? Daniel?
>
> Yes, Daniel indicated to Jani this morning we should pull this, so
> I'll sidestep the middle man here for expediency.
There's going to be one more (waiting for confirmation since I can't repro
here). But with these I think we have at least the oopses under control,
the remaining one is just paranoid state self-checks. I hope ;-)
And since this is all a bit unpleasant for -rc5 I've thought a bit about
what needs to be improved:
- I'll be more broken record about correctly referencing commits that have
introduced an issue. Some of the fixes in -next didn't have these
references, so when we cherry-picked the first one it was hard to find
the follow-up fixups.
- I'm stitching together a short scriptlet for cherry-picking to make sure
we don't forget to look for all the fixup commits next time around.
- I'll start a drm-fixes branch to make sure drm core fixes don't get lost
when I "temporarily" stash them in my drm-misc -next branch.
Cheers, Daniel
>
> updated pull:
>
> The following changes since commit 90a5a895cc8b284ac522757a01de15e36710c2b9:
>
> Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net
> (2015-03-23 10:16:13 -0700)
>
> are available in the git repository at:
>
> git://people.freedesktop.org/~airlied/linux drm-fixes
>
> for you to fetch changes up to 59a58cb34d3fe73e6c899cc5d9a87428ca662925:
>
> drm/i915: Don't try to reference the fb in
> get_initial_plane_config() (2015-03-25 10:01:46 +1000)
>
> ----------------------------------------------------------------
> Damien Lespiau (1):
> drm/i915: Don't try to reference the fb in get_initial_plane_config()
>
> Daniel Vetter (1):
> drm: Fixup racy refcounting in plane_force_disable
>
> drivers/gpu/drm/drm_crtc.c | 13 +------------
> drivers/gpu/drm/i915/intel_display.c | 7 +++----
> 2 files changed, 4 insertions(+), 16 deletions(-)
>
>
> Dave.
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
next prev parent reply other threads:[~2015-03-25 9:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-24 2:11 [git pull] drm urgent fix Dave Airlie
2015-03-24 23:48 ` Linus Torvalds
2015-03-24 23:48 ` Linus Torvalds
2015-03-25 0:04 ` Dave Airlie
2015-03-25 0:04 ` Dave Airlie
2015-03-25 9:06 ` Daniel Vetter [this message]
2015-03-25 9:06 ` Daniel Vetter
2015-03-25 22:43 ` Linus Torvalds
2015-03-25 22:43 ` Linus Torvalds
2015-03-26 3:04 ` Linus Torvalds
2015-03-26 3:04 ` Linus Torvalds
2015-03-26 3:29 ` Dave Airlie
2015-03-26 3:29 ` Dave Airlie
2015-03-26 7:59 ` Daniel Vetter
2015-03-26 7:59 ` Daniel Vetter
2015-03-26 12:13 ` Jani Nikula
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=20150325090628.GS1349@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--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.