From: Christoph Hellwig <hch@ns.caldera.de>
To: chrisc@shad0w.org.uk (Chris Crowther)
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] CDP handler for linux
Date: Tue, 14 Aug 2001 21:30:23 +0200 [thread overview]
Message-ID: <200108141930.f7EJUNj01929@ns.caldera.de> (raw)
In-Reply-To: <Pine.LNX.4.33.0108141934130.3283-100000@monolith.shad0w.org.uk>
Hi Chis,
In article <Pine.LNX.4.33.0108141934130.3283-100000@monolith.shad0w.org.uk> you wrote:
> I've been working on an addition to the kernel over the past
> couple of days that enables the kernel to interpret CDP (Cisco Discovery
> Protocol) packets which can be transmited by various pieces of Cisco kit.
>
> I've got it to the stage where it will read neighbors packets and
> display them via a /proc/net entry, but I've only really tested it with
> the router I have access to here, so I was wondering:
> --- linux-2.4/net/cdp/Makefile Thu Jan 1 01:00:00 1970
> +++ linux-2.4.7-cdp/net/cdp/Makefile Thu Aug 9 12:11:44 2001
> @@ -0,0 +1,25 @@
> +#
> +# Makefile for the Linux CDP layer.
> +#
> +# Note! Dependencies are done automagically by 'make dep', which also
> +# removes any old dependencies. DON'T put your own dependencies here
> +# unless it's something special (ie not a .c file).
> +#
> +# Note 2! The CFLAGS definition is now in the main makefile...
> +
> +# We only get in/to here if CONFIG_CDP = 'y' or 'm'
> +
> +O_TARGET := cdp.o
> +
> +export-objs = af_cdp.o
You don't export symbols, so you don't need to add your object to export-objs.
> +
> +obj-y := af_cdp.o
> +
> +ifeq ($(CONFIG_CDP),m)
> + obj-m += $(O_TARGET)
> +endif
> +
> +include $(TOPDIR)/Rules.make
> +
> +tar:
> + tar -cvf /dev/f1 .
Kill this tar rule, please :)
> diff -urN -X dontdiff linux-2.4/net/cdp/af_cdp.c linux-2.4.7-cdp/net/cdp/af_cdp.c
> --- linux-2.4/net/cdp/af_cdp.c Thu Jan 1 01:00:00 1970
> +++ linux-2.4.7-cdp/net/cdp/af_cdp.c Tue Aug 14 19:14:11 2001
> @@ -0,0 +1,509 @@
> +/*
> + * Implements a CDP handler.
> + *
> + * This code is derived from protocol specifications by Cisco Systems
> + * and various code culled from the Kernel source tree, mostly the IPX
> + * code.
> + *
> + * Unless otherwise commented, all revisions by Chris Crowther.
> + *
> + * Revision 0.1.0: Initial coding.
> + * Revision 0.1.1: Incoming CDP packet handling working, prefix's and addresses
> + * need handling still.
> + *
> + * Portions Copyright (c) 2001 Chris Crowther.
I think it's all yours, isn't it?
Besides this little nitpicks I'd like to give you the advise to send this
to linuxnetdev, too.
Christoph
--
Whip me. Beat me. Make me maintain AIX.
next prev parent reply other threads:[~2001-08-14 19:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-14 18:47 Chris Crowther
2001-08-14 19:30 ` Christoph Hellwig [this message]
2001-08-14 19:56 ` Chris Crowther
2001-08-14 20:59 ` Bjoern A. Zeeb
2001-08-14 20:17 ` Alan Cox
2001-08-14 20:54 ` Chris Crowther
2001-08-14 20:59 ` Alan Cox
2001-08-15 5:48 ` David Luyer
2001-08-14 21:07 ` Bjoern A. Zeeb
2001-08-14 21:32 ` Dan Hollis
2001-08-14 22:46 ` David S. Miller
2001-08-15 9:13 ` Chris Crowther
2001-08-15 9:23 ` David S. Miller
2001-08-15 9:32 ` Chris Crowther
2001-08-14 20:19 ` Dan Hollis
[not found] <Pine.LNX.4.33.0108141934130.3283-100000@monolith.shad0w.or g.uk>
2001-08-14 23:01 ` Lincoln Dale
2001-08-15 16:14 ` Chris Crowther
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=200108141930.f7EJUNj01929@ns.caldera.de \
--to=hch@ns.caldera.de \
--cc=chrisc@shad0w.org.uk \
--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
all inboxes | Powered by JetHome®