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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id C9503C433EF for ; Wed, 6 Jul 2022 14:57:36 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232302AbiGFO5f (ORCPT ); Wed, 6 Jul 2022 10:57:35 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:44344 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233130AbiGFO5c (ORCPT ); Wed, 6 Jul 2022 10:57:32 -0400 Received: from madras.collabora.co.uk (madras.collabora.co.uk [46.235.227.172]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 25FD3A1B0 for ; Wed, 6 Jul 2022 07:57:31 -0700 (PDT) Received: from [192.168.2.145] (109-252-119-232.nat.spd-mgts.ru [109.252.119.232]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: dmitry.osipenko) by madras.collabora.co.uk (Postfix) with ESMTPSA id E876366019AA; Wed, 6 Jul 2022 15:57:28 +0100 (BST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=collabora.com; s=mail; t=1657119449; bh=gKKVNdBjcN8KkoeprOxQ8ffGlP7W2ucwq70DNkoi0pM=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=AFo5SHqa1+b4dKZSAM5aDazw8Dg2FSqMDEb3VHe4xH5gT2saeZZZURl7+B4fIuO7W YFfBEEN4fNQmNUyiudA4KYXf+8e7c8bOOjy/hoVWKs8W1XSCJ3qmtfYpXtJFWmswcI an0mMfgGHr9fFc2LS2KrBOhUoH2qUxqsZxx3/SjV3lzhtfX1qujv2JEgNOFzsKa0HO XhOVOWY4yr6+GasG6QxhB4zXKuMAJ3RdbwDectgJ0Kmyj0zZ7gE6OfzvwcAvEGIm37 lHf8Lw66AuZovpAJ0Cxwdn2UsegQD/cvnZsJ5LP9C3PTgqzsIbE6uoCrNZa3wOPj/9 MimulBF98GOog== Message-ID: <4cb8ef00-1b8a-7ef0-aa4c-be0912aba496@collabora.com> Date: Wed, 6 Jul 2022 17:57:25 +0300 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.10.0 Subject: Re: [PATCH v1] drm/scheduler: Don't kill jobs in interrupt context Content-Language: en-US To: Andrey Grodzovsky , Erico Nunes , Steven Price Cc: David Airlie , Daniel Vetter , Tomeu Vizoso , Rob Herring , Alyssa Rosenzweig , Rob Clark , Dmitry Osipenko , linux-kernel , dri-devel References: <20220411221536.283312-1-dmitry.osipenko@collabora.com> <573fae0d-c9ab-98b0-c6f1-5b0d4e52dd01@amd.com> <107fe968-8311-0511-cc31-22feb994a6d7@collabora.com> <3e07a8d0-2cbc-8f3e-8f9f-5b73fb82028b@amd.com> From: Dmitry Osipenko In-Reply-To: <3e07a8d0-2cbc-8f3e-8f9f-5b73fb82028b@amd.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 7/6/22 16:49, Andrey Grodzovsky wrote: > On 2022-07-06 03:07, Dmitry Osipenko wrote: > >> Hello Andrey, >> >> On 5/17/22 17:48, Dmitry Osipenko wrote: >>> On 5/17/22 17:13, Andrey Grodzovsky wrote: >>>> Done. >>>> >>>> Andrey >>> Awesome, thank you! >>> >> Given that this drm-scheduler issue needs to be fixed in the 5.19-RC and >> earlier, shouldn't it be in the drm-fixes and not in drm-next? > > > I pushed it into drm-misc from where it got into drm-next. I don't have > permission for drm-fixes. Thank you -- Best regards, Dmitry