From: Rusty Russell <rusty@rustcorp.com.au>
To: Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>
Cc: Roman Zippel <zippel@linux-m68k.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][RFC] new module interface
Date: Sat, 27 Jul 2002 17:00:32 +1000 [thread overview]
Message-ID: <20020727070410.B44A0418B@lists.samba.org> (raw)
In-Reply-To: Your message of "Fri, 26 Jul 2002 13:15:53 EST." <Pine.LNX.4.44.0207261313280.384-100000@chaos.physics.uiowa.edu>
In message <Pine.LNX.4.44.0207261313280.384-100000@chaos.physics.uiowa.edu> you
write:
> On Fri, 26 Jul 2002, Rusty Russell wrote:
>
> > > Not yet. The problem is the module name, e.g. ext2 is called
> > > fs_ext2_super, it will need some kbuild changes to get the right module
> > > name.
> >
> > I need that too: the mythical "KBUILD_MODNAME". Both Keith and Kai
> > promised it to me...
>
> I told you that I have the code, and that I can provide it to you as soon
> as you need it. You did never ask for it, though. Do you need it now?
Sorry for the misunderstanding, I expected it to appear in the build
system one day magically 8)
You can just send me the patch though, and I'll throw it on my page
and make the module replacement patch Depend: on it. I'll also give
it some good testing.
Thanks!
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
next prev parent reply other threads:[~2002-07-27 7:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-24 20:02 [PATCH][RFC] new module interface Roman Zippel
2002-07-25 8:08 ` Rusty Russell
2002-07-25 9:56 ` Roman Zippel
2002-07-26 3:43 ` Rusty Russell
2002-07-26 4:22 ` Keith Owens
2002-07-26 10:12 ` Roman Zippel
2002-07-27 6:49 ` Rusty Russell
2002-07-28 11:57 ` Roman Zippel
2002-07-26 18:15 ` Kai Germaschewski
2002-07-27 7:00 ` Rusty Russell [this message]
2002-07-27 17:11 ` Kai Germaschewski
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=20020727070410.B44A0418B@lists.samba.org \
--to=rusty@rustcorp.com.au \
--cc=kai@tp1.ruhr-uni-bochum.de \
--cc=linux-kernel@vger.kernel.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