All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bob Cochran <yocto@mindchasers.com>
To: meta-freescale@yoctoproject.org
Subject: Re: 9/8 community meeting, was [RFC] The proposal of FSL QorIQ SDK upstream
Date: Sun, 07 Sep 2014 21:04:55 -0400	[thread overview]
Message-ID: <540D00B7.5060604@mindchasers.com> (raw)
In-Reply-To: <ac919416d27a4f1793d487a56e4df514@CY1PR0301MB0715.namprd03.prod.outlook.com>

On 07/16/2014 02:00 AM, zhenhua.luo@freescale.com wrote:
> Hi all,
>
> Following is the proposal for FSL QorIQ SDK upstream, comment is welcome.

[snip]

>
> 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.


Can we get an update on the items listed above during tomorrow's 
community meeting (or soon afterwards)?

Also, I had previously asked about creating a branch on meta-fsl-ppc 
that could be used to track patches / improvements for SDK1.6 in 
addition to master, which I think is basically being used to set up 1.7.

I need to start getting after some bugs on SDK1.6 related to various 
kernel oops that pop up inconsistently.  I would love to see an 
infrastructure in place to help with this.

Thanks,

Bob






>
>
> Best Regards,
>
> Zhenhua
>



  parent reply	other threads:[~2014-09-08  1:05 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 ` Bob Cochran [this message]
2014-09-09 13:28   ` 9/8 community meeting, was " 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

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=540D00B7.5060604@mindchasers.com \
    --to=yocto@mindchasers.com \
    --cc=meta-freescale@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.