From: Darren Hart <dvhart@linux.intel.com>
To: "Bodke, Kishore K" <kishore.k.bodke@intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: [PATCH 0/1] [KERNEL] meta: New Crystal Forest Machine Branch
Date: Wed, 08 Aug 2012 11:32:17 -0700 [thread overview]
Message-ID: <5022B0B1.1050008@linux.intel.com> (raw)
In-Reply-To: <D956029D25CF204F948EA0FB515E1EE20AD45DC1@ORSMSX105.amr.corp.intel.com>
On 08/08/2012 11:28 AM, Bodke, Kishore K wrote:
>
>
>> -----Original Message-----
>> From: Darren Hart [mailto:dvhart@linux.intel.com]
>> Sent: Wednesday, August 08, 2012 11:14 AM
>> To: Bodke, Kishore K
>> Cc: yocto@yoctoproject.org; bruce.ashfield@windriver.com
>> Subject: Re: [PATCH 0/1] [KERNEL] meta: New Crystal Forest Machine Branch
>>
>> n 08/08/2012 10:56 AM, kishore.k.bodke@intel.com wrote:
>>> From: Kishore Bodke <kishore.k.bodke@intel.com>
>>>
>>> Hi,
>>>
>>> This is a revised patch set is for creating the new Crystal Forest Machine.
>>> Crystal Forest Machine is Sandybridge CPU with Cave Creek Chipset.
>>>
>>> This machine is based on standard/default/common-pc-64.
>>>
>>> Please create a new branch called standard/default/common-pc-
>> 64/crystalforest
>>> for linux-yocto-3.4 kernel and pull this new meta branch.
>>>
>>> Thanks
>>> Kishore.
>>
>> Hi Kishore, please note that as these patches are for the linux-yocto
>> sources, they should be sent to the linux-yocto mailing list:
>>
>> https://lists.yoctoproject.org/listinfo/linux-yocto
>>
>> This is a relatively new list, please keep it in mind for the future.
>
> Hi Darren,
>
> Thanks for letting me know this.
> A quick question.
> Do we need to send all the kernel related patches only to Linux-yocto mailing list or to both Linux-yocto and Yocto mailing list too?
If the patches are against a linux-yocto*.git repository, they go to
linux-yocto. If they are against the oe-core meta-data, they should go
to the openembedded-core mailing list. If they are to meta-yocto, they
should go to the poky mailing list (this one is rather confusing
unfortunately). The only patches that should go to the "yocto" mailing
list are for related projects, such as meta-intel, that are not part of
oe-core, poky, linux-yocto, and do not have their own lists (such as
bitbake-devel).
For the work you are doing:
Patches to meta-intel go here, to the yocto mailing list.
Patches to linux-yocto*git go to the linux-yocto mailing list.
Patches to poky/meta/recipes-kernel/linux/* should go to the
openembedded-core mailing list.
Clear as mud? :-)
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Technical Lead - Linux Kernel
next prev parent reply other threads:[~2012-08-08 18:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-08 17:56 [PATCH 0/1] [KERNEL] meta: New Crystal Forest Machine Branch kishore.k.bodke
2012-08-08 17:56 ` [PATCH 1/1] [KERNEL] meta: Crystal Forest Machine Created kishore.k.bodke
2012-08-08 18:11 ` Darren Hart
2012-08-08 18:13 ` [PATCH 0/1] [KERNEL] meta: New Crystal Forest Machine Branch Darren Hart
2012-08-08 18:28 ` Bodke, Kishore K
2012-08-08 18:32 ` Darren Hart [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-08-02 18:35 kishore.k.bodke
2012-08-03 15:26 ` Bruce Ashfield
2012-08-03 15:55 ` Darren Hart
2012-08-03 16:31 ` Bodke, Kishore K
2012-08-03 16:50 ` Darren Hart
2012-08-01 19:15 kishore.k.bodke
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=5022B0B1.1050008@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=kishore.k.bodke@intel.com \
--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.