From: "Michel Dänzer" <michel@tungstengraphics.com>
To: Dave Airlie <airlied@linux.ie>
Cc: linuxppc-dev@ozlabs.org, dri-devel@lists.sourceforge.net
Subject: Re: DRM git vs. Linux 2.6.17
Date: Wed, 26 Jul 2006 16:38:46 +0200 [thread overview]
Message-ID: <1153924726.20778.116.camel@thor.lorrainebruecke.local> (raw)
In-Reply-To: <1153899787.20778.99.camel@thor.lorrainebruecke.local>
On Wed, 2006-07-26 at 09:43 +0200, Michel Dänzer wrote:
>
> I suspect this might be a PPC specific kernel build system issue related
> to Modules.symvers,
Actually, now that my x86_64 box is back up, it happens there as well,
so maybe it's related to the Debian toolchain or kernel packaging.
Apologies to linuxppc-dev for the false alarm.
--
Earthling Michel Dänzer | http://tungstengraphics.com
Libre software enthusiast | Debian, X and DRI developer
prev parent reply other threads:[~2006-07-26 14:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1153818665.20778.82.camel@thor.lorrainebruecke.local>
[not found] ` <Pine.LNX.4.64.0607251030220.30301@skynet.skynet.ie>
2006-07-26 7:43 ` DRM git vs. Linux 2.6.17 Michel Dänzer
2006-07-26 14:38 ` Michel Dänzer [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=1153924726.20778.116.camel@thor.lorrainebruecke.local \
--to=michel@tungstengraphics.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.sourceforge.net \
--cc=linuxppc-dev@ozlabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).