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=-0.6 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no 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 2B08EC43331 for ; Mon, 30 Mar 2020 09:39:54 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id F0CD02072E for ; Mon, 30 Mar 2020 09:39:53 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="qbVjwtVD" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728680AbgC3Jjw (ORCPT ); Mon, 30 Mar 2020 05:39:52 -0400 Received: from mail-io1-f68.google.com ([209.85.166.68]:39653 "EHLO mail-io1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726127AbgC3Jjw (ORCPT ); Mon, 30 Mar 2020 05:39:52 -0400 Received: by mail-io1-f68.google.com with SMTP id c16so2560449iod.6 for ; Mon, 30 Mar 2020 02:39:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=c1gUtwRvLYdtrLbJA/IGQZdtPAAqrGpsy+JPnbE+NNQ=; b=qbVjwtVD2BzCf+Qpuozkb4s5p58/+w8HArwivwoaXjhQM4BRBbJZD1kjXjvrGMR2Sc c01PLmgHVLFPuJdFniHGMXu2w6rLIvzSQLvalO8Q/dKJVfnW9vg91QmDa9qpqpZ7A/ZS NDnjOyLxG5uOej6SWj2xLai2CEnoKXDf6G/88kxwgjdURScr1KviSCU82A3r3qOvk7Za GBKGw86I9wMmNFgdiGiFT5xs9qqCa/TWhd9uDOg/D0UssIN9Xx67PlvK9ktcyPpHSzvN QQdk9LkTYzni3Q3RY1WZbO9dB2TpaMazsGCIZeybPYWY90TNh+m5vd71koBGJ9unsrrI ZAPg== 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=c1gUtwRvLYdtrLbJA/IGQZdtPAAqrGpsy+JPnbE+NNQ=; b=s2OuG0zGT3XI9YoFtPSkGgVlQLNNtX3nCURYo9ccccteZGMlIRaYIiOrqBWvazA192 Q/VACLTOraec6E7cEGTxpEHkcoV6IvNNKX2mhXKOQQf5ORIzuesFP1gJv7OVwFeS941a 8XzPVJm6AmjQoJwYCoardEBGQOnGYxLssfrF067OejK0s0zTIznXLJ3+y9nTo3F4fBh5 qEgKZ/NPgzhodZgduZ+iJG4xs9BFb0tgFE5aHvIgjyJcjKkI++ax4JLtg0FQen9HSW6N ix62GjzL13ep7kjfSN2IeASYE81Hc9yRd/2Vv300A2LJyyvBr0vI7f6USoE9rhHPGMfv uB8w== X-Gm-Message-State: ANhLgQ1p7EExOV0svND6v5lXBFFi2TxJfum/usD6iCm1In0sfIFo5Q49 pbPJMsAS06wp9ZV+ce9EpJAqh5Gup6z85GODqx8= X-Google-Smtp-Source: ADFU+vtaoT6KjcJ9ecQiB0qXnt+YZYGFPOYnZ5jKaU4tddPcw7WZUkopfgN0n8FZ4HONOwByDpEh1zQSusUc3tl1iv0= X-Received: by 2002:a6b:c916:: with SMTP id z22mr9873080iof.138.1585561191793; Mon, 30 Mar 2020 02:39:51 -0700 (PDT) MIME-Version: 1.0 References: <20200325090741.21957-2-bigbeeshane@gmail.com> <4aef60ff-d9e4-d3d0-1a28-8c2dc3b94271@samsung.com> <82df6735-1cf0-e31f-29cc-f7d07bdaf346@amd.com> In-Reply-To: From: Shane Francis Date: Mon, 30 Mar 2020 10:39:41 +0100 Message-ID: Subject: Re: [v4,1/3] drm/prime: use dma length macro when mapping sg To: Marek Szyprowski , =?UTF-8?Q?Christian_K=C3=B6nig?= Cc: Maling list - DRI developers , David Airlie , linux-kernel@vger.kernel.org, amd-gfx-request@lists.freedesktop.org, Alex Deucher Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Mar 30, 2020 at 9:18 AM Marek Szyprowski wrote: > Today I've noticed that this patch went to final v5.6 without even a day > of testing in linux-next, so v5.6 is broken on Exynos and probably a few > other ARM archs, which rely on the drm_prime_sg_to_page_addr_arrays > function. > > Best regards > -- > Marek Szyprowski, PhD > Samsung R&D Institute Poland > Not sure what the full merge pipeline is here, but my original patch was not sent to the stable mailing list. So I would assume that it went through the normal release gates / checks ? If there was a fault on the way I uploaded the patches I do apologise however I did follow the normal guidelines as far as I understood them. Personally I did validate this patch on systems with Intel and AMD GFX, unfortunately I do not have any ARM based dev kits that are able to run mainline (was never able to get an Nvidia TK1 to boot outside of L4T) 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=-0.3 required=3.0 tests=DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no 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 7EA50C2D0EB for ; Mon, 30 Mar 2020 09:39:54 +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 5486F20714 for ; Mon, 30 Mar 2020 09:39:54 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="qbVjwtVD" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 5486F20714 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=gmail.com 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 6956B89DC1; Mon, 30 Mar 2020 09:39:53 +0000 (UTC) Received: from mail-io1-xd44.google.com (mail-io1-xd44.google.com [IPv6:2607:f8b0:4864:20::d44]) by gabe.freedesktop.org (Postfix) with ESMTPS id 6187589DC1 for ; Mon, 30 Mar 2020 09:39:52 +0000 (UTC) Received: by mail-io1-xd44.google.com with SMTP id a24so16361347iol.12; Mon, 30 Mar 2020 02:39:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=c1gUtwRvLYdtrLbJA/IGQZdtPAAqrGpsy+JPnbE+NNQ=; b=qbVjwtVD2BzCf+Qpuozkb4s5p58/+w8HArwivwoaXjhQM4BRBbJZD1kjXjvrGMR2Sc c01PLmgHVLFPuJdFniHGMXu2w6rLIvzSQLvalO8Q/dKJVfnW9vg91QmDa9qpqpZ7A/ZS NDnjOyLxG5uOej6SWj2xLai2CEnoKXDf6G/88kxwgjdURScr1KviSCU82A3r3qOvk7Za GBKGw86I9wMmNFgdiGiFT5xs9qqCa/TWhd9uDOg/D0UssIN9Xx67PlvK9ktcyPpHSzvN QQdk9LkTYzni3Q3RY1WZbO9dB2TpaMazsGCIZeybPYWY90TNh+m5vd71koBGJ9unsrrI ZAPg== 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=c1gUtwRvLYdtrLbJA/IGQZdtPAAqrGpsy+JPnbE+NNQ=; b=dZ0KYYDEOCMXhfxFL9Jv0xj8KIJsU9pX2JgsEIsk/YWVMqrsxkI7JyEPKPbTgh0A1t dc3c7YFTnXhuOn8U7uzhBsx1cen4OMT1xp4yvhrpMiael1KFABEgRP6JJouPoT7f6aYl bnP53VPllXkDzNwyouFdwpDcNrFYTZLx25yeTAOiRbqbAdfd36fAh09FMXA0pQ8mrApE IfI5RiHmzCvx0KxkusNe12x0Frr7Eu4j+TOpYV5AzZkCg2pxoWl8ZzwBdQeWPPvWZxzt +PU0Uv7mHcLzGuWn7hBAopBOyi+Gk9mcDrhQg9lwleSfpcS2Z1M2kbahboK0p6gUPaId 1x3w== X-Gm-Message-State: ANhLgQ0o8SyOaCqEN5WGLzLB/iJrkDzudj1ZJwQFbwxJGerXBQSbgFH/ CXtHVdYfR/zYX2Pu9vpJb0cdNwGoYFTalR0NyODLY4FP5mM= X-Google-Smtp-Source: ADFU+vtaoT6KjcJ9ecQiB0qXnt+YZYGFPOYnZ5jKaU4tddPcw7WZUkopfgN0n8FZ4HONOwByDpEh1zQSusUc3tl1iv0= X-Received: by 2002:a6b:c916:: with SMTP id z22mr9873080iof.138.1585561191793; Mon, 30 Mar 2020 02:39:51 -0700 (PDT) MIME-Version: 1.0 References: <20200325090741.21957-2-bigbeeshane@gmail.com> <4aef60ff-d9e4-d3d0-1a28-8c2dc3b94271@samsung.com> <82df6735-1cf0-e31f-29cc-f7d07bdaf346@amd.com> In-Reply-To: From: Shane Francis Date: Mon, 30 Mar 2020 10:39:41 +0100 Message-ID: Subject: Re: [v4,1/3] drm/prime: use dma length macro when mapping sg To: Marek Szyprowski , =?UTF-8?Q?Christian_K=C3=B6nig?= 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: David Airlie , Alex Deucher , amd-gfx-request@lists.freedesktop.org, linux-kernel@vger.kernel.org, Maling list - DRI developers Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" On Mon, Mar 30, 2020 at 9:18 AM Marek Szyprowski wrote: > Today I've noticed that this patch went to final v5.6 without even a day > of testing in linux-next, so v5.6 is broken on Exynos and probably a few > other ARM archs, which rely on the drm_prime_sg_to_page_addr_arrays > function. > > Best regards > -- > Marek Szyprowski, PhD > Samsung R&D Institute Poland > Not sure what the full merge pipeline is here, but my original patch was not sent to the stable mailing list. So I would assume that it went through the normal release gates / checks ? If there was a fault on the way I uploaded the patches I do apologise however I did follow the normal guidelines as far as I understood them. Personally I did validate this patch on systems with Intel and AMD GFX, unfortunately I do not have any ARM based dev kits that are able to run mainline (was never able to get an Nvidia TK1 to boot outside of L4T) _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel