From: "David S. Miller" <davem@redhat.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: bunk@fs.tum.de, acme@conectiva.com.br, netdev@oss.sgi.com,
pekkas@netcore.fi, lksctp-developers@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: RFC: [2.6 patch] disallow modular IPv6
Date: Tue, 30 Sep 2003 01:51:25 -0700 [thread overview]
Message-ID: <20030930015125.5de36d97.davem@redhat.com> (raw)
In-Reply-To: <1064911360.21551.49.camel@hades.cambridge.redhat.com>
On Tue, 30 Sep 2003 09:42:41 +0100
David Woodhouse <dwmw2@infradead.org> wrote:
> 'make modules' should make the modules. If for some reason this really
> does require the core kernel image to be present and up to date, perhaps
> for modversions, then I agree that it should also rebuild the core
> kernel.
So it's OK for modversions to make modules depend upon the main kernel
image, but it's not OK for ipv6 to do the same exact thing. Is this
what you're saying?
> If there's no actual dependency on the core kernel image, however, then
> it should not be rebuilt for 'make modules'. If 'make modules' was
> equivalent to 'make all' then it should not exist at all.
I don't see how you can say that modversions can create this module
dependency upon the kernel image, but ipv6 is not allowed to.
And this doesn't turn 'make modules' into the same thing as 'make all'.
It will still behave differently in a lot of situations.
next prev parent reply other threads:[~2003-09-30 8:51 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-28 22:59 RFC: [2.6 patch] disallow modular IPv6 Adrian Bunk
2003-09-28 23:18 ` Arnaldo Carvalho de Melo
2003-09-28 23:24 ` Adrian Bunk
2003-09-28 23:39 ` Arnaldo Carvalho de Melo
2003-09-28 23:47 ` Arnaldo Carvalho de Melo
2003-09-29 0:14 ` Adrian Bunk
2003-09-29 0:32 ` Arnaldo Carvalho de Melo
2003-09-29 9:02 ` David Woodhouse
2003-09-29 14:15 ` Arnaldo Carvalho de Melo
2003-09-29 14:28 ` Jan Evert van Grootheest
2003-09-29 14:29 ` David Woodhouse
2003-09-29 14:38 ` Valdis.Kletnieks
2003-09-29 14:46 ` David Woodhouse
2003-09-30 5:17 ` David S. Miller
2003-09-30 6:31 ` David Woodhouse
2003-10-01 19:47 ` Guennadi Liakhovetski
2003-09-30 5:11 ` David S. Miller
2003-09-30 13:37 ` Adrian Bunk
2003-09-30 15:04 ` Arnaldo Carvalho de Melo
2003-10-01 6:39 ` David S. Miller
2003-09-30 5:09 ` David S. Miller
2003-09-30 6:32 ` David Woodhouse
2003-09-30 7:03 ` David S. Miller
2003-09-30 7:39 ` David Woodhouse
2003-09-30 8:08 ` David S. Miller
2003-09-30 8:26 ` David Woodhouse
2003-09-30 8:30 ` David S. Miller
2003-09-30 8:42 ` David Woodhouse
2003-09-30 8:51 ` David S. Miller [this message]
2003-09-30 9:14 ` David Woodhouse
2003-09-30 9:17 ` David Woodhouse
2003-09-30 9:24 ` David S. Miller
2003-09-30 9:57 ` Sam Ravnborg
2003-09-30 10:02 ` David Woodhouse
2003-09-30 10:01 ` David S. Miller
2003-09-30 10:14 ` David Woodhouse
2003-09-30 11:39 ` Sam Ravnborg
2003-09-30 13:44 ` Dana Lacoste
2003-09-30 13:50 ` Kai Germaschewski
2003-09-30 15:13 ` Richard Guy Briggs
2003-09-30 14:21 ` Theodore Ts'o
2003-09-30 14:51 ` David Woodhouse
2003-09-30 12:06 ` Olivier Galibert
2003-09-29 6:29 ` Pekka Savola
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=20030930015125.5de36d97.davem@redhat.com \
--to=davem@redhat.com \
--cc=acme@conectiva.com.br \
--cc=bunk@fs.tum.de \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lksctp-developers@lists.sourceforge.net \
--cc=netdev@oss.sgi.com \
--cc=pekkas@netcore.fi \
/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).