From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-10.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_CR_TRAILER, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id C9AD9C433E6 for ; Fri, 19 Mar 2021 08:25:00 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 895FD64F6D for ; Fri, 19 Mar 2021 08:25:00 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234240AbhCSIYW (ORCPT ); Fri, 19 Mar 2021 04:24:22 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:32904 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233819AbhCSIYM (ORCPT ); Fri, 19 Mar 2021 04:24:12 -0400 Received: from mail-ed1-x52c.google.com (mail-ed1-x52c.google.com [IPv6:2a00:1450:4864:20::52c]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B846BC06174A for ; Fri, 19 Mar 2021 01:24:11 -0700 (PDT) Received: by mail-ed1-x52c.google.com with SMTP id bx7so9719820edb.12 for ; Fri, 19 Mar 2021 01:24:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to; bh=i3ME3RZycqfcfKl/INYO3mj0pc2g5bpS8vxgj1H2Zho=; b=P+5LihIKwLgCsx10OfJIAw04qzyiTgtZ+9mVR3WckS2IOAidGoGZL3ddGFqeTyiWrx HFNLGJkkIgVaAyVKZXa3FE1/nuP6JHJbyOdedNBMMzQp/iT+6gDLy1aJtYevlvk92o+g FOiw14Uq3K23+15kZQxvtt3z0iFriNPPHzkntAqWaThhUj0y5bOV/LkWWvM5vboi3NL6 nruXC6lGYs+ze7MJBrOuFwiI1j/aNoW14FE/UHwTmaxsYLtiY6iwiT8Nknb+edBW42sw /gW2YDfE/zZkyFLp5hFpuBA/KGScPE/fy3K2x45r7r5KCQ161p+ccfRVEUZjHFsRSn6F rnRQ== 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:content-transfer-encoding :in-reply-to; bh=i3ME3RZycqfcfKl/INYO3mj0pc2g5bpS8vxgj1H2Zho=; b=cF9AuCMGwoSGMfplrf6wmUmFgLNOES2kv6df0F/7JqzF4lkrzkOxXrBSyU6oUxja3p VS5ewp0b4tGks51g2kZ5IpevfCWIL5G6B9l2SHyqJEpL5igfm4eW004oFCPr3h5vIIgf JH9qZOZkV0TImfxoQyhcjeXx+fDFAv4LmqX/Ze/Me6qXh1DfX/t6iRJfjPILCK2RD/Bh neeKB2jBLzzoyZB9oaE7gDXoicPhpju6cM1U327C+gruQem51YyGwSkk5PYTcpjdMLVE 1LemboNACIsK6GL7V8C2RDiDobdu7AjTOdRhJ2Lb3P+SftcXQQD4lV6M8GDENUBJfeEH DFUg== X-Gm-Message-State: AOAM530Kh+1ymHMjV5MOJg9mUxMqNW7TxMZDkA7GyViQTDAeOb9XwwYe IAqTRRFPwcxSkQXgRP9inCNvRA== X-Google-Smtp-Source: ABdhPJwvsynmGTO200msXpOq0tH3ulqN/PugQIqOCYp1LVOxM4bgeagMgSBC0AYVkGV7Fb9kcROngA== X-Received: by 2002:a05:6402:17af:: with SMTP id j15mr8214688edy.50.1616142250503; Fri, 19 Mar 2021 01:24:10 -0700 (PDT) Received: from dell ([91.110.221.194]) by smtp.gmail.com with ESMTPSA id gb4sm3185084ejc.122.2021.03.19.01.24.09 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 19 Mar 2021 01:24:10 -0700 (PDT) Date: Fri, 19 Mar 2021 08:24:07 +0000 From: Lee Jones To: Daniel Vetter Cc: Roland Scheidegger , Linux Kernel Mailing List , Alex Deucher , amd-gfx list , Anthony Koo , Ben Skeggs , Christian =?iso-8859-1?Q?K=F6nig?= , Colin Ian King , Dave Airlie , David Airlie , dri-devel , freedreno , Harry Wentland , Jeremy Kolb , Kuogee Hsieh , Leo Li , "moderated list:DMA BUFFER SHARING FRAMEWORK" , linux-arm-msm , "open list:DMA BUFFER SHARING FRAMEWORK" , Lyude Paul , Maarten Lankhorst , Maxime Ripard , Nouveau Dev , Qinglang Miao , Rob Clark , Rob Clark , Sean Paul , Sumit Semwal , Thomas Zimmermann , VMware Graphics , Zack Rusin Subject: Re: [RESEND 00/53] Rid GPU from W=1 warnings Message-ID: <20210319082407.GG2916463@dell> References: <20210303134319.3160762-1-lee.jones@linaro.org> <16d4300e-bf29-1e85-317b-53d257890cb9@vmware.com> <20210308091932.GB4931@dell> <20210311135152.GT701493@dell> <20210317081729.GH701493@dell> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-media@vger.kernel.org On Thu, 18 Mar 2021, Daniel Vetter wrote: > On Wed, Mar 17, 2021 at 9:32 PM Daniel Vetter wrote: > > > > On Wed, Mar 17, 2021 at 9:17 AM Lee Jones wrote: > > > > > > On Thu, 11 Mar 2021, Lee Jones wrote: > > > > > > > On Thu, 11 Mar 2021, Daniel Vetter wrote: > > > > > > > > > On Mon, Mar 08, 2021 at 09:19:32AM +0000, Lee Jones wrote: > > > > > > On Fri, 05 Mar 2021, Roland Scheidegger wrote: > > > > > > > > > > > > > The vmwgfx ones look all good to me, so for > > > > > > > 23-53: Reviewed-by: Roland Scheidegger > > > > > > > That said, they were already signed off by Zack, so not sure what > > > > > > > happened here. > > > > > > > > > > > > Yes, they were accepted at one point, then dropped without a reason. > > > > > > > > > > > > Since I rebased onto the latest -next, I had to pluck them back out of > > > > > > a previous one. > > > > > > > > > > They should show up in linux-next again. We merge patches for next merge > > > > > window even during the current merge window, but need to make sure they > > > > > don't pollute linux-next. Occasionally the cut off is wrong so patches > > > > > show up, and then get pulled again. > > > > > > > > > > Unfortunately especially the 5.12 merge cycle was very wobbly due to some > > > > > confusion here. But your patches should all be in linux-next again (they > > > > > are queued up for 5.13 in drm-misc-next, I checked that). > > > > > > > > > > Sorry for the confusion here. > > > > > > > > Oh, I see. Well so long as they don't get dropped, I'll be happy. > > > > > > > > Thanks for the explanation Daniel > > > > > > After rebasing today, all of my GPU patches have remained. Would > > > someone be kind enough to check that everything is still in order > > > please? > > > > It's still broken somehow. I've kiced Maxime and Maarten again, > > they're also on this thread. > > You're patches have made it into drm-next meanwhile, so they should > show up in linux-next through that tree at least. Except if that one > also has some trouble. Thanks for letting me know. I see some patches made it back in, others didn't. I'll resend the stragglers - bear with. -- Lee Jones [李琼斯] Senior Technical Lead - Developer Services Linaro.org │ Open source software for Arm SoCs Follow Linaro: Facebook | Twitter | Blog