From: Rasmus Andersen <rasmus@jaquet.dk>
To: linux-kernel@vger.kernel.org
Subject: [PATCH] net/802/transit/Makefile (240-test13-pre1)
Date: Thu, 14 Dec 2000 21:23:28 +0100 [thread overview]
Message-ID: <20001214212328.A600@jaquet.dk> (raw)
Hi.
I'm not quite sure whom this patch belongs to but I hope that it ends up
in the right hands by way of linux-kernel.
In order to get 'make dep' to make it through my tree (240-test13-pre1) I
need the following patch applied:
diff -Naur linux-240-t13-pre1-clean/net/802/transit/Makefile linux/net/802/transit/Makefile
--- linux-240-t13-pre1-clean/net/802/transit/Makefile Thu Dec 12 15:54:22 1996
+++ linux/net/802/transit/Makefile Thu Dec 14 21:07:39 2000
@@ -1,3 +1,5 @@
+include $(TOPDIR)/Rules.make
+
all: pdutr.h timertr.h
pdutr.h: pdutr.pre compile.awk
--
Regards,
Rasmus(rasmus@jaquet.dk)
Even if you're on the right track, you'll get run over if you just sit there.
-- Will Rogers
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
reply other threads:[~2000-12-14 20:54 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=20001214212328.A600@jaquet.dk \
--to=rasmus@jaquet.dk \
--cc=linux-kernel@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 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).