From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, Ram Pai <linuxram@us.ibm.com>,
Sam Ravnborg <sam@ravnborg.org>
Subject: Re: 2.6.17-mm3: segvs in modpost with out-of-tree modules
Date: Wed, 28 Jun 2006 11:44:20 -0700 [thread overview]
Message-ID: <44A2CE04.80606@goop.org> (raw)
In-Reply-To: <20060628112925.f96fcfc4.akpm@osdl.org>
Andrew Morton wrote:
> On Wed, 28 Jun 2006 09:51:11 -0700
> Jeremy Fitzhardinge <jeremy@goop.org> wrote:
>
>> I haven't really looked at yet, but I was hoping someone had already
>> tracked it down.
>>
>
> Not that I'm aware of.
OK, it wasn't really a bug; I had an old Modules.symvers lying around
the madwifi tree from a previous build against an earlier kernel. But
modpost seems all pretty fragile...
J
next prev parent reply other threads:[~2006-06-28 18:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-28 16:51 2.6.17-mm3: segvs in modpost with out-of-tree modules Jeremy Fitzhardinge
2006-06-28 18:29 ` Andrew Morton
2006-06-28 18:44 ` Jeremy Fitzhardinge [this message]
2006-07-01 9:47 ` Sam Ravnborg
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=44A2CE04.80606@goop.org \
--to=jeremy@goop.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxram@us.ibm.com \
--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