All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kumar Gala <kumar.gala@freescale.com>
To: "Tom Rini" <trini@kernel.crashing.org>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: building ppc_htab?
Date: Thu, 17 Mar 2005 11:34:14 -0600	[thread overview]
Message-ID: <a74c02a8aa54e529b296eeac31bdec4e@freescale.com> (raw)
In-Reply-To: <20050316221152.GZ8345@smtp.west.cox.net>


On Mar 16, 2005, at 4:11 PM, Tom Rini wrote:

> On Wed, Mar 16, 2005 at 12:57:24AM -0600, Kumar Gala wrote:
>
> > Is there any reason not to make the following change so we build
> > ppc_htab only on PPC STD MMU?=A0 This would also require fixing up
> > fs/proc/proc_misc.c.
>
> I could have sworn, but maybe my memory sucks, that we no longer =
messed
> w/ fs/proc/proc_misc.c for any of the PPC-specific things (since in =
2.6
>  you can do all of that proc magic in your 'driver').=A0 So this patch
>  would make a great deal of sense to do, and if it lacks what I'm=20
> talking
>  about, we should do that part as well :)

I'm not exactly clear on what you are talking about.  There is this=20
snippet in fs/proc/proc_misc.c:

#ifdef CONFIG_PPC32
         {
                 extern struct file_operations ppc_htab_operations;
                 entry =3D create_proc_entry("ppc_htab", =
S_IRUGO|S_IWUSR,=20
NULL);
                 if (entry)
                         entry->proc_fops =3D &ppc_htab_operations;
         }
#endif

Are you suggesting this should live elsewhere?  I'm not that familiar=20
with proc code.

- kumar

  reply	other threads:[~2005-03-17 17:34 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
2005-03-16 22:11 ` Tom Rini
2005-03-17 17:34   ` Kumar Gala [this message]
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=a74c02a8aa54e529b296eeac31bdec4e@freescale.com \
    --to=kumar.gala@freescale.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=trini@kernel.crashing.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.