From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public•gmane.org>
To: Daniel Vetter <daniel.vetter-/w4YWyX8dFk@public•gmane.org>
Cc: Rob Clark <robdclark-Re5JQEeQqe8AvxtiuMwx3w@public•gmane.org>,
"dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public•gmane.org"
<dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public•gmane.org>,
"linux-tegra-u79uwXL29TY76Z2rM5mHXA@public•gmane.org"
<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public•gmane.org>,
"linux-next-u79uwXL29TY76Z2rM5mHXA@public•gmane.org"
<linux-next-u79uwXL29TY76Z2rM5mHXA@public•gmane.org>,
Mark Zhang <markz-DDmLM1+adcrQT0dZR+AlfA@public•gmane.org>,
Dave Airlie <airlied-Re5JQEeQqe8AvxtiuMwx3w@public•gmane.org>
Subject: Re: Broken build due to 6aed8ec "drm: review locking for drm_fb_helper_restore_fbdev_mode"
Date: Tue, 19 Feb 2013 12:29:38 -0700 [thread overview]
Message-ID: <5123D2A2.5050301@wwwdotorg.org> (raw)
In-Reply-To: <CAKMK7uG=x4ESF_uVUwvK+0kzvsXEgZBtM9Z6_Qrm6keSasoCbA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 02/19/2013 11:56 AM, Daniel Vetter wrote:
> On Tue, Feb 19, 2013 at 6:48 PM, Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public•gmane.org> wrote:
>> Daniel,
>>
>> Commit 6aed8ec "drm: review locking for
>> drm_fb_helper_restore_fbdev_mode" (now in next-20130218 and later)
>> causes build failures for tegra_defconfig. The issue is this part of the
>> patch:
>
> You need to yell at Dave Airlie:
>
> https://patchwork.kernel.org/patch/2162391/
Ah, thanks, that solves it.
I guess that was too new for Google to find, and I'm not on dri-devel so
it wasn't in my mailbox.
prev parent reply other threads:[~2013-02-19 19:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-19 17:48 Broken build due to 6aed8ec "drm: review locking for drm_fb_helper_restore_fbdev_mode" Stephen Warren
2013-02-19 18:56 ` Daniel Vetter
[not found] ` <CAKMK7uG=x4ESF_uVUwvK+0kzvsXEgZBtM9Z6_Qrm6keSasoCbA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-02-19 19:29 ` Stephen Warren [this message]
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=5123D2A2.5050301@wwwdotorg.org \
--to=swarren-3lzwwm7+weoh9zmkesr00q@public$(echo .)gmane.org \
--cc=airlied-Re5JQEeQqe8AvxtiuMwx3w@public$(echo .)gmane.org \
--cc=daniel.vetter-/w4YWyX8dFk@public$(echo .)gmane.org \
--cc=dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public$(echo .)gmane.org \
--cc=linux-next-u79uwXL29TY76Z2rM5mHXA@public$(echo .)gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public$(echo .)gmane.org \
--cc=markz-DDmLM1+adcrQT0dZR+AlfA@public$(echo .)gmane.org \
--cc=robdclark-Re5JQEeQqe8AvxtiuMwx3w@public$(echo .)gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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