linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: kentborg@borg.org (Kent Borg)
To: linux-arm-kernel@lists.infradead.org
Subject: mach header files
Date: Fri, 04 Apr 2014 14:01:43 -0400	[thread overview]
Message-ID: <533EF387.9080702@borg.org> (raw)
In-Reply-To: <4379667.784l7DtcMU@wuerfel>

On 04/04/2014 09:24 AM, Arnd Bergmann wrote:
> Basically at this point we expect zero code in arch/arm/mach-* for a 
> new platform. 

I am in a position similar to Phil's, bringing up Linux on emulated 
hardware. And obviously I look at existing code to see how things are done.

What is the cleanest look-here-first, least mach-code, SMP example for 
me to try to slavishly copy?


Thanks,

-kb, the Kent who was so glad to see the recent anti-pen ranting, as in 
his looking he couldn't figure out what the pen was for.

  parent reply	other threads:[~2014-04-04 18:01 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-04  8:19 mach header files Phil Edworthy
2014-04-04 10:29 ` Grant Likely
2014-04-04 12:16   ` Phil Edworthy
2014-04-04 12:22     ` Grant Likely
2014-04-04 13:14       ` Phil Edworthy
2014-04-04 13:20         ` Thomas Petazzoni
2014-04-08 14:00           ` Laurent Pinchart
2014-04-04 13:44         ` Grant Likely
2014-04-04 13:24   ` Arnd Bergmann
2014-04-04 13:32     ` Barry Song
2014-04-04 15:27       ` Arnd Bergmann
2014-04-04 13:52     ` Phil Edworthy
2014-04-04 15:30       ` Arnd Bergmann
2014-04-04 15:42         ` Phil Edworthy
2014-04-04 15:50           ` Arnd Bergmann
2014-04-04 16:02             ` Phil Edworthy
2014-04-04 16:22               ` Russell King - ARM Linux
2014-04-04 16:38                 ` Phil Edworthy
2014-04-04 18:01     ` Kent Borg [this message]
2014-04-04 18:49       ` Arnd Bergmann
2014-04-04 19:01         ` Kent Borg
2014-04-04 19:19           ` Arnd Bergmann
  -- strict thread matches above, loose matches on Subject: below --
2014-04-02 15:11 Phil Edworthy
2014-04-02 15:16 ` Arnd Bergmann
2014-04-03  7:48   ` Phil Edworthy
2014-04-02 15:20 ` Ben Dooks

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=533EF387.9080702@borg.org \
    --to=kentborg@borg.org \
    --cc=linux-arm-kernel@lists.infradead.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).