From: Sam Ravnborg <sam@ravnborg.org>
To: Paul Mundt <lethal@linux-sh.org>, Adrian Bunk <bunk@kernel.org>,
linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: sh O= builds broken
Date: Fri, 01 Aug 2008 22:12:22 +0000 [thread overview]
Message-ID: <20080801221222.GA14125@uranus.ravnborg.org> (raw)
In-Reply-To: <20080801215338.GC13448@linux-sh.org>
On Sat, Aug 02, 2008 at 06:53:38AM +0900, Paul Mundt wrote:
> >
> Ok, so this is what I get for moving the auto-generated header outside of
> include/asm-sh.. it seemed like a good idea at the time.
Ups - I should have caught that when I reviewd your initial patch.
kbuild does on purpose not fiddle with the path in the inital
include specification.
Sam
WARNING: multiple messages have this Message-ID (diff)
From: Sam Ravnborg <sam@ravnborg.org>
To: Paul Mundt <lethal@linux-sh.org>, Adrian Bunk <bunk@kernel.org>,
linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: sh O= builds broken
Date: Sat, 2 Aug 2008 00:12:22 +0200 [thread overview]
Message-ID: <20080801221222.GA14125@uranus.ravnborg.org> (raw)
In-Reply-To: <20080801215338.GC13448@linux-sh.org>
On Sat, Aug 02, 2008 at 06:53:38AM +0900, Paul Mundt wrote:
> >
> Ok, so this is what I get for moving the auto-generated header outside of
> include/asm-sh.. it seemed like a good idea at the time.
Ups - I should have caught that when I reviewd your initial patch.
kbuild does on purpose not fiddle with the path in the inital
include specification.
Sam
next prev parent reply other threads:[~2008-08-01 22:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-01 21:27 sh O= builds broken Adrian Bunk
2008-08-01 21:27 ` Adrian Bunk
2008-08-01 21:53 ` Paul Mundt
2008-08-01 21:53 ` Paul Mundt
2008-08-01 22:03 ` Adrian Bunk
2008-08-01 22:03 ` Adrian Bunk
2008-08-01 22:12 ` Sam Ravnborg [this message]
2008-08-01 22:12 ` Sam Ravnborg
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=20080801221222.GA14125@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=bunk@kernel.org \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.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.