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 BD48EC433EF for ; Tue, 11 Jan 2022 09:42:57 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235485AbiAKJm4 (ORCPT ); Tue, 11 Jan 2022 04:42:56 -0500 Received: from mail-ua1-f43.google.com ([209.85.222.43]:45702 "EHLO mail-ua1-f43.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229629AbiAKJmz (ORCPT ); Tue, 11 Jan 2022 04:42:55 -0500 Received: by mail-ua1-f43.google.com with SMTP id x33so27224006uad.12; Tue, 11 Jan 2022 01:42:54 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=YYoFhZpMdrKIinjBqjY4BJ47Yl1lAi9aD03OcFH30xQ=; b=PFIY7PMVO4AJi9SCwbse3I0zalF/3ypRRIC/qfeeNO6jnDAyfwIeEottysxUoRz3QK 42rG68XKuBBOZIOyr/TV6a1yHE2owomY3Zw1Yvmi2dQc2yPyQNlbRiMTVmfzLPtLtnhW IRqi7w5lm2jA9kD/Q4QmTkAa9eNVud1xRrLNU6ScoAqFEc5wd8sn6AG+yLlCOYZSrJD0 uzbQVmXN9FZMMDLuWOCtYDht7KzzgWOwZzWKcKaPobashFdXNEldrb4DoHn6bqbP53v6 9zys1piNFqcGL5Y4BCFIxZI5JyKzwaGeh4MAlnqTXW/eBsCFJYvpAcpjANIa62xbdkQk /03Q== X-Gm-Message-State: AOAM532r9dwlYRLZOs8G2U+753KGaDOKaoCVIqvdIIKLA6Oo0pC7XrON 6VUPWR8oCfWV8UU0zcRgyEP14LPtVpPGcA== X-Google-Smtp-Source: ABdhPJxaChTMLOcDhW5LSEx1c4Tv6RLv+1yv/J57++sax1YelxnxpTCGA4SQcLpEjm4Ig6E9bgQMgQ== X-Received: by 2002:a9f:2acc:: with SMTP id d12mr1551139uaj.109.1641894174183; Tue, 11 Jan 2022 01:42:54 -0800 (PST) Received: from mail-ua1-f43.google.com (mail-ua1-f43.google.com. [209.85.222.43]) by smtp.gmail.com with ESMTPSA id c15sm5218266uaj.13.2022.01.11.01.42.53 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 11 Jan 2022 01:42:53 -0800 (PST) Received: by mail-ua1-f43.google.com with SMTP id p1so28534018uap.9; Tue, 11 Jan 2022 01:42:53 -0800 (PST) X-Received: by 2002:a05:6102:2329:: with SMTP id b9mr1668803vsa.5.1641894173002; Tue, 11 Jan 2022 01:42:53 -0800 (PST) MIME-Version: 1.0 References: <20220111011239.452837-1-jiasheng@iscas.ac.cn> In-Reply-To: <20220111011239.452837-1-jiasheng@iscas.ac.cn> From: Geert Uytterhoeven Date: Tue, 11 Jan 2022 10:42:41 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH] dmaengine: sh: rcar-dmac: Check for error num after dma_set_max_seg_size To: Jiasheng Jiang Cc: Vinod , Yoshihiro Shimoda , Laurent Pinchart , Wolfram Sang , Zou Wei , dmaengine , Linux Kernel Mailing List Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jan 11, 2022 at 2:12 AM Jiasheng Jiang wrote: > As the possible failure of the dma_set_max_seg_size(), it should be > better to check the return value of the dma_set_max_seg_size(). > > Fixes: 97d49c59e219 ("dmaengine: rcar-dmac: set scatter/gather max segment size") > Reported-by: Geert Uytterhoeven > Signed-off-by: Jiasheng Jiang Reviewed-by: Geert Uytterhoeven Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds