Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Bian Naimeng <biannm@cn.fujitsu.com>
To: openembedded-core@lists.openembedded.org
Subject: [RFC][PATCH 0/6]provide a common machine configuration to developer for customizing specific machine
Date: Mon, 29 Jul 2013 11:58:27 +0800	[thread overview]
Message-ID: <51F5E863.9010406@cn.fujitsu.com> (raw)

The main purposes are following.
 - make it possible for developers/distributor to customize their specific machine
   based common machine configurations such as meta/conf/machine/inc/qemuxx.inc
 - make our specific machine compatible with bb file which depends on COMPATIBLE_MACHINE="qemuxx|..."
 - easy to developers to merge mainline to their branch which containing specific machine.

Bian Naimeng (6):
  qemuarm.conf: provide a common qemuarm machine configuration, 
                so developer/distributor can customize their specific one.
  qemuxmips64.conf: provide a common qemuxmips64 machine configuration, 
                    so developer/distributor can customize their specific one.
  qemumips.conf: provide a common qemumips machine configuration, 
                 so developer/distributor can customize their specific one.
  qemuppc.conf: provide a common qemuppc machine configuration, 
                so developer/distributor can customize their specific one.
  qemux86-64.conf: provide a common qemux86-64 machine configuration, 
                   so developer/distributor can customize their specific one.
  qemux86.conf: provide a common qemux86 machine configuration, 
                so developer/distributor can customize their specific one.

 meta/conf/machine/include/qemuarm.inc    |   10 ++++++++++
 meta/conf/machine/include/qemumips.inc   |   11 +++++++++++
 meta/conf/machine/include/qemumips64.inc |   11 +++++++++++
 meta/conf/machine/include/qemuppc.inc    |    9 +++++++++
 meta/conf/machine/include/qemux86-64.inc |   24 ++++++++++++++++++++++++
 meta/conf/machine/include/qemux86.inc    |   24 ++++++++++++++++++++++++
 meta/conf/machine/qemuarm.conf           |   10 ++--------
 meta/conf/machine/qemumips.conf          |   12 ++----------
 meta/conf/machine/qemumips64.conf        |   12 ++----------
 meta/conf/machine/qemuppc.conf           |    8 +-------
 meta/conf/machine/qemux86-64.conf        |   23 +----------------------
 meta/conf/machine/qemux86.conf           |   25 ++-----------------------
 12 files changed, 99 insertions(+), 80 deletions(-)




             reply	other threads:[~2013-07-29  3:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-29  3:58 Bian Naimeng [this message]
2013-07-29  4:02 ` [RFC][PATCH 1/6]qemuarm.conf: provide a common qemuarm machine configuration Bian Naimeng
2013-07-29 15:36   ` Phil Blundell
2013-07-30  1:51     ` Bian Naimeng
2013-07-30  8:15       ` Martin Jansa
2013-07-30  8:55         ` Bian Naimeng
2013-07-29  4:04 ` [RFC][PATCH 2/6]qemuarm.conf: provide a common qemux86-64 " Bian Naimeng
2013-07-29  4:05 ` [RFC][PATCH 3/6]qemuppc.conf: provide a common qemuppc " Bian Naimeng
2013-07-29  4:07 ` [RFC][PATCH 4/6]qemumips.conf: provide a common qemumips " Bian Naimeng
2013-07-29  4:08 ` [RFC][PATCH 5/6]qemumips64.conf: provide a common qemumips64 " Bian Naimeng
2013-07-29  4:09 ` [RFC][PATCH 6/6]qemuarm.conf: provide a common qemuarm " Bian Naimeng

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=51F5E863.9010406@cn.fujitsu.com \
    --to=biannm@cn.fujitsu.com \
    --cc=openembedded-core@lists.openembedded.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