From: Simon Ser <contact@emersion.fr>
To: Marek Szyprowski <m.szyprowski@samsung.com>
Cc: "dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
'Linux Samsung SOC' <linux-samsung-soc@vger.kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
Sam Ravnborg <sam@ravnborg.org>
Subject: Re: [v2,1/2] drm: convert drm_atomic_uapi.c to new debug helpers
Date: Mon, 16 Nov 2020 09:08:59 +0000 [thread overview]
Message-ID: <9Kr7KSkpWU_eo1ALXztw7ryOMnXwGVye3q_RK-hjpjRGpkdqcq_nVROg8C3OXF3jPxMMOB3XeLrSri8XG0h6IoC-5uyV2JwztiaGZK6gGqw=@emersion.fr> (raw)
In-Reply-To: <87bba2ec-b044-66c8-1fd7-4c01a9e5b791@samsung.com>
On Monday, November 16, 2020 10:06 AM, Marek Szyprowski <m.szyprowski@samsung.com> wrote:
> This patch landed in today's linux-next as commit e3aae683e861 ("drm:
> convert drm_atomic_uapi.c to new debug helpers"). Sadly it breaks
> booting all Exynos based boards. Here is example of the panic log:
Sorry for the inconvenience, my tests didn't trigger this code-path.
I pushed a fix for this in drm-misc-next: 0003b687ee6d ("drm: fix oops
in drm_atomic_set_crtc_for_connector").
WARNING: multiple messages have this Message-ID (diff)
From: Simon Ser <contact@emersion.fr>
To: Marek Szyprowski <m.szyprowski@samsung.com>
Cc: Thomas Zimmermann <tzimmermann@suse.de>,
'Linux Samsung SOC' <linux-samsung-soc@vger.kernel.org>,
Sam Ravnborg <sam@ravnborg.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: Re: [v2,1/2] drm: convert drm_atomic_uapi.c to new debug helpers
Date: Mon, 16 Nov 2020 09:08:59 +0000 [thread overview]
Message-ID: <9Kr7KSkpWU_eo1ALXztw7ryOMnXwGVye3q_RK-hjpjRGpkdqcq_nVROg8C3OXF3jPxMMOB3XeLrSri8XG0h6IoC-5uyV2JwztiaGZK6gGqw=@emersion.fr> (raw)
In-Reply-To: <87bba2ec-b044-66c8-1fd7-4c01a9e5b791@samsung.com>
On Monday, November 16, 2020 10:06 AM, Marek Szyprowski <m.szyprowski@samsung.com> wrote:
> This patch landed in today's linux-next as commit e3aae683e861 ("drm:
> convert drm_atomic_uapi.c to new debug helpers"). Sadly it breaks
> booting all Exynos based boards. Here is example of the panic log:
Sorry for the inconvenience, my tests didn't trigger this code-path.
I pushed a fix for this in drm-misc-next: 0003b687ee6d ("drm: fix oops
in drm_atomic_set_crtc_for_connector").
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-11-16 9:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-11 9:07 [PATCH v2 1/2] drm: convert drm_atomic_uapi.c to new debug helpers Simon Ser
2020-11-11 18:31 ` Sam Ravnborg
[not found] ` <CGME20201116090608eucas1p128a4fa2e03380fe0cffea2f9bc2af816@eucas1p1.samsung.com>
2020-11-16 9:06 ` [v2,1/2] " Marek Szyprowski
2020-11-16 9:06 ` Marek Szyprowski
2020-11-16 9:08 ` Simon Ser [this message]
2020-11-16 9:08 ` Simon Ser
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='9Kr7KSkpWU_eo1ALXztw7ryOMnXwGVye3q_RK-hjpjRGpkdqcq_nVROg8C3OXF3jPxMMOB3XeLrSri8XG0h6IoC-5uyV2JwztiaGZK6gGqw=@emersion.fr' \
--to=contact@emersion.fr \
--cc=dri-devel@lists.freedesktop.org \
--cc=krzk@kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=sam@ravnborg.org \
--cc=tzimmermann@suse.de \
/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.