From: Chris Wilson <chris@chris-wilson.co.uk>
To: Sven Joachim <svenjoac@gmx.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Dave Airlie <airlied@redhat.com>,
intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [git pull] i915
Date: Mon, 06 Sep 2010 10:49:56 +0100 [thread overview]
Message-ID: <89k83a$9icvuq@azsmga001.ch.intel.com> (raw)
In-Reply-To: <8739tnw7ax.fsf@turtle.gmx.de>
On Mon, 06 Sep 2010 11:27:34 +0200, Sven Joachim <svenjoac@gmx.de> wrote:
> Sadly, these still do not include a fix for the build failure¹ that
> occurs if CONFIG_DEBUG_FS is not set:
>
> ,----
> | CC [M] drivers/gpu/drm/i915/intel_overlay.o
> | drivers/gpu/drm/i915/intel_overlay.c: In function 'intel_overlay_print_error_state':
> | drivers/gpu/drm/i915/intel_overlay.c:1467: error: implicit declaration of function 'seq_printf'
> | make[4]: *** [drivers/gpu/drm/i915/intel_overlay.o] Error 1
Andrew Morton picked up a patch to fix that, hence why I left it out.
--
Chris Wilson, Intel Open Source Technology Centre
WARNING: multiple messages have this Message-ID (diff)
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Sven Joachim <svenjoac@gmx.de>
Cc: Dave Airlie <airlied@redhat.com>,
intel-gfx@lists.freedesktop.org,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [git pull] i915
Date: Mon, 06 Sep 2010 10:49:56 +0100 [thread overview]
Message-ID: <89k83a$9icvuq@azsmga001.ch.intel.com> (raw)
In-Reply-To: <8739tnw7ax.fsf@turtle.gmx.de>
[-- Attachment #1: Type: text/plain, Size: 625 bytes --]
On Mon, 06 Sep 2010 11:27:34 +0200, Sven Joachim <svenjoac@gmx.de> wrote:
> Sadly, these still do not include a fix for the build failure¹ that
> occurs if CONFIG_DEBUG_FS is not set:
>
> ,----
> | CC [M] drivers/gpu/drm/i915/intel_overlay.o
> | drivers/gpu/drm/i915/intel_overlay.c: In function 'intel_overlay_print_error_state':
> | drivers/gpu/drm/i915/intel_overlay.c:1467: error: implicit declaration of function 'seq_printf'
> | make[4]: *** [drivers/gpu/drm/i915/intel_overlay.o] Error 1
Andrew Morton picked up a patch to fix that, hence why I left it out.
--
Chris Wilson, Intel Open Source Technology Centre
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2010-09-06 9:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-06 8:30 [git pull] i915 Chris Wilson
2010-09-06 8:30 ` Chris Wilson
2010-09-06 9:27 ` Sven Joachim
2010-09-06 9:27 ` Sven Joachim
2010-09-06 9:49 ` Chris Wilson [this message]
2010-09-06 9:49 ` Chris Wilson
2010-09-06 18:32 ` Rafael J. Wysocki
2010-09-07 2:00 ` [Intel-gfx] " Zhenyu Wang
2010-09-07 2:00 ` Zhenyu Wang
2010-09-07 15:22 ` Daniel Vetter
2010-09-07 5:07 ` [Intel-gfx] " Tino Keitel
2010-09-07 5:07 ` Tino Keitel
[not found] ` <AANLkTi=pFSB5AfqXbPNUQUknbnCBwqUHdUVzR6jaZqaQ@mail.gmail.com>
2010-09-07 10:55 ` [git pull v2] i915 Chris Wilson
2010-09-07 10:55 ` Chris Wilson
2010-09-07 20:29 ` Kyle McMartin
2010-09-07 20:52 ` Chris Wilson
2010-09-07 20:52 ` Chris Wilson
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='89k83a$9icvuq@azsmga001.ch.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=airlied@redhat.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=svenjoac@gmx.de \
--cc=torvalds@linux-foundation.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.