From: Aaron Pace <kodiakuppercut@gmail.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Large physical address support on e500 platform
Date: Mon, 25 Jan 2010 10:06:32 -0700 [thread overview]
Message-ID: <bc81dc641001250906o18ba8e9cofbb02421ae046f65@mail.gmail.com> (raw)
In-Reply-To: <C8218436-3EA1-46F0-8E7E-4699AA06005B@kernel.crashing.org>
>
> Is a simple "hello world" module sufficient to show the issue? =A0I'll lo=
ok into it this week.
>
> - k
It wasn't in my situation, unfortunately. To duplicate this, I had
one relatively large kernel module, and then one simple 'hello world'
module that did nothing more than call an exported function from the
first module as part of its init.
-Aaron
next prev parent reply other threads:[~2010-01-25 17:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-22 6:27 Large physical address support on e500 platform Aaron Pace
2010-01-25 16:46 ` Kumar Gala
2010-01-25 17:06 ` Aaron Pace [this message]
2010-01-25 17:25 ` Kumar Gala
2010-05-13 12:01 ` Kumar Gala
2010-05-13 12:05 ` Kumar Gala
-- strict thread matches above, loose matches on Subject: below --
2010-01-19 6:54 Alex Dubov
2010-01-19 19:13 ` Kumar Gala
2010-01-20 1:34 ` Alex Dubov
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=bc81dc641001250906o18ba8e9cofbb02421ae046f65@mail.gmail.com \
--to=kodiakuppercut@gmail.com \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).