From: Sam Ravnborg <sam@ravnborg.org>
To: Jesper Nilsson <jesper.nilsson@axis.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Mikael Starvik <mikael.starvik@axis.com>,
linux-kernel@vger.kernel.org, Jan Dittmer <jdi@l4x.org>
Subject: Re: [PATCH] CRIS: avoid using arch links in Kconfig
Date: Wed, 21 Nov 2007 10:55:05 +0100 [thread overview]
Message-ID: <20071121095505.GA1070@uranus.ravnborg.org> (raw)
In-Reply-To: <20071121090346.GD14797@axis.com>
On Wed, Nov 21, 2007 at 10:03:46AM +0100, Jesper Nilsson wrote:
> Improve including of architecture dependent Kconfig files.
>
> - Always include the architecture dependent Kconfig files.
> - Wrap architecture dependent Kconfig files inside an appropriate
> "if ETRAX_ARCH_Vxx" block.
>
> This makes it possible to run the configuration even without the arch links,
> which are created later in the build process.
Looks good!
Getting rid of magic symlinks is always good - especially in the early
config phase.
Sam
prev parent reply other threads:[~2007-11-21 9:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-21 9:03 [PATCH] CRIS: avoid using arch links in Kconfig Jesper Nilsson
2007-11-21 9:55 ` Sam Ravnborg [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=20071121095505.GA1070@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=akpm@linux-foundation.org \
--cc=jdi@l4x.org \
--cc=jesper.nilsson@axis.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikael.starvik@axis.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.