From: Armin Kuster <akuster@mvista.com>
To: Michael Sokolov <msokolov@ivan.Harhan.ORG>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Platform files question
Date: Wed, 28 Nov 2001 10:06:39 -0800 [thread overview]
Message-ID: <3C0527AF.9CA07809@mvista.com> (raw)
In-Reply-To: 0111281640.AA27241@ivan.Harhan.ORG
Michael Sokolov wrote:
>
> Hi there,
>
> Now that we have arch/ppc/platforms and include/asm-ppc/platforms for all
> platform-specific files, I have this question for you guys. When I do a new
> platform port, should I put the main .h file for the platform in
> arch/ppc/platforms or in include/asm-ppc/platforms?
>
> MS
>
AFAIK your board header should go in include/asm-ppc/platforms and your
board.c file should go arch/ppc/platforms
-- armin
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-11-28 18:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-28 16:40 Platform files question Michael Sokolov
2001-11-28 18:06 ` Armin Kuster [this message]
2001-12-28 17:14 ` Dan Malek
-- strict thread matches above, loose matches on Subject: below --
2001-11-28 17:14 Michael Sokolov
2001-11-28 18:50 ` Tom Rini
2001-11-28 18:54 Michael Sokolov
2001-11-28 23:37 ` Tom Rini
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=3C0527AF.9CA07809@mvista.com \
--to=akuster@mvista.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=msokolov@ivan.Harhan.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.