From: "Sérgio Basto" <sergio@serjux•com>
To: Randy Dunlap <rdunlap@xenotime•net>
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 17:16:57 +0000 [thread overview]
Message-ID: <1322673417.31541.1.camel@segulix> (raw)
In-Reply-To: <4ED5417C.1030908@xenotime.net>
Randy, not dri-devel@lists•sourceforge.net, anymore
now is dri-devel@lists•freedesktop.org
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.
>
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure
> contains a definitive record of customers, application performance,
> security threats, fraudulent activity, and more. Splunk takes this
> data and makes sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-novd2d
> -- _______________________________________________ Dri-devel mailing list Dri-devel@lists•sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
--
Sérgio M. B.
next prev parent reply other threads:[~2011-11-30 17:16 UTC|newest]
Thread overview: 5+ 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-30 17:16 ` Sérgio Basto [this message]
2011-11-30 18:18 ` Randy Dunlap
2011-11-30 17:51 ` Dave Airlie
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=1322673417.31541.1.camel@segulix \
--to=sergio@serjux$(echo .)com \
--cc=dri-devel@lists$(echo .)freedesktop.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=rdunlap@xenotime$(echo .)net \
--cc=sfr@canb$(echo .)auug.org.au \
/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