From: Andi Kleen <ak@suse.de>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Andi Kleen <ak@suse.de>, Paul Mundt <lethal@linux-sh.org>,
torvalds@osdl.org, linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: [PATCH 13/17] 4level support for sh
Date: Mon, 25 Oct 2004 19:26:45 +0200 [thread overview]
Message-ID: <20041025172645.GE9142@wotan.suse.de> (raw)
In-Reply-To: <20041025171604.GJ25154@smtp.west.cox.net>
On Mon, Oct 25, 2004 at 10:16:04AM -0700, Tom Rini wrote:
> On Mon, Oct 25, 2004 at 07:04:01PM +0200, Andi Kleen wrote:
> > On Mon, Oct 25, 2004 at 09:32:11AM -0700, Tom Rini wrote:
> > > On Mon, Oct 25, 2004 at 07:25:10PM +0300, Paul Mundt wrote:
> > > > On Mon, Oct 25, 2004 at 06:09:59PM +0200, Andi Kleen wrote:
> > > > > BTW separate objdir build seems to be totally broken on sh and
> > > > > it adds random bogus symlinks to the source tree when you do
> > > > > that. Perhaps you can fix that too.
> > > > >
> > > > Tom Rini was working on that stuff, I've not tested it myself. I thought
> > > > this was all fixed by now though, Tom?
> > >
> > > The last problem with SH and O= I found was with EMBEDDED_RAMDISK.
> > > Andi, can you be more specific about bogus symlinks ? Unless I broke
> > > something when copying from ARM, it shouldn't have any more, or less,
> > > problems than ARM for include/asm/foo symlinks.
> >
> > I tried a separate objdir compilation which eventually didn't work.
> > But my original source tree had several symlinks and a machtypes.h file
> > now in include/asm-sh*/* which messed up diffs.
>
> Was this stock 2.6.9 or -bk at some point? All of the O= changes went
> in after 2.6.9 went out as part of akpm's first resync.
Stock 2.6.9
-Andi
prev parent reply other threads:[~2004-10-25 17:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-25 7:23 [PATCH 13/17] 4level support for sh Andreas Kleen
2004-10-25 8:22 ` Paul Mundt
2004-10-25 16:09 ` Andi Kleen
2004-10-25 16:25 ` Paul Mundt
2004-10-25 16:32 ` Tom Rini
2004-10-25 17:04 ` Andi Kleen
2004-10-25 17:16 ` Tom Rini
2004-10-25 17:26 ` Andi Kleen [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=20041025172645.GE9142@wotan.suse.de \
--to=ak@suse.de \
--cc=akpm@osdl.org \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=trini@kernel.crashing.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.