From: Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>
To: chas williams <chas@locutus.cmf.nrl.navy.mil>
Cc: "David S. Miller" <davem@redhat.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][ATM] make atm (and clip) modular + try_module_get()
Date: Mon, 3 Mar 2003 18:28:20 -0600 (CST) [thread overview]
Message-ID: <Pine.LNX.4.44.0303031825240.16397-100000@chaos.physics.uiowa.edu> (raw)
In-Reply-To: <200303032220.h23MKVGi028878@locutus.cmf.nrl.navy.mil>
On Mon, 3 Mar 2003, chas williams wrote:
> Index: linux/net/atm/Makefile
> ===================================================================
> RCS file: /home/chas/CVSROOT/linux/net/atm/Makefile,v
> retrieving revision 1.1.1.1
> diff -u -r1.1.1.1 Makefile
> --- linux/net/atm/Makefile 20 Feb 2003 13:46:30 -0000 1.1.1.1
> +++ linux/net/atm/Makefile 3 Mar 2003 16:51:03 -0000
> @@ -3,12 +3,15 @@
> #
>
> mpoa-objs := mpc.o mpoa_caches.o mpoa_proc.o
> +atm-objs := addr.o pvc.o signaling.o svc.o common.o atm_misc.o raw.o resources.o
>
> -obj-$(CONFIG_ATM) := addr.o pvc.o signaling.o svc.o common.o atm_misc.o raw.o resources.o
> +obj-$(CONFIG_ATM) += atm.o
>
> -obj-$(CONFIG_ATM_CLIP) += clip.o ipcommon.o
> -obj-$(CONFIG_NET_SCH_ATM) += ipcommon.o
> -obj-$(CONFIG_PROC_FS) += proc.o
> +obj-$(CONFIG_ATM_CLIP) += clip.o
> +# obj-$(CONFIG_NET_SCH_ATM) += ipcommon.o
> +ifeq ($(CONFIG_PROC_FS),y)
> +atm-objs += proc.o
> +endif
>
> obj-$(CONFIG_ATM_LANE) += lec.o
> obj-$(CONFIG_ATM_MPOA) += mpoa.o
Not terribly important, but you can write this as:
obj-$(CONFIG_ATM) += atm.o
atm-y += addr.o pvc.o signaling.o svc.o ...
atm-$(CONFIG_PROC_FS) += proc.o
which looks a bit nicer ;)
--Kai
next prev parent reply other threads:[~2003-03-04 0:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-03 22:20 [PATCH][ATM] make atm (and clip) modular + try_module_get() chas williams
2003-03-03 22:26 ` chas williams
2003-03-04 0:28 ` Kai Germaschewski [this message]
2003-03-05 14:43 ` chas williams
2003-03-05 15:58 ` Kai Germaschewski
2003-03-05 16:05 ` chas williams
2003-03-05 16:11 ` Kai Germaschewski
2003-03-05 16:24 ` chas williams
2003-03-05 16:40 ` Kai Germaschewski
2003-03-05 16:26 ` Roman Zippel
2003-03-04 2:07 ` Werner Almesberger
2003-03-05 14:47 ` chas williams
2003-03-05 14:31 ` David S. Miller
2003-03-05 15:08 ` chas williams
2003-03-05 14:53 ` David S. Miller
2003-03-05 15:28 ` chas williams
2003-03-05 15:12 ` David S. Miller
2003-03-05 15:43 ` chas williams
2003-03-05 15:52 ` Werner Almesberger
2003-03-06 20:44 ` chas williams
2003-03-06 21:02 ` Werner Almesberger
2003-03-06 23:36 ` chas williams
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=Pine.LNX.4.44.0303031825240.16397-100000@chaos.physics.uiowa.edu \
--to=kai@tp1.ruhr-uni-bochum.de \
--cc=chas@locutus.cmf.nrl.navy.mil \
--cc=davem@redhat.com \
--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).