From: Dan Malek <dan@embeddededge•com>
To: Kumar Gala <kumar.gala@freescale•com>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs•org>
Subject: Re: building ppc_htab?
Date: Wed, 16 Mar 2005 12:12:28 -0500 [thread overview]
Message-ID: <a6c94966dfd580730c9b435c0d95deef@embeddededge.com> (raw)
In-Reply-To: <4e44f753c3a197eff3b584f24a239f06@freescale.com>
On Mar 16, 2005, at 1:57 AM, Kumar Gala wrote:
> Is there any reason not to make the following change so we build
> ppc_htab only on PPC STD MMU? This would also require fixing up
> fs/proc/proc_misc.c.
Does it actually build properly this way? There used to be
functions/variables
defined there, needed for linking resolution at least. There were also
some
generally called functions, that usually didn't do anything unless
there was
a hash table used. If that is fixed up, then this is fine :-)
Thanks.
-- Dan
next prev parent reply other threads:[~2005-03-16 17:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-16 6:57 building ppc_htab? Kumar Gala
2005-03-16 17:12 ` Dan Malek [this message]
2005-03-16 22:11 ` Tom Rini
2005-03-17 17:34 ` Kumar Gala
2005-03-17 17:41 ` Tom Rini
2005-03-17 21:58 ` Tom Rini
2005-03-18 5:12 ` Kumar Gala
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=a6c94966dfd580730c9b435c0d95deef@embeddededge.com \
--to=dan@embeddededge$(echo .)com \
--cc=kumar.gala@freescale$(echo .)com \
--cc=linuxppc-dev@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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