All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Elvis Dowson <elvis.dowson@mac.com>
Cc: Linux OMAP Mailing List <linux-omap@vger.kernel.org>
Subject: Re: Using C++ style inheritance for board files
Date: Wed, 15 Sep 2010 10:48:48 -0700	[thread overview]
Message-ID: <20100915174848.GB4174@atomide.com> (raw)
In-Reply-To: <66D2DD39-F82B-49BA-89FE-5993B2BF471E@mac.com>

* Elvis Dowson <elvis.dowson@mac.com> [100914 12:58]:
> 
> For example, I have a platform that is based on board-overo.c. Instead copy pasting and creating a new board-overo-variant.c, if the core structures were defined as classes, I could potentially inherit from the base overo board definition, and add my own specific modifications. 

Uhh, let's leave c++ out of this..

You can already easily share most of the code among boards
by having multiple MACHINE entries in the board-*.c file.
See board-n8x0.c for example.

Then you can spend some effort to create common platform
device init code, see gpmc-*.c and hsmmc.c for examples.

Regards,

Tony

           reply	other threads:[~2010-09-15 17:48 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <66D2DD39-F82B-49BA-89FE-5993B2BF471E@mac.com>]

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=20100915174848.GB4174@atomide.com \
    --to=tony@atomide.com \
    --cc=elvis.dowson@mac.com \
    --cc=linux-omap@vger.kernel.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.