From: Bob Cochran <yocto@mindchasers.com>
To: Luo Zhenhua <zhenhua.luo@freescale.com>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: [RFC] The proposal of FSL QorIQ SDK upstream
Date: Wed, 20 May 2015 12:00:10 -0400 [thread overview]
Message-ID: <555CAF8A.6060501@mindchasers.com> (raw)
In-Reply-To: <BN3PR03MB1367795BC07F0DC2E9FD8156E4C20@BN3PR03MB1367.namprd03.prod.outlook.com>
On 05/20/2015 04:14 AM, Luo Zhenhua wrote:
> Hi Bob,
>
> The external bug report system and maillist are not setup now.
Is Freescale still planning on doing this? If so, please provide an idea
when we might see it.
>
> The QorIQ SDK 1.8 release is planned in this June, the recipes will be upstreamed in meta-fsl-ppc layer in July.
>
>
> Best Regards,
>
> Zhenhua
>
>> -----Original Message-----
>> From: Bob Cochran [mailto:yocto@mindchasers.com]
>> Sent: Thursday, May 14, 2015 9:27 AM
>> To: Luo Zhenhua-B19537; meta-freescale@yoctoproject.org
>> Subject: Re: [meta-freescale] [RFC] The proposal of FSL QorIQ SDK upstream
>>
>> On 07/16/2014 02:00 AM, zhenhua.luo@freescale.com wrote:
>>
>>> More to do
>>> • Setup public bug management system for FSL SDKs.
>>> • Push all modules to public git repository to ensure FSL community BSP sync
>> with FSL released SDK.
>>> • Setup an external mailing list for external git repository for FSL SDK
>> discussion, patch submission, patch review.
>>> • Setup an patch management tool(patchwork or gerrit) to manage patches
>> from community.
>>> • Enhance the commit message in patch to facilitate the patch search for
>> specific issue.
>>
>>
>> Hi Zhenhua,
>>
>> Can you please update us on the status of these work items? As far as I know
>> things like public bug management for FSL SDKs and an external mail list for the
>> FSL external git repo haven't happened, but I could have just missed it.
>>
>> I have to believe that between the FSL SDK 1.7 release data (12/18/14) and
>> now, there have been numerous bugs identified in the QorIQ SDK that weren't
>> reported on this yocto mail list or pushed to the meta-fsl-ppc repo as patches
>> to the code hosted on the FSL git site. Assuming this is true, will this be
>> addressed in the (near) future?
>>
>> Thank you,
>>
>> Bob
>>
>>
>>
>>
>
prev parent reply other threads:[~2015-05-20 16:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-16 6:00 [RFC] The proposal of FSL QorIQ SDK upstream zhenhua.luo
2014-07-16 12:20 ` Daiane.Angolini
2014-07-16 20:49 ` Bob Cochran
2014-07-23 7:41 ` zhenhua.luo
2014-07-24 18:08 ` Bob Cochran
2014-07-29 9:56 ` zhenhua.luo
2014-08-20 12:27 ` Ahsan, Noor
2014-08-21 2:54 ` zhenhua.luo
2014-07-23 7:16 ` zhenhua.luo
2014-07-23 13:42 ` Bob Cochran
2014-07-24 4:19 ` zhenhua.luo
2014-09-08 1:04 ` 9/8 community meeting, was " Bob Cochran
2014-09-09 13:28 ` zhenhua.luo
2014-09-11 15:45 ` Bob Cochran
2014-09-17 5:31 ` zhenhua.luo
2014-09-18 23:54 ` Bob Cochran
2015-05-14 1:27 ` Bob Cochran
2015-05-20 8:14 ` Luo Zhenhua
2015-05-20 16:00 ` Bob Cochran [this message]
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=555CAF8A.6060501@mindchasers.com \
--to=yocto@mindchasers.com \
--cc=meta-freescale@yoctoproject.org \
--cc=zhenhua.luo@freescale.com \
/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.