From: Jan Kiszka <jan.kiszka@domain.hid>
To: Xenomai-core@domain.hid
Subject: [Xenomai-core] [PATCH] prepare-kernel: get rid of arch_makefile
Date: Sat, 29 Dec 2007 21:33:27 +0100 [thread overview]
Message-ID: <4776AF17.3070102@domain.hid> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 282 bytes --]
For me there appears to be neither a need for nor a benefit of patching
the sub-arch Makefile instead of the top one. The big drawback is that
you have to re-prepare the kernel when you switch between 32 and 64-bit
mode at .config level. So let's kill this special case.
Jan
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1.2: kill-arch_makefile.patch --]
[-- Type: text/x-patch; name="kill-arch_makefile.patch", Size: 1058 bytes --]
Index: xenomai/scripts/prepare-kernel.sh
===================================================================
--- xenomai/scripts/prepare-kernel.sh (Revision 3348)
+++ xenomai/scripts/prepare-kernel.sh (Arbeitskopie)
@@ -334,14 +334,11 @@
fi
done
-arch_makefile=Makefile
-
# i386 and x86_64 architectures are merged since 2.6.24. The resulting
# combo is available from arch/x86 when present.
if test "$xenomai_arch" = x86; then
if test -d $linux_tree/arch/x86; then
linux_arch=x86
- arch_makefile=Makefile_$x86_arch_bits
fi
fi
@@ -433,9 +430,9 @@
patch_append init/Kconfig
fi
- if ! grep -q CONFIG_XENOMAI $linux_tree/arch/$linux_arch/$arch_makefile; then
+ if ! grep -q CONFIG_XENOMAI $linux_tree/arch/$linux_arch/Makefile; then
p="drivers-\$(CONFIG_XENOMAI) += arch/$linux_arch/xenomai/"
- ( echo ; echo $p ) | patch_append arch/$linux_arch/$arch_makefile
+ ( echo ; echo $p ) | patch_append arch/$linux_arch/Makefile
fi
patch_architecture_specific="n"
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 254 bytes --]
reply other threads:[~2007-12-29 20:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4776AF17.3070102@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=Xenomai-core@domain.hid \
/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.