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=unavailable 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 2C182C433E9 for ; Thu, 18 Mar 2021 13:19:41 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id F394F64F1B for ; Thu, 18 Mar 2021 13:19:40 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231271AbhCRNTJ (ORCPT ); Thu, 18 Mar 2021 09:19:09 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39224 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230458AbhCRNSh (ORCPT ); Thu, 18 Mar 2021 09:18:37 -0400 Received: from mail-ot1-x32d.google.com (mail-ot1-x32d.google.com [IPv6:2607:f8b0:4864:20::32d]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 20234C061760 for ; Thu, 18 Mar 2021 06:18:37 -0700 (PDT) Received: by mail-ot1-x32d.google.com with SMTP id w31-20020a9d36220000b02901f2cbfc9743so4858735otb.7 for ; Thu, 18 Mar 2021 06:18:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ffwll.ch; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=v0u3U62VgqQ/5cx0dl1OlmbnmTob1+65hnEnMoAP8+g=; b=Wq2xIKdqjdfzxw2Myb5taaYoDXG0Mt5eTvw70t+Qfukgix/l82cWO0JuAAM9pp9Lr8 iuztkE2RYqfAeHvp28wsWDJ+QoGaPWC+Rv09fwMM2iRu/K2UOyFvuXajEDVEVPCoATb4 oF5XWjbtWmNZTiF6bVmPZ4xhDEvuykvOW88w0= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=v0u3U62VgqQ/5cx0dl1OlmbnmTob1+65hnEnMoAP8+g=; b=i+5FoDThMRsIFjOqS/QP3Gsvg+Duv98lSWQy8U6ePzBaJzXUREKrLPovWFTfNQDqpj kuruaMD6mQXhTcE2x7T3rRGtzChjoUqCeB2wy0bEw3hsidMPbm7t6kp44ihHaWs5b9eW ilKRgZs6f44ZgZuqmnXyDyAgmoMTVleNcL+2wQz8wJNCBcxRhHcL/qGFT2Yqfo6bCyny cVFKWitlvcyEXuUCoQI0gQH1UjwGTdCGPNjZG1xs6mZVnx72ltBwjgSPsHsm/auhbv2O Dq7pY3jbNqv0xTXjITNkT91fKXBXQL77Rrdx3yDKmtrZNuQaUkiYNuN1dsMSxUBt8MbP VDbg== X-Gm-Message-State: AOAM530xGSvTsRgDPFpwdxy2L5fHX0GKxcHFI0rF9YCeMYZmIkQWAGqI /eX/XVeNdjIqWrDaQxWD2gC9ekrxhN+ci6UVLJpnYw== X-Google-Smtp-Source: ABdhPJys7CWu1QW7sqaGp8DPpYtt4z4UFBXzAiTSc52E6cJ3FtAgdwRl3llcaxjGyQonUci42YLrVhEplIIDHitKc+k= X-Received: by 2002:a9d:63d6:: with SMTP id e22mr7303358otl.188.1616073516410; Thu, 18 Mar 2021 06:18:36 -0700 (PDT) MIME-Version: 1.0 References: <20210303134319.3160762-1-lee.jones@linaro.org> <16d4300e-bf29-1e85-317b-53d257890cb9@vmware.com> <20210308091932.GB4931@dell> <20210311135152.GT701493@dell> <20210317081729.GH701493@dell> In-Reply-To: From: Daniel Vetter Date: Thu, 18 Mar 2021 14:18:25 +0100 Message-ID: Subject: Re: [RESEND 00/53] Rid GPU from W=1 warnings To: Lee Jones Cc: Roland Scheidegger , Linux Kernel Mailing List , Alex Deucher , amd-gfx list , Anthony Koo , Ben Skeggs , =?UTF-8?Q?Christian_K=C3=B6nig?= , 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 Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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. -Daniel -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch