All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Malek <dan@embeddededge.com>
To: Becky Bruce <becky.bruce@freescale.com>
Cc: linuxppc64-dev@ozlabs.org, linuxppc-dev@ozlabs.org
Subject: Re: RFC: proposed arch/powerpc directory structure
Date: Wed, 10 Aug 2005 13:01:34 -0400	[thread overview]
Message-ID: <22fac6c20e1ee142606e4295722c2d1d@embeddededge.com> (raw)
In-Reply-To: <c237b7e878e0c32f421209fa37b7a156@freescale.com>


On Aug 10, 2005, at 12:45 PM, Becky Bruce wrote:

> ....  Listed below are the proposed directories, along with a 
> description of the logical contents, as well as a description of which 
> existing files will be moved into these directories.

I think this is fine, but I'd like to make a suggestion about the file 
names themselves.
Since we have platform directories for a specific processor type or 
core, can we
change the file names a little?  For example, if I'm in the 
platforms/82xx directory,
I don't need to prepend every file with mpc82xx_ or ppc82xx- or 
whatever.  We
know that's what it is, let's try to use the file names to be more 
descriptive of what's
inside of them.  Regardless of the build or management tools we use, I 
still find it
nice to keep a concise file name that is still descriptive, and take 
advantage of
the directory structure names to assist with this.

Thanks.


	-- Dan

  reply	other threads:[~2005-08-10 17:01 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-10 16:45 RFC: proposed arch/powerpc directory structure Becky Bruce
2005-08-10 17:01 ` Dan Malek [this message]
2005-08-10 21:35   ` John W. Linville
2005-08-11  0:09 ` Stephen Rothwell
2005-08-11  1:10   ` Olof Johansson
2005-08-11 19:59 ` Tom Rini
2005-08-11 20:13   ` Kumar Gala
2005-08-11 20:18     ` Tom Rini
2005-08-11 22:41       ` Becky Bruce
2005-08-11 23:07       ` Kumar Gala
2005-08-11 23:19         ` Tom Rini
2005-08-12  2:34           ` Kumar Gala
2005-08-12  3:38             ` Tom Rini
2005-08-11 23:29         ` Dan Malek
2005-08-12  2:09   ` Josh Boyer
2005-08-12  3:49   ` Paul Mackerras
2005-08-12  4:14     ` Tom Rini
2005-08-15 18:25       ` Segher Boessenkool
2005-08-11 20:25 ` Olaf Hering

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=22fac6c20e1ee142606e4295722c2d1d@embeddededge.com \
    --to=dan@embeddededge.com \
    --cc=becky.bruce@freescale.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=linuxppc64-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 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.