From: "David S. Miller" <davem@davemloft.net>
To: sam@ravnborg.org
Cc: kaber@trash.net, bunk@stusta.de, evil@g-house.de,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
zippel@linux-m68k.org
Subject: Re: [2.6 patch] do not select NET_CLS
Date: Tue, 22 Nov 2005 15:00:41 -0800 (PST) [thread overview]
Message-ID: <20051122.150041.90521592.davem@davemloft.net> (raw)
In-Reply-To: <20051122224914.GA17575@mars.ravnborg.org>
From: Sam Ravnborg <sam@ravnborg.org>
Date: Tue, 22 Nov 2005 23:49:14 +0100
> On Tue, Nov 22, 2005 at 02:37:13PM -0800, David S. Miller wrote:
> >
> > One thing we can do to prevent human
> > mistakes, is to make the "make modules" pass do a quick "is vmlinux
> > uptodate?" check, and if not print out an error message explaining the
> > situation and aborting the "make modules" attempt.
>
> I do not quite follow you here.
If the user tries to do a "make modules" without first rebuilding
their kernel image, then the make will fail if the dependencies
are not satisfied for the main kernel image and it is thus not
up to date.
next prev parent reply other threads:[~2005-11-22 23:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-16 23:10 2.6.15-rc1: NET_CLS_U32 not working? Christian
2005-11-16 23:58 ` Adrian Bunk
2005-11-17 0:06 ` Christian
2005-11-17 15:57 ` Christian
2005-11-21 15:59 ` [2.6 patch] do not select NET_CLS Adrian Bunk
2005-11-21 16:16 ` Patrick McHardy
2005-11-22 22:37 ` David S. Miller
2005-11-22 22:49 ` Sam Ravnborg
2005-11-22 23:00 ` David S. Miller [this message]
2005-11-23 5:57 ` Sam Ravnborg
2005-11-24 2:13 ` Randy.Dunlap
2005-11-24 5:40 ` Sam Ravnborg
2005-11-22 23:12 ` Adrian Bunk
2005-11-23 10:27 ` Thomas Graf
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=20051122.150041.90521592.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bunk@stusta.de \
--cc=evil@g-house.de \
--cc=kaber@trash.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=zippel@linux-m68k.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
Powered by JetHome