From: Rusty Russell <rusty@rustcorp.com.au>
To: Kai Germaschewski <kai-germaschewski@uiowa.edu>
Cc: Sam Ravnborg <sam@ravnborg.org>, linux-kernel@vger.kernel.org
Subject: Re: [RFC] [PATCH] new modversions implementation
Date: Tue, 28 Jan 2003 18:07:57 +1100 [thread overview]
Message-ID: <20030128091625.2B5322C08A@lists.samba.org> (raw)
In-Reply-To: Your message of "Sat, 25 Jan 2003 20:30:44 MDT." <Pine.LNX.4.44.0301252025350.6749-100000@chaos.physics.uiowa.edu>
In message <Pine.LNX.4.44.0301252025350.6749-100000@chaos.physics.uiowa.edu> yo
u write:
> On Sat, 25 Jan 2003, Sam Ravnborg wrote:
>
> > A genksyms replacement should do all the three steps above?
>
> Yes, I think at some point I should take a look at patching genksyms so
> that the post-processing above is not necessary anymore. However, it
> doesn't hurt much, performance-wise.
Of course, genksyms belongs in the kernel sources, too, since it's
intimately tied to them.
One step at a time...
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
next prev parent reply other threads:[~2003-01-28 9:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-25 18:44 [RFC] [PATCH] new modversions implementation Kai Germaschewski
2003-01-25 21:56 ` Sam Ravnborg
2003-01-25 22:56 ` Sam Ravnborg
2003-01-26 2:31 ` Kai Germaschewski
2003-01-26 2:30 ` Kai Germaschewski
2003-01-28 7:07 ` Rusty Russell [this message]
2003-01-28 16:40 ` Kai Germaschewski
2003-01-28 7:06 ` Rusty Russell
2003-01-28 19:20 ` Sam Ravnborg
2003-01-28 10:38 ` Rusty Russell
2003-01-28 16:31 ` Richard Henderson
2003-01-28 16:35 ` Kai Germaschewski
2003-01-29 0:15 ` Rusty Russell
-- strict thread matches above, loose matches on Subject: below --
2003-02-02 8:37 [RFC][PATCH] " Paul Marinceu
2003-02-02 8:51 ` David Woodhouse
2003-02-03 0:46 ` Rusty Russell
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=20030128091625.2B5322C08A@lists.samba.org \
--to=rusty@rustcorp.com.au \
--cc=kai-germaschewski@uiowa.edu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox