From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: "Development list for the linux-yocto*.git Linux kernel
repositories" <linux-yocto@yoctoproject.org>
Cc: Yocto Project Discussion <yocto@yoctoproject.org>
Subject: Re: [linux-yocto] [meta-realtime][PATCH] add sched_deadline reckpies-kernel for 3.8 kernel
Date: Thu, 14 Mar 2013 23:46:29 -0700 [thread overview]
Message-ID: <5142C3C5.7030302@windriver.com> (raw)
In-Reply-To: <5142C353.8020209@windriver.com>
On 13-03-14 11:44 PM, Bruce Ashfield wrote:
> On 13-03-14 11:36 PM, Insop Song wrote:
>> On Thu, Mar 14, 2013 at 11:13 PM, Bruce Ashfield
>> <bruce.ashfield@gmail.com> wrote:
>>
>>
>>>
>>> Hmm. One of the arbiters is me .. if it doesn't work this time, let
>>> me know
>>> and I'll check the list membership.
>>
>> I've just signed up and got a confirmation email.
>>
>>
>>>>
>>>> I was do some testing on "make localmodconfig", which will gets me the
>>>> using module build .config.
>>>> So let me me ask you this before I send out an updated patch.
>>>>
>>>> I ran "lsmod > /tmp/lsmod" on my qemux86
>>>> On dev host, run "make LSMOD=/tmp/lsmod localmodconfig" to get this
>>>> localmodconfig_qemux86.cfg file, which has less module configurations.
>>>>
>>>> Then I use this in bbappend file like below:
>>>>
>>>> ---
>>>> SRC_URI =
>>>> "git://git.yoctoproject.org/linux-yocto-3.8.git;protocol=git;bareclone=1;branch=${KBRANCH},${KMETA};name=machine,meta
>>>>
>>>> \
>>>> file://localmodconfig_qemux86.cfg \
>>>> "
>>>> ----
>>>>
>>>> what do you think?
>>>
>>> We want to track the modules and policies of the main qemu BSP,
>>> not override them all here. Extra layers should be only changing board
>>> functionality that is specific to their functionality, not the base
>>> board
>>> configuration.
>>>
>>> If you think there are modules that are enabled that shouldn't be, we
>>> can address that by looking at the base policy and deciding if that
>>> base policy is wrong.
>>>
>>> Cheers,
>>>
>>
>> I see, let me follow up the current patch update and do some more look
>> on qemu bsp and deal with a separate patch.
>>
>> Here are the update patches 2/2.
>>
>> And let me know if you want to see in different ways of patch
>> delivery? since, I haven't set up my gmail smtp set up yet (due to
>> application specific athentication), so I manually copy and paste and
>> attach the files.
>
> Are you trying to send via git send-email ? The following is the
> way that I'd relay through gmail:
>
> > git send-email --smtp-server smtp.gmail.com --smtp-user
> bruce.ashfield@gmail.com --smtp-pass <paswd> --smtp-ssl ~/rr/
>
> And to generate the patches and introductory email, look at
> the oe-core scripts/create-pull-request.
>
> That's the best and easiest way to send patches.
>
>> ------
>>
>>
>> Subject: [meta-realtime][PATCH 2/2] remove edf.cfg and follow up review
>> feedback
>>
>> ---
>> recipes-kernel/linux/linux-yocto/edf.cfg | 4 ----
>> recipes-kernel/linux/linux-yocto_3.8.bbappend | 5 -----
>> 2 files changed, 9 deletions(-)
>> delete mode 100644 recipes-kernel/linux/linux-yocto/edf.cfg
>
> This looks good. I'll stage it locally and do a quick test build.
I hit send too soon, I meant to point out that in a situation such
as this, you can ammend your original commit with your second set
of change and re-submit just the single patch. I can squash the
commits here, but it's easier to do on your end.
Just summarize the v2 in your new patch email when you ammend/squash
changes, so we won't forget what was changed :)
Cheers,
Bruce
>
> Cheers,
>
> Bruce
>
>>
>> diff --git a/recipes-kernel/linux/linux-yocto/edf.cfg
>> b/recipes-kernel/linux/linux-yocto/edf.cfg
>> deleted file mode 100644
>> index ccf004f..0000000
>> --- a/recipes-kernel/linux/linux-yocto/edf.cfg
>> +++ /dev/null
>> @@ -1,4 +0,0 @@
>> -CONFIG_CGROUPS=y
>> -CONFIG_CGROUP_SCHED=y
>> -CONFIG_DEADLINE_GROUP_SCHED=y
>> -
>> diff --git a/recipes-kernel/linux/linux-yocto_3.8.bbappend
>> b/recipes-kernel/linux/linux-yocto_3.8.bbappend
>> index c6a969f..175ab91 100644
>> --- a/recipes-kernel/linux/linux-yocto_3.8.bbappend
>> +++ b/recipes-kernel/linux/linux-yocto_3.8.bbappend
>> @@ -1,13 +1,8 @@
>> FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
>> -COMPATIBLE_MACHINE_qemux86 = "qemux86"
>> -COMPATIBLE_MACHINE_fri2 = "fri2"
>>
>> KBRANCH_qemux86 = "standard/edf"
>> KBRANCH_fri2 = "standard/edf"
>>
>> -KMACHINE_qemux86 = "qemux86"
>> -KMACHINE_fri2 = "fri2"
>> -
>> SRCREV_machine_qemux86 = "62d98f6b12f91cc7419b88dfa2e0abe077c94f9f"
>> SRCREV_machine_fri2 = "62d98f6b12f91cc7419b88dfa2e0abe077c94f9f"
>>
>>
>>
>> _______________________________________________
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>>
>
> _______________________________________________
> linux-yocto mailing list
> linux-yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/linux-yocto
next prev parent reply other threads:[~2013-03-15 6:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-15 5:09 [meta-realtime][PATCH] add sched_deadline reckpies-kernel for 3.8 kernel Insop Song
2013-03-15 5:15 ` Bruce Ashfield
2013-03-15 5:59 ` Insop Song
2013-03-15 6:13 ` Bruce Ashfield
2013-03-15 6:36 ` Insop Song
2013-03-15 6:44 ` Bruce Ashfield
2013-03-15 6:46 ` Bruce Ashfield [this message]
2013-03-15 10:51 ` [linux-yocto] " Insop Song
2013-03-15 10:51 ` Insop Song
2013-03-15 6:27 ` Bruce Ashfield
2013-03-15 11:55 ` Insop Song
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=5142C3C5.7030302@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=linux-yocto@yoctoproject.org \
--cc=yocto@yoctoproject.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.