From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ob0-f175.google.com (mail-ob0-f175.google.com [209.85.214.175]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 3CE55E006DD for ; Wed, 17 Jul 2013 14:02:28 -0700 (PDT) Received: by mail-ob0-f175.google.com with SMTP id xn12so2895151obc.34 for ; Wed, 17 Jul 2013 14:02:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=is7q8QfMe0o4ED8NcGiOy3YXQy/nPXNz2QGp9QPyB0c=; b=hJeAy2A4QlFYLRLHolanRWWnTKtRe/pC7bLxIGB/GTBXEDpgtjQiJNIPiEFcbNmnUN bq3y2w59kqQhE2i/TXn1F3fONIYVKU4P5o/YWYdi4HXhiQ43+v9ypEs614wx+riHOecz yOfSxmTEicjCYYeZle1GrmA4X164CMh6va1uDCY3NbzHNzCMH0uB4G+GNsiPNaMNxKZL CWZRW/ghfujA7lxCSHe/kHHyyXIzgaPfhiXCabsU1U1fXpr3iYbiZ9+lDRs8o9dyRdyX tjbqf+hTopYLsHCUUFkgiVVEXNhcxjhUufU4kUt/Cm53QR0roO6SqhclDlxcQ6wEJ6TC f3TQ== MIME-Version: 1.0 X-Received: by 10.182.142.104 with SMTP id rv8mr4542132obb.3.1374094947472; Wed, 17 Jul 2013 14:02:27 -0700 (PDT) Sender: otavio.salvador@gmail.com Received: by 10.182.60.166 with HTTP; Wed, 17 Jul 2013 14:02:27 -0700 (PDT) In-Reply-To: <51E701DD.3040905@freescale.com> References: <999FEFBC61661A4099B55CE06B5D10755377FC@039-SN1MPN1-001.039d.mgd.msft.net> <1714287.19idnEh5B1@rudolf> <999FEFBC61661A4099B55CE06B5D107553783F@039-SN1MPN1-001.039d.mgd.msft.net> <20130717101347.537b91c2@e6520eb> <20130717142654.107d37c3@e6520eb> <20130717143302.7fc2415b@e6520eb> <20130717150116.6e1d70af@e6520eb> <51E701DD.3040905@freescale.com> Date: Wed, 17 Jul 2013 18:02:27 -0300 X-Google-Sender-Auth: GXq_F-qXeIMTS7EexA8J5RghicE Message-ID: From: Otavio Salvador To: Daiane Angolini Cc: "meta-freescale@yoctoproject.org" Subject: Re: GPU 2d/3d acceleration not working in yocto qte-in-use-image X-BeenThere: meta-freescale@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-fsl-* layers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Jul 2013 21:02:29 -0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Wed, Jul 17, 2013 at 5:43 PM, Daiane Angolini wrote: > On 07/17/2013 10:14 AM, Otavio Salvador wrote: >> >> On Wed, Jul 17, 2013 at 10:01 AM, Eric B=E9nard wrote: >>> >>> Le Wed, 17 Jul 2013 09:37:09 -0300, >>> Otavio Salvador a =E9crit : >>> >>>> On Wed, Jul 17, 2013 at 9:33 AM, Eric B=E9nard wrote= : >>>>> >>>>> Le Wed, 17 Jul 2013 09:30:18 -0300, >>>>> Otavio Salvador a =E9crit : >>>>>> >>>>>> Those in master-next will be send to mailing list for review. >>>>>> >>>>> so if I understand well master-next is a sandbox which can get commit= s >>>>> not sent to the ML ? >>>> >>>> >>>> No; master-next is a place I have been using to push things to >>>> autobuilder or people test. It sometimes has patches not sent to >>>> mailing list for my convenience so I can get autobuilder test and >>>> feedback. >>> >>> >>> so you confirm that master-next can get commits not sent to the ML so >>> the answer to the question is "yes" ;-) that's not a big issue for >>> master-next the only thing is to be aware of that. >>> >>> Just FYI, unless I'm mistaken, these ones are in master and were not >>> sent to the ML : >>> >>> http://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-arm/commit/?id=3D30f= 65ca2688a4c94f9790968fa2a8408e8e50a34 >>> >>> http://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-arm/commit/?id=3D539= 8e59900cfceb995f924bd06dc8e3801599767 >>> >>> http://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-arm/commit/?id=3D4a9= 1984318cbc8c8b56f319a6eb7856e81fa9cac >>> >>> http://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-arm/commit/?id=3Ddaf= 582c93a7283fb0af3b25fe2ada48f4c9985c4 >>> >>> http://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-arm/commit/?id=3Dba4= 87405f60c38ea2a77b7a6866f954b665eefa7 >>> >>> http://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-arm/commit/?id=3Dd48= e4022824a13206f2a893759cf332a174e6d7d >>> >>> http://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-arm/commit/?id=3Df8a= 8a5eddc9e0d7e39e219dfb1fd137c8f77addc >>> >>> http://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-arm/commit/?id=3D1cb= 885570c9666bf4c7f8986623fc66988cec292 >>> >>> Here again not a big problem : the only thing is to be aware patches ca= n >>> reach master without being sent to the ML, that can be important for >>> peoples having external layers based on meta-fsl-arm's master branch. >> >> >> Yes and if you check those they're build failure fixes (except the >> duplicated assignment in mx28evk) so I could keep autobuilder and >> users being able to build. So this is the exception :-) > > I don't agree it should exists any exception for this. For everything there're an exception. However those patches were failures which NO ONE fixed and I use daily build for checking the quality of the BSP so it being broken is a problem for me. It is clear that *most* people do not run updated master branches (or they'd have got those failures and send a patch). > I really think any merged patch MUST be sent to ML previously. Most are send. Except the exceptions as said above. > I've been "accepting" your master-next approach only because I don't thin= k > it matter for anyone. However, we must be sure what have in master. There's GIT for it. If people matter GIT log have all the information and I try to keep informative logs. > Is there any restriction from Yoctoproject daily build server that it mus= t > build every single time, with no failure? No; this is my restriction. The more time it is failing to build more failure accumulate and I keep it working all the time to avoid having hidden issues there. Regards, -- Otavio Salvador O.S. Systems http://www.ossystems.com.br http://projetos.ossystems.com.br Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750