From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Failed cherry-picks on drm-intel-fixes
Date: Mon, 18 Nov 2019 09:39:55 -0800 [thread overview]
Message-ID: <20191118173955.GA13156@intel.com> (raw)
Hi Chris,
2 fixes failed on this cherry-pick round.
8eb4704b124c ("drm/i915: Protect request peeking with RCU")
3cac195875ef ("drm/i915: Leave the aliasing-ppgtt size alone")
The second is strange because git complain about the
empty commit.
Anyway, if any is needed could you please provide those
through your ickle/dif please?
Also looking there I noticed one commit pending:
drm/i915: Split i915_active.mutex into an irq-safe spinlock for the rbtree
It seems that we do need that, but I wonder why dim is not getting
itself. Also it conflicts on top of current drm-intel-fixes so
I'd need a rebased version anyway please!
Thanks a lot,
Rodrigo.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
WARNING: multiple messages have this Message-ID (diff)
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] Failed cherry-picks on drm-intel-fixes
Date: Mon, 18 Nov 2019 09:39:55 -0800 [thread overview]
Message-ID: <20191118173955.GA13156@intel.com> (raw)
Message-ID: <20191118173955.ur2g5AP66170ToFjcPFlHU03gVyqmK8spZWftd6bv70@z> (raw)
Hi Chris,
2 fixes failed on this cherry-pick round.
8eb4704b124c ("drm/i915: Protect request peeking with RCU")
3cac195875ef ("drm/i915: Leave the aliasing-ppgtt size alone")
The second is strange because git complain about the
empty commit.
Anyway, if any is needed could you please provide those
through your ickle/dif please?
Also looking there I noticed one commit pending:
drm/i915: Split i915_active.mutex into an irq-safe spinlock for the rbtree
It seems that we do need that, but I wonder why dim is not getting
itself. Also it conflicts on top of current drm-intel-fixes so
I'd need a rebased version anyway please!
Thanks a lot,
Rodrigo.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2019-11-18 17:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-18 17:39 Rodrigo Vivi [this message]
2019-11-18 17:39 ` [Intel-gfx] Failed cherry-picks on drm-intel-fixes Rodrigo Vivi
2019-11-18 17:48 ` Chris Wilson
2019-11-18 17:48 ` [Intel-gfx] " Chris Wilson
2019-11-18 18:13 ` Chris Wilson
2019-11-18 18:13 ` [Intel-gfx] " Chris Wilson
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=20191118173955.GA13156@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.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.