From: Toralf Lund <toralf@procaptura.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Arjan van de Ven <arjan@infradead.org>, Greg KH <greg@kroah.com>,
linux-kernel@vger.kernel.org
Subject: Re: insmod segfault in pci_find_subsys()
Date: Mon, 18 Apr 2005 09:20:18 +0200 [thread overview]
Message-ID: <42635FB2.8050706@procaptura.com> (raw)
In-Reply-To: <20050413132755.GA8236@mars.ravnborg.org>
Sam Ravnborg wrote:
>On Wed, Apr 13, 2005 at 01:49:10PM +0200, Toralf Lund wrote:
>
>
>>>
>>>
>>Yes. As I've (also) already said elsewhere, I knew that, really. The
>>current build setup fails to do this partly for historical reasons,
>>partly because the driver also supports different OSes. (And is still
>>expected to build correctly with Linux 2.4, not just 2.6.)
>>
>>
>
>
>
Hmmm. Seems like my original reply to this message got lost...
>Following trick works with both 2.4 and 2.6:
>
>makefile:
>all:
> $(MAKE) -C Kernel_src_path SUBDIRS=$(PWD) modules
>
>Makefile:
>
>obj-m := mymodule.o
>
>It obtains CFLAGS as expected etc.
>People seems to do their best to avoid such a simple setup :-(
>
>
What? Write a simple makefile that a normal human being may actually
understand? Not autogenerate something utterly unreadable from something
that's autogenerated from something that's ... ???
It's not *quite* that simple with the module I'm talking about, though,
as the source code is split into several files. Which is a Good Thing, IMO.
Also, I was unsure if this would work with Linux 2.4 (but I was going to
test it)...
> Sam
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at http://www.tux.org/lkml/
>
>
prev parent reply other threads:[~2005-04-18 7:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-18 9:12 insmod segfault in pci_find_subsys() Toralf Lund
2005-03-18 17:07 ` Greg KH
2005-03-19 12:28 ` Toralf Lund
2005-03-29 14:15 ` Toralf Lund
2005-04-13 7:12 ` Greg KH
2005-04-13 11:00 ` Toralf Lund
2005-04-13 11:13 ` Arjan van de Ven
2005-04-13 11:49 ` Toralf Lund
2005-04-13 13:27 ` Sam Ravnborg
2005-04-18 7:20 ` Toralf Lund [this message]
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=42635FB2.8050706@procaptura.com \
--to=toralf@procaptura.com \
--cc=arjan@infradead.org \
--cc=greg@kroah.com \
--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