From: msokolov@ivan.Harhan.ORG (Michael Sokolov)
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: Platform files question
Date: Wed, 28 Nov 01 10:54:05 PST [thread overview]
Message-ID: <0111281854.AA27629@ivan.Harhan.ORG> (raw)
Tom Rini <trini@kernel.crashing.org> wrote:
> There's no exact way right now. But it breaks down like this, if you
> have a port which does _not_ need to change include/asm-ppc/serial.h,
> they can all go in arch/ppc/platforms. If you change
> include/asm-ppc/serial.h AND newBoard_serial.h needs to include
> newBoard.h, they both go in include/asm-ppc/platforms/.
And what if I have a port that has its newBoard_serial.h, but it doesn't need
to include newBoard.h?
MS
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2001-11-28 18:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-28 18:54 Michael Sokolov [this message]
2001-11-28 23:37 ` Platform files question Tom Rini
-- 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 16:40 Michael Sokolov
2001-11-28 18:06 ` Armin Kuster
2001-12-28 17:14 ` Dan Malek
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=0111281854.AA27629@ivan.Harhan.ORG \
--to=msokolov@ivan.harhan.org \
--cc=linuxppc-dev@lists.linuxppc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).