From: Thierry Reding <thierry.reding@gmail.com>
To: Liviu Dudau <Liviu.Dudau@arm.com>
Cc: DRI devel <dri-devel@lists.freedesktop.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: drm: Bogus WARN() in drm_atomic_helper_update_legacy_modeset_state() ?
Date: Tue, 10 Nov 2015 17:56:15 +0100 [thread overview]
Message-ID: <20151110165615.GB27962@ulmo> (raw)
In-Reply-To: <20151110150102.GP963@e106497-lin.cambridge.arm.com>
[-- Attachment #1.1: Type: text/plain, Size: 342 bytes --]
On Tue, Nov 10, 2015 at 03:01:03PM +0000, Liviu Dudau wrote:
> Hello,
>
> When booting my Juno board with the HDLCD driver that I have converted to
> atomic operations I'm getting the following warning:
Perhaps you can provide pointers to the source code, that might make it
easier for people to spot what's going wrong.
Thierry
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
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: Thierry Reding <thierry.reding@gmail.com>
To: Liviu Dudau <Liviu.Dudau@arm.com>
Cc: Daniel Vetter <daniel@ffwll.ch>, David Airlie <airlied@linux.ie>,
Rob Clark <robdclark@gmail.com>,
DRI devel <dri-devel@lists.freedesktop.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: drm: Bogus WARN() in drm_atomic_helper_update_legacy_modeset_state() ?
Date: Tue, 10 Nov 2015 17:56:15 +0100 [thread overview]
Message-ID: <20151110165615.GB27962@ulmo> (raw)
In-Reply-To: <20151110150102.GP963@e106497-lin.cambridge.arm.com>
[-- Attachment #1: Type: text/plain, Size: 342 bytes --]
On Tue, Nov 10, 2015 at 03:01:03PM +0000, Liviu Dudau wrote:
> Hello,
>
> When booting my Juno board with the HDLCD driver that I have converted to
> atomic operations I'm getting the following warning:
Perhaps you can provide pointers to the source code, that might make it
easier for people to spot what's going wrong.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-11-10 16:56 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-10 15:01 drm: Bogus WARN() in drm_atomic_helper_update_legacy_modeset_state() ? Liviu Dudau
2015-11-10 15:01 ` Liviu Dudau
2015-11-10 16:56 ` Thierry Reding [this message]
2015-11-10 16:56 ` Thierry Reding
2015-11-11 16:09 ` Liviu Dudau
2015-11-11 16:09 ` Liviu Dudau
2015-11-12 12:16 ` Thierry Reding
2015-11-12 12:16 ` Thierry Reding
2015-11-12 13:57 ` Liviu Dudau
2015-11-12 13:57 ` Liviu Dudau
2015-11-12 16:28 ` Thierry Reding
2015-11-12 16:28 ` Thierry Reding
2015-11-16 16:30 ` Daniel Vetter
2015-11-16 16:30 ` Daniel Vetter
2015-11-12 6:27 ` Mark yao
2015-11-12 6:34 ` Mark yao
2015-11-12 10:34 ` Liviu Dudau
2015-11-12 10:34 ` Liviu Dudau
2015-11-12 10:52 ` Mark yao
2015-11-12 10:52 ` Mark yao
2015-11-12 12:26 ` Thierry Reding
2015-11-12 12:26 ` Thierry Reding
2015-11-12 8:32 ` Mark yao
2015-11-12 10:36 ` Liviu Dudau
2015-11-12 10:36 ` Liviu Dudau
2015-11-12 10:49 ` Mark yao
2015-11-12 10:49 ` Mark yao
2015-11-12 13:34 ` Thierry Reding
2015-11-12 13:34 ` Thierry Reding
2015-11-12 14:03 ` Liviu Dudau
2015-11-12 16:12 ` Thierry Reding
2015-11-12 16:12 ` Thierry Reding
2015-11-12 16:48 ` Liviu Dudau
2015-11-12 16:48 ` Liviu Dudau
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=20151110165615.GB27962@ulmo \
--to=thierry.reding@gmail.com \
--cc=Liviu.Dudau@arm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.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.