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=-8.6 required=3.0 tests=BAYES_00,DKIM_INVALID, DKIM_SIGNED,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 945D6C433B4 for ; Wed, 21 Apr 2021 09:12:28 +0000 (UTC) Received: from gabe.freedesktop.org (gabe.freedesktop.org [131.252.210.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 9B50C613E6 for ; Wed, 21 Apr 2021 09:12:27 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 9B50C613E6 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=ffwll.ch Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=dri-devel-bounces@lists.freedesktop.org Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id CD9F06E23F; Wed, 21 Apr 2021 09:12:26 +0000 (UTC) Received: from mail-ej1-x62a.google.com (mail-ej1-x62a.google.com [IPv6:2a00:1450:4864:20::62a]) by gabe.freedesktop.org (Postfix) with ESMTPS id 323B06E42F for ; Wed, 21 Apr 2021 09:12:26 +0000 (UTC) Received: by mail-ej1-x62a.google.com with SMTP id g5so55728200ejx.0 for ; Wed, 21 Apr 2021 02:12:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ffwll.ch; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to; bh=FEam5TET7rhN7+PR3mXypZotRQqC9IqmKKfFLGC0Cc4=; b=Iepkup3IaMiOfVhyXm8Bbckx6YcsWQ2s2PMMnKfIgyF5vuA3JHPpJ7oCxu07f77CFl NhFQP7+p72gmHHrl0Dc0sEwZclXd3QEQgViUb/DX1OY5xJ9U/46wQ/ADCKO4p67YtBGb yl1CIe/v9rWHBrjTuUR21RQXOS9k+Q8UvSOP4= 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=FEam5TET7rhN7+PR3mXypZotRQqC9IqmKKfFLGC0Cc4=; b=cgDOjghY7Q0zR1ntsb4sJhctNXMkdgO98GA2Rml8clIM/HCRMqNhHCXNdDrJl43D5r uWMhSgyONMywaYI5tQbees4dUDE4r8pjT+D4lktRytnAIwZwgAHZLW6bgM2LVRmMVn9X Q9weN2wwciYUM2cigPPqWp82KlcK7JlySLj/UnocVGSChJAmWufSQJoH5IAsCEKUk78q y8PkxOPrShvljn2tFDnijx7j5+IrtNbVipTIvYBGPRRC06VL23jRjUAHmLBsrfIPgV4G 5K7+M4zYz1ve+uPH3+Er938q2kZQW6FA4QrVggxhRbK3zaOVwRvKW1ivznXHWh/rwVyZ v24A== X-Gm-Message-State: AOAM533l+PSLFmdw5blmgIO8lxlbQbazrMXdMOdYEyhPcG56OnQAboWs AHoQkeQdxpXkPpaua2yQiAmMiA== X-Google-Smtp-Source: ABdhPJwRFLGQeI5LUaHl/xRUKCcQz20vdi9yS83zYlInGKxg8bjL2xita3Xtc67I179eBVX1eD8Pgw== X-Received: by 2002:a17:906:a10e:: with SMTP id t14mr31318076ejy.103.1618996344761; Wed, 21 Apr 2021 02:12:24 -0700 (PDT) Received: from phenom.ffwll.local ([2a02:168:57f4:0:efd0:b9e5:5ae6:c2fa]) by smtp.gmail.com with ESMTPSA id o17sm2489966edt.92.2021.04.21.02.12.23 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 21 Apr 2021 02:12:24 -0700 (PDT) Date: Wed, 21 Apr 2021 11:12:22 +0200 From: Daniel Vetter To: Christian =?iso-8859-1?Q?K=F6nig?= Subject: Re: [PATCH v3 5/7] drm/vmwgfx: Inline ttm_bo_mmap() into vmwgfx driver Message-ID: References: <20210416133146.24825-1-tzimmermann@suse.de> <20210416133146.24825-6-tzimmermann@suse.de> <80012c09-6975-f694-420f-72b2236dcf4e@amd.com> <52403618-62f5-2085-c245-e1e98762cccb@suse.de> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: X-Operating-System: Linux phenom 5.7.0-1-amd64 X-BeenThere: dri-devel@lists.freedesktop.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Direct Rendering Infrastructure - Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: amd-gfx list , "Sharma, Shashank" , Dave Airlie , Christian =?iso-8859-1?Q?K=F6nig?= , Felix Kuehling , Roland Scheidegger , Nirmoy Das , dri-devel , Huang Rui , VMware Graphics , Ben Skeggs , Thomas Zimmermann , Nouveau Dev , Alex Deucher , Sam Ravnborg , Emil Velikov Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" On Wed, Apr 21, 2021 at 09:01:00AM +0200, Christian K=F6nig wrote: > Am 20.04.21 um 22:53 schrieb Daniel Vetter: > > On Tue, Apr 20, 2021 at 10:23 PM Felix Kuehling wrote: > > > = > > > Am 2021-04-20 um 4:51 a.m. schrieb Daniel Vetter: > > > > > > Whole series is Reviewed-by: Christian K=F6nig > > > > > Thanks a lot. If I'm not mistaken, the patches at [1] need to go = in first. > > > > > So it could take a a bit until this lands. > > > > > = > > > > > Otherwise, this series could go through the same tree as [1] if n= ouveau and > > > > > vmwgfx devs don't mind. > > > > I would land it all through drm-misc-next. Maybe check with Alex on= irc > > > > for an ack for merging that way, but I don't think this will cause = issues > > > > against the amdgpu tree. Lots of ttm cleanup has landed this way al= ready > > > > past few months. Otherwise you could create a small topic branch wi= th > > > > these patches here and send that to Alex, and he can sort out the > > > > interaction with Felix' series. > > > > -Daniel > > > My patch series involved some pretty far-reaching changes in KFD > > > (renaming some variables in KFD and amdgpu, changing the KFD->amdgpu > > > interface). We already submitted other patches on top of it that have > > > dependencies on it. If we decide to deliver this through a different > > > tree and remove it from amd-staging-drm-next, there will be conflicts= to > > > resolve when removing it from amd-staging-drm-next, and again the next > > > time you merge with amd-staging-drm-next. > > Ah then the usual way is for Alex to assemble a topic pull request > > (stable, non-rebasing) with those select patches, which then gets > > merged into drm-misc-next. Or we smash it all into amdgpu-next. Or we > > just wait until -rc2 when drm-next is back open for business. > = > I need to double check, but if I'm not totally mistaken the changes in > question should already be in drm-next. > = > But exactly that was the reason why I asked when the next backmerge from > drm-next into drm-misc-next is planned :) Best way to make that happen isn't to ask when it will happen, but tell drm-misc maintainers to do it and why (ideally with references to the commits you need). Also I tend to do those requests over irc. Backmerges are generally on demand, not on schedule. Hence you need to demand one :-) -Daniel -- = Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel