From: Randy Dunlap <rdunlap@xenotime.net>
To: "Sérgio Basto" <sergio@serjux.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: linux-next: Tree for Nov 29 (drm)
Date: Wed, 30 Nov 2011 10:18:47 -0800 [thread overview]
Message-ID: <4ED67387.90902@xenotime.net> (raw)
In-Reply-To: <1322673417.31541.1.camel@segulix>
On 11/30/2011 09:16 AM, Sérgio Basto wrote:
> Randy, not dri-devel@lists.sourceforge.net, anymore
> now is dri-devel@lists.freedesktop.org
Argh, thanks.
That was thunderbird trying to be too helpful. :(
> On Tue, 2011-11-29 at 12:33 -0800, Randy Dunlap wrote:
>> On 11/28/2011 08:20 PM, Stephen Rothwell wrote:
>>> Hi all,
>>>
>>> Changes since 20111128:
>>>
>>> The drm tree lost its build failure but gained another for which I
>>> applied a patch.
>>
>>
>> ERROR: "drm_helper_get_fb_bpp_depth" [drivers/gpu/drm/vmwgfx/vmwgfx.ko] undefined!
>>
>> Full x86_64 randconfig file is attached.
>>
>> ------------------------------------------------------------------------------
>> -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
>
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2011-11-30 17:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-29 4:20 linux-next: Tree for Nov 29 Stephen Rothwell
2011-11-29 20:33 ` linux-next: Tree for Nov 29 (drm) Randy Dunlap
2011-11-29 20:33 ` Randy Dunlap
2011-11-30 17:16 ` Sérgio Basto
2011-11-30 18:18 ` Randy Dunlap [this message]
2011-11-30 17:51 ` Dave Airlie
2011-11-29 20:33 ` Randy Dunlap
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=4ED67387.90902@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sergio@serjux.com \
--cc=sfr@canb.auug.org.au \
/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.