From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 2B4B0E00D15; Fri, 5 Apr 2019 10:13:38 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider * (twoerner[at]gmail.com) * -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's * domain * -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature * 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily * valid * -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at https://www.dnswl.org/, no * trust * [209.85.166.65 listed in list.dnswl.org] Received: from mail-io1-f65.google.com (mail-io1-f65.google.com [209.85.166.65]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 446A4E00BB7 for ; Fri, 5 Apr 2019 10:13:35 -0700 (PDT) Received: by mail-io1-f65.google.com with SMTP id p23so4984621iol.13 for ; Fri, 05 Apr 2019 10:13:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=LmSkDyEatRarESps7Za4hsEGyS3BjvGM9xwhkIBzZys=; b=fOgZohnogNrzN8scFZk2syiq3E9U41c+MJtFQNNGynCmWtL919mcDJP0s/Me0jInPK 7mnazx1+EMbqtozH1z9e7FHwiWiLL+ijriD7I38ylcZEgkhx3ihWuxGGcnUFuHBk/bbq R8SAPVAZV5aXfqQJPYRu3joAFg5MIYEfPEGT19yG1HCfO6OFmae11OJReZTrgTlStpI2 TVjP5LTve7nO60TSY/ipFl21IlntppiOAY2M5t9KpF/M7ddcwmKVA0spxx4lWZlH3q+t wiAGPSXkQPEroDzvEZ9nUgwgQdQpNT9XJ1vyzXT5BwSQERAvQHjWUHO2LKJiLVpL5BY5 6CCQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=LmSkDyEatRarESps7Za4hsEGyS3BjvGM9xwhkIBzZys=; b=ngfy/mBWoFK4oVhnK6EO1aAwMtfT8uE1D7xmQqGXNxYW82d7HHhDwJHus/gTmXDVSj k3NBK314e1J5+/7hY4odOD/kGGXOyvl5no2C2HKFDHdTu2d7IBKfh8apTpoIg/83efzz 5v24GjX1978Nw4Xgi6IvFb2cDx5S+1+GlZg/IoSlHbFFNGUrjjE1pGjCeUQXVMX/bm97 moYgrI7D9qzZxAFZAARgSZzHO30uskVymNa2EMursxPK3koILkE4K35eZviLXB9hu1AT 4jXczC73EiYlQMzAHoWY+0XIhzqI1NJjhn1tuyp+aK5C6WVV9pg8Fh9LIyQeT/Zx1XHz MJLA== X-Gm-Message-State: APjAAAVlCorGGCKI5VlLbd2tcm2GItSWxK3nVwriNyjJBSbBnEmD1Lqt sB7OnDBqN6WrxInbP4wh7Csd+bYM X-Google-Smtp-Source: APXvYqz3liP12Qt877jQLSszVf75CYIIcODayYndBxLKXucKHPYdx58SdBUELLHH1Glo+AIm7WEklw== X-Received: by 2002:a6b:7519:: with SMTP id l25mr10221854ioh.51.1554484415322; Fri, 05 Apr 2019 10:13:35 -0700 (PDT) Received: from linux-uys3 ([206.248.190.95]) by smtp.gmail.com with ESMTPSA id e11sm8359445iob.48.2019.04.05.10.13.33 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 05 Apr 2019 10:13:34 -0700 (PDT) Date: Fri, 5 Apr 2019 13:13:31 -0400 From: Trevor Woerner To: Otavio Salvador Message-ID: <20190405171331.GA28564@linux-uys3> References: <20190327182204.29498-1-trevor@toganlabs.com> MIME-Version: 1.0 In-Reply-To: User-Agent: Mutt/1.6.0 (2016-04-01) Cc: meta-freescale Mailing List Subject: Re: [PATCH] mesa%bbappend: switch imx to kmsro 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: Fri, 05 Apr 2019 17:13:38 -0000 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline On Mon 2019-04-01 @ 02:05:58 PM, Otavio Salvador wrote: > Yes, we were carrying this during the mesa update and keeping it local > until it reached master. I am sorry you ended having it been affected > by this issue but we try to be as fast as possible. > > As said here, we moved out from mailing list for patches, as github is > nicer for high volume and also easier to not loose patches and > contributions so we have been doing this way now. Ah, that explains it! :-) No worries, thanks for the update. I'll be sure to use the new workflow :-)