From: Ian Campbell <Ian.Campbell@XenSource.com>
To: Gerd Hoffmann <kraxel@suse.de>
Cc: Xen devel list <xen-devel@lists.xensource.com>
Subject: Re: BUG: make O= broken
Date: Thu, 07 Dec 2006 11:08:46 +0000 [thread overview]
Message-ID: <1165489726.9694.148.camel@localhost.localdomain> (raw)
In-Reply-To: <4577F450.6010804@suse.de>
On Thu, 2006-12-07 at 12:00 +0100, Gerd Hoffmann wrote:
> I've tried to turn the sparse tree into a big patch (is there an easy
> way to do this btw?).
make linux-2.6-xen.patch should give you a patch against the upstream
kernel, is that what you are looking for?
> Documentation/dontdiff excludes too much giving
> me a incomplete xenlinux tree, which in turn generated build errors
> looking much like it takes the wrong (native) include files. I've seen
> that in the past with O=, so I blamed it first ...
That's strange -- I wouldn't expect the sparse tree to add anything
which would be listed in dontdiff. Are the symlinks into the sparse tree
confusing diff perhaps?
Ian.
next prev parent reply other threads:[~2006-12-07 11:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-07 10:19 BUG: make O= broken Gerd Hoffmann
2006-12-07 10:32 ` Ian Campbell
2006-12-07 11:00 ` Gerd Hoffmann
2006-12-07 11:08 ` Ian Campbell [this message]
2006-12-07 11:18 ` Gerd Hoffmann
2006-12-07 13:18 ` Muli Ben-Yehuda
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=1165489726.9694.148.camel@localhost.localdomain \
--to=ian.campbell@xensource.com \
--cc=kraxel@suse.de \
--cc=xen-devel@lists.xensource.com \
/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.