From: Denys Vlasenko <vda.linux@googlemail.com>
To: Daniel Walker <dwalker@mvista.com>
Cc: sam@ravnborg.org, kai@germaschewski.name, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] build system: section garbage collection for vmlinux
Date: Thu, 6 Sep 2007 11:57:43 +0100 [thread overview]
Message-ID: <200709061157.44080.vda.linux@googlemail.com> (raw)
In-Reply-To: <1189021619.4442.36.camel@imap.mvista.com>
On Wednesday 05 September 2007 20:46, Daniel Walker wrote:
> On Wed, 2007-09-05 at 20:49 +0100, Denys Vlasenko wrote:
>
> > What does "it" stand for in this sentence?
>
> "it" is your patches, and I think we got to bottom of it .. "it" (i.e.
> your patches) don't actually work with modules, which is what you
> originally contended ..
Kernel builds, loads and runs with my patches, and modules load just fine.
> > My patch was tested to work in my limited testing,
> > but it is very conservative.
> >
> > I can't talk for Marcelo, but his patch probably worked too,
> > it just didn't guarantee that you can install kernel, and
> > then compile and load external module. Wel, it will compile,
> > but maybe will fail to load.
>
> At least you should modify your Kconfig changes so that you don't allow
> people to select your new option unless they have CONFIG_MODULES off..
You seem to have interesting definition of "desn't work".
--
vda
next prev parent reply other threads:[~2007-09-06 10:58 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-05 13:43 [PATCH 0/3] build system: section garbage collection for vmlinux Denys Vlasenko
2007-09-05 13:47 ` [PATCH 1/3] " Denys Vlasenko
2007-09-05 13:49 ` [PATCH 2/3] " Denys Vlasenko
2007-09-05 13:55 ` [PATCH 3/3] " Denys Vlasenko
2007-09-05 18:40 ` Denys Vlasenko
2007-09-05 20:46 ` Sam Ravnborg
2007-09-06 10:55 ` Denys Vlasenko
2007-09-06 22:33 ` Sam Ravnborg
2007-09-10 12:01 ` Sam Ravnborg
2007-09-10 19:02 ` Denys Vlasenko
2007-09-10 19:14 ` Sam Ravnborg
2007-09-11 11:23 ` Denys Vlasenko
2007-09-11 11:55 ` Sam Ravnborg
2007-09-05 20:07 ` [PATCH 1/3] " Sam Ravnborg
2007-09-06 10:59 ` Denys Vlasenko
2007-09-06 22:36 ` Sam Ravnborg
2007-09-08 15:02 ` Denys Vlasenko
2007-09-05 15:53 ` [PATCH 0/3] " Oleg Verych
2007-09-05 18:46 ` Denys Vlasenko
2007-09-05 20:34 ` Oleg Verych
2007-09-05 21:52 ` Adrian Bunk
2007-09-06 10:55 ` Denys Vlasenko
2007-09-06 11:40 ` Oleg Verych
2007-09-06 12:21 ` Adrian Bunk
2007-09-06 20:43 ` Oleg Verych
2007-09-06 20:39 ` Adrian Bunk
2007-09-06 21:16 ` Oleg Verych
2007-09-06 21:19 ` Adrian Bunk
2007-09-06 22:01 ` Oleg Verych
2007-09-06 22:43 ` Adrian Bunk
2007-09-06 12:33 ` Denys Vlasenko
2007-09-05 16:29 ` Daniel Walker
2007-09-05 18:37 ` Denys Vlasenko
2007-09-05 18:38 ` Daniel Walker
2007-09-05 19:14 ` Denys Vlasenko
2007-09-05 19:07 ` Daniel Walker
2007-09-05 19:49 ` Denys Vlasenko
2007-09-05 19:46 ` Daniel Walker
2007-09-06 10:57 ` Denys Vlasenko [this message]
2007-09-06 15:13 ` Daniel Walker
2007-09-06 17:07 ` Denys Vlasenko
2007-09-07 16:31 ` Daniel Walker
2007-09-07 17:24 ` Sam Ravnborg
2007-09-07 17:19 ` Daniel Walker
2007-09-07 17:30 ` Denys Vlasenko
2007-09-07 17:38 ` Daniel Walker
2007-09-05 19:31 ` Adrian Bunk
2007-09-05 19:24 ` Daniel Walker
2007-09-05 19:46 ` Adrian Bunk
2007-09-05 19:27 ` Adrian Bunk
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=200709061157.44080.vda.linux@googlemail.com \
--to=vda.linux@googlemail.com \
--cc=dwalker@mvista.com \
--cc=kai@germaschewski.name \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.