mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: Jaswinder Singh <jaswinderrajput@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Support 2.4 modules features in 2.6
Date: Tue, 12 Dec 2006 16:37:33 +0100	[thread overview]
Message-ID: <1165937853.27217.625.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <aa5953d60612120711h375eecadpeb20d971853626cc@mail.gmail.com>

On Tue, 2006-12-12 at 20:41 +0530, Jaswinder Singh wrote:
> On 12/12/06, Arjan van de Ven <arjan@infradead.org> wrote:
> > On Tue, 2006-12-12 at 19:36 +0530, Jaswinder Singh wrote:
> > > Hello,
> > >
> > > I want to support old 2.4 modules features in 2.6 kernel modules:-
> > > 1. no kernel source tree is required to build modules.
> >
> > this is a 2.6 not a 2.4 feature btw
> >
> 
> Really!! , Please let me know what is the procedure to build the
> modules after deleting kernel linux-2.6*

you only need include/* for this in 2.6

you can't do this at all with 2.4 kernels, it needs the whole lot.

(in both cases the code and headers are needed so that your module can
use the data structures and compile in the kernel code you select to use
from inlines)
> 
> 
> > > 2. support modular plugins.
> >
> > ?
> 
> modular plugins means :-

you can still do that. Just you're better off building them in one go;


can you give us a pointer to the source of this 2.4 module you have?
Maybe some of the mechanisms that you want this for are now very
outdated and obsoleted by easier functionality.


-- 
if you want to mail me at work (you don't), use arjan (at) linux.intel.com
Test the interaction between Linux and your BIOS via http://www.linuxfirmwarekit.org


  reply	other threads:[~2006-12-12 15:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-12 14:06 Jaswinder Singh
2006-12-12 14:11 ` Arjan van de Ven
2006-12-12 15:11   ` Jaswinder Singh
2006-12-12 15:37     ` Arjan van de Ven [this message]
2006-12-12 16:48       ` Jaswinder Singh
2006-12-13  8:06         ` Arjan van de Ven
2006-12-12 23:51 ` Matthias Schniedermeyer
     [not found] <fa.49G5lweS8py4hisexsfl1zRqB3Y@ifi.uio.no>
     [not found] ` <fa.o58YYFf0KmJCYaGfzWFQYvWvWqw@ifi.uio.no>
     [not found]   ` <fa.LL4m3y1d6ywMNgGlDl6zW5gCaRA@ifi.uio.no>
     [not found]     ` <fa.uN/dXUaQFfxu97P18c1QPZodm1A@ifi.uio.no>
     [not found]       ` <fa.eHbXg8xrK/U8MrbcE6JMfwHCb1k@ifi.uio.no>
2006-12-12 23:31         ` Robert Hancock

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=1165937853.27217.625.camel@laptopd505.fenrus.org \
    --to=arjan@infradead.org \
    --cc=jaswinderrajput@gmail.com \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®