From: Alex Riesen <Alexander.Riesen@synopsys.com>
To: Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>
Cc: linux-kernel@vger.kernel.org, trivial@rustcorp.com.au
Subject: [PATCH] 2.5.38+bk: modversions.h generation
Date: Thu, 26 Sep 2002 10:43:49 +0200 [thread overview]
Message-ID: <20020926084349.GA941@riesen-pc.gr05.synopsys.com> (raw)
Hi,
The .ver to #include part can be simplified a bit,
if we can assume everyone uses GNU find.
--- linus.linux-2.5/Makefile 2002-09-23 20:01:26.000000000 +0200
+++ v2.5.38+bk/Makefile 2002-09-26 10:34:10.000000000 +0200
@@ -437,9 +437,7 @@
echo "#define _LINUX_MODVERSIONS_H"; \
echo "#include <linux/modsetver.h>"; \
cd .tmp_export-objs >/dev/null; \
- for f in `find modules -name \*.ver -print | sort`; do \
- echo "#include <linux/$${f}>"; \
- done; \
+ find modules -name \*.ver -printf "#include <linux/%p>\\n" | sort; \
echo "#endif"; \
) > $@.tmp; \
$(update-if-changed)
reply other threads:[~2002-09-26 8:38 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=20020926084349.GA941@riesen-pc.gr05.synopsys.com \
--to=alexander.riesen@synopsys.com \
--cc=kai@tp1.ruhr-uni-bochum.de \
--cc=linux-kernel@vger.kernel.org \
--cc=trivial@rustcorp.com.au \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).