From: Ingo Molnar <mingo@elte.hu>
To: Mel Gorman <mel@csn.ul.ie>
Cc: Eric Lacombe <goretux@gmail.com>,
linux-kernel@vger.kernel.org, davej@redhat.com,
tglx@linutronix.de
Subject: Re: [unused symbol] need to use init_mm
Date: Thu, 30 Apr 2009 16:40:57 +0200 [thread overview]
Message-ID: <20090430144057.GA14897@elte.hu> (raw)
In-Reply-To: <20090430140957.GD21997@csn.ul.ie>
* Mel Gorman <mel@csn.ul.ie> wrote:
> On Thu, Apr 30, 2009 at 12:32:04PM +0200, Eric Lacombe wrote:
> > Hi,
> >
> > Within a module I work on, I need to access to init_mm, but as it is marked
> > UNUSED, I wonder if there is another way (an API) to access to it.
> > Otherwise, what can I do to have this mark removed from init_mm in the
> > mainline? as my module is really not yet ready for inclusion.
> >
> > Thanks in advance for your response,
> >
>
> It looks to be that it was removed already, somewhat behind schedule, in
> commit 9470565579f29486f4ed0ffa50774268b64994b0 after an initial attempt
> was made in commit 3abf024d2abb79614d8c4cb25a70d5596f77d0ad. I don't know
> if there is a procedure for bringing it back but I would guess it's a call
> for the x86 maintainers. I imagine they will want to at least know;
>
> 1. Why do you need init_mm exported?
> 2. Is there an alternative approach to using init_mm?
> 3. Assuming yes, what are the downsides?
> 4. When do you think the module will be ready for posting? i.e. is this
> really something destined for mainline or some perma-out-of-tree?
yes, those questions have to be answered.
Ingo
next prev parent reply other threads:[~2009-04-30 14:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-30 10:32 [unused symbol] need to use init_mm Eric Lacombe
2009-04-30 14:09 ` Mel Gorman
2009-04-30 14:40 ` Ingo Molnar [this message]
2009-04-30 17:55 ` Eric Lacombe
2009-05-01 15:51 ` Mel Gorman
2009-05-02 18:05 ` Eric Lacombe
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=20090430144057.GA14897@elte.hu \
--to=mingo@elte.hu \
--cc=davej@redhat.com \
--cc=goretux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mel@csn.ul.ie \
--cc=tglx@linutronix.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