From: "Justin Mattock" <justinmattock@gmail.com>
To: "Adrian Bunk" <bunk@kernel.org>
Cc: npiggin@suse.de,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: nopage mm.h
Date: Sat, 3 May 2008 23:48:35 +0000 [thread overview]
Message-ID: <dd18b0c30805031648x562beaabwff47e721acddc0e9@mail.gmail.com> (raw)
In-Reply-To: <20080503233818.GZ5838@cs181133002.pp.htv.fi>
On Sat, May 3, 2008 at 11:38 PM, Adrian Bunk <bunk@kernel.org> wrote:
>
> On Sat, May 03, 2008 at 11:29:20PM +0000, Justin Mattock wrote:
> > Hello; I have a question about the nopage function that was removed in
> > the kernel.
> > What would be the best way for me to build a module that has a nopage
> > funtion in it?
> > Right now I went and undid what you had done to the kernel,to atleast
> > have the module not give me errors,
> > but, am wondering if I should try to take the module and remove the
> > nopage function in it , and add the functions that is relevent.
> > to keep the module up-to date.
>
> Where can we find the source code of your module?
>
> > regards;
>
> cu
> Adrian
>
> --
>
> "Is there not promise of rain?" Ling Tan asked suddenly out
> of the darkness. There had been need of rain for many days.
> "Only a promise," Lao Er said.
> Pearl S. Buck - Dragon Seed
>
>
The module is fglrx.
regards;
--
Justin P. Mattock
next prev parent reply other threads:[~2008-05-03 23:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-03 23:29 Justin Mattock
2008-05-03 23:38 ` Adrian Bunk
2008-05-03 23:48 ` Justin Mattock [this message]
2008-05-03 23:56 ` Adrian Bunk
2008-05-04 0:15 ` Justin Mattock
2008-05-04 7:42 ` Jiri Slaby
2008-05-04 16:12 ` Justin Mattock
2008-05-05 3:28 ` Nick Piggin
2008-05-05 3:47 ` Justin Mattock
2008-05-05 4:19 ` Nick Piggin
2008-05-05 5:07 ` Justin Mattock
2008-05-05 8:28 ` Nick Piggin
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=dd18b0c30805031648x562beaabwff47e721acddc0e9@mail.gmail.com \
--to=justinmattock@gmail.com \
--cc=bunk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@suse.de \
/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®