From: Richard Purdie <rpurdie@linux.intel.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Dave Airlie <airlied@linux.ie>, linux-next@vger.kernel.org
Subject: Re: linux-next: drm tree build failure
Date: Mon, 12 Jan 2009 17:13:19 +0000 [thread overview]
Message-ID: <1231780399.12963.47.camel@dax.rpnet.com> (raw)
In-Reply-To: <20090112141249.f9d72f6c.sfr@canb.auug.org.au>
On Mon, 2009-01-12 at 14:12 +1100, Stephen Rothwell wrote:
> Today's linux-next build (x86_64 allmodconfig) failed like this:
>
> drivers/gpu/drm/i915/i915_dma.c: In function 'i915_initialize':
> drivers/gpu/drm/i915/i915_dma.c:183: error: 'drm_i915_init_t' has no member named 'sarea_priv'
>
> Immediate cause is commit 21edb2690395e7a5281d0d5b5b8a9362491c9879
> ("drm/i915: setup sarea properly in master_priv").
>
> I have dropped the drm tree for today.
I've also mentioned to this to Dave and there is a fixed version of that
patch in his inbox.
Cheers,
Richard
next prev parent reply other threads:[~2009-01-12 17:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-12 3:12 linux-next: drm tree build failure Stephen Rothwell
2009-01-12 17:13 ` Richard Purdie [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-02-04 5:33 Stephen Rothwell
2009-02-04 8:35 ` Dave Airlie
2008-07-10 6:27 Stephen Rothwell
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=1231780399.12963.47.camel@dax.rpnet.com \
--to=rpurdie@linux.intel.com \
--cc=airlied@linux.ie \
--cc=linux-next@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox