From: Pekka Paalanen <ppaalanen@gmail.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Daniel Vetter <daniel.vetter@intel.com>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
Sean Paul <seanpaul@chromium.org>,
DRI Development <dri-devel@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH 2/2] drm/atomic: debug output for EBUSY
Date: Fri, 25 Sep 2020 12:11:47 +0300 [thread overview]
Message-ID: <20200925121147.791ea941@eldfell> (raw)
In-Reply-To: <20200925084651.3250104-2-daniel.vetter@ffwll.ch>
[-- Attachment #1.1: Type: text/plain, Size: 378 bytes --]
On Fri, 25 Sep 2020 10:46:51 +0200
Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
> Hopefully we'll have the drm crash recorder RSN, but meanwhile
> compositors would like to know a bit better why they get an EBUSY.
>
> v2: Move misplaced hunk to the right patch (Pekka)
Hi,
both patches
Acked-by: Pekka Paalanen <pekka.paalanen@collabora.com>
Thanks,
pq
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-09-25 9:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-25 8:46 [Intel-gfx] [PATCH 1/2] drm/atomic: document and enforce rules around "spurious" EBUSY Daniel Vetter
2020-09-25 8:46 ` [Intel-gfx] [PATCH 2/2] drm/atomic: debug output for EBUSY Daniel Vetter
2020-09-25 9:11 ` Pekka Paalanen [this message]
2020-09-29 15:48 ` Daniel Stone
2020-10-08 9:31 ` Daniel Vetter
2020-09-25 10:50 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/2] drm/atomic: document and enforce rules around "spurious" EBUSY Patchwork
2020-09-25 11:12 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-09-25 14:24 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2021-11-05 20:47 ` [Intel-gfx] [PATCH 1/2] " Kazlauskas, Nicholas
2021-11-08 15:07 ` Daniel Vetter
2021-11-08 15:32 ` Kazlauskas, Nicholas
2021-11-08 15:41 ` Daniel Vetter
-- strict thread matches above, loose matches on Subject: below --
2020-09-23 10:57 Daniel Vetter
2020-09-23 10:57 ` [Intel-gfx] [PATCH 2/2] drm/atomic: debug output for EBUSY Daniel Vetter
2020-09-25 8:27 ` Pekka Paalanen
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=20200925121147.791ea941@eldfell \
--to=ppaalanen@gmail.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=seanpaul@chromium.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox