From: Bian Naimeng <biannm@cn.fujitsu.com>
To: Phil Blundell <pb@pbcl.net>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [RFC][PATCH 1/6]qemuarm.conf: provide a common qemuarm machine configuration
Date: Tue, 30 Jul 2013 09:51:54 +0800 [thread overview]
Message-ID: <51F71C3A.8000701@cn.fujitsu.com> (raw)
In-Reply-To: <1375112169.13247.44.camel@phil-desktop.brightsign>
said the following on 2013-7-29 23:36:, Phil Blundell wrote:
> On Mon, 2013-07-29 at 12:02 +0800, Bian Naimeng wrote:
>> qemux86.conf: provide a common qemux86 machine configuration,
>> so developer/distributor can customize their specific one.
>>
>> Although, we can modify the meta/conf/machine/qemux86.conf to customize our
>> configuration, but it's uncomfortable for developer/distributor maintaining
>> their branch.
>> After applying this patch, developer can tell poky using their machine
>> configuration by prepending their layer to BBPATH(Of course,
>> the bblayers.conf should be adapted to it).
>
> I don't really understand the purpose of this patch. Surely there is
> nothing to stop you from shipping an overlay qemux86.conf in some other
> layer today, right? What exactly is the advantage of this extra
> indirection through an .inc file?
>
What my purpose is that make it easy to implement the below case.
1. I want inherit all the configuration item of qemux86.conf.
2. I want add some new items to my qemux86.conf.
3. If there're changes to qemux86.conf, i want merge them to my qemux86.conf
Yes, we can implement this case today.
1. Copy the meta/conf/machine/qemux86.conf to my layer.
2. Add new items to my qemux86.conf
3. Rewrite my qemux86.conf to merge community changes.
However, if applying these patches, it becomes easy.
1. add "require conf/machine/include/qemux86.inc" to my qemux86.conf
2. add new items to my qemux86.conf
3. modify qemux86.inc to update qemux86 configration at community,
so all community changes will be merged to my qemux86.conf automatically
when merging the mainline.
> Also, as a side note, your patches 1/6, 2/6 and 6/6 all said
> "qemuarm.conf" in the subject lines but only the last of them actually
> contained changes to qemuarm.conf.
Sorry for my mistake. The correct one is following.
1/6: qemux86.conf.
2/6: qemux86-64.conf
>
> Also also, the patches in this form are quite hard to follow. Did you
> use "git format-patch -M" when creating them?
Yes, I used "git format-patch -M" to create them.
I will check them by linux/scripts/checkpatch.pl next time.
Thanks
bian
>
> p.
>
>
next prev parent reply other threads:[~2013-07-30 1:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-29 3:58 [RFC][PATCH 0/6]provide a common machine configuration to developer for customizing specific machine Bian Naimeng
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 [this message]
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=51F71C3A.8000701@cn.fujitsu.com \
--to=biannm@cn.fujitsu.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=pb@pbcl.net \
/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