Received: by 2002:a05:6a10:9848:0:0:0:0 with SMTP id x8csp1513970pxf; Fri, 19 Mar 2021 08:44:40 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzfbapcsKNjrmaOYBcfo9CGetM+3zi0PRDJlH6IQFqtEKvr7xwGgq3F+QVC4IEbIVkDX7aZ X-Received: by 2002:a17:907:a04f:: with SMTP id gz15mr4991947ejc.293.1616168679859; Fri, 19 Mar 2021 08:44:39 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1616168679; cv=none; d=google.com; s=arc-20160816; b=brEGmKDVJLHtKAIWDrbz9X2295/HQT6ddbrOdH359yBTxBBz8JvVBAJT1m94tp9FZD VmNBjOOef/0Q/4X0fB7bm8vCMFZ8sQVTlyHiKn+3UHPo1WhRw8sBmHQMz4pOJ4bLJazT WuZqX1BS7EaBRdw2dPRRM/sP/kwcEfILIo1NwxnQYmrJBFnFkQEG7y8I6Dr5wurCthKt o47n4h7Ayrdi9wLgnupPfLOoQ7E9niURzxMcl8yrGgzTX0MBsGcFtmwdZOb3Q2Z+nwRC IuNEhNa6wOdxyEhgxg1R4au1l0ooGZd5uiFK2UK3t+R1ogBIxmiQEccEEmNV+ynccinW i8rA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:date:cc:to:from:subject :message-id:dkim-signature; bh=AosAsdPYu9Ufpf4Wk/dfAmNbL8dSXdLyf4cxfVtJsJs=; b=rv3lGI1W1s1fuRDlvIqyq/LlI8Ugnp3y0FLowoJfbLZOGGZN+0fA5yg8iYRhwgYgLZ 1oQSy/h/ruAi31UZFIlzinhMhuVPClbKUHMx0i7P3P/x+e1CCOXukKYOAomgIvNt5xqz gdStCE+tpE8DHiPRqlTX22Y/Ol9A/NxU+ADugGOHlW2dZE4PGL/W0sRleEiadWx3FPkx xoeGb24Yj1zdxr8n//I9vrNwV82wtsxmiHOH30I/UOnp35ed7UuWvsZKiKGcNAOtfsop G4GgwkjTEERbrh9e2EBRC6xa5k75AzwYNCvpefIJj5Frp0SW8XKFikSFLyuPiSCKEMle zjkg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=lyiABF6F; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id g20si4441801edt.518.2021.03.19.08.44.16; Fri, 19 Mar 2021 08:44:39 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=lyiABF6F; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229978AbhCSPnQ (ORCPT + 99 others); Fri, 19 Mar 2021 11:43:16 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:42846 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229914AbhCSPmq (ORCPT ); Fri, 19 Mar 2021 11:42:46 -0400 Received: from mail-ej1-x62e.google.com (mail-ej1-x62e.google.com [IPv6:2a00:1450:4864:20::62e]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 95107C06174A; Fri, 19 Mar 2021 08:42:45 -0700 (PDT) Received: by mail-ej1-x62e.google.com with SMTP id b9so10456097ejc.11; Fri, 19 Mar 2021 08:42:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=message-id:subject:from:to:cc:date:in-reply-to:references :user-agent:mime-version:content-transfer-encoding; bh=AosAsdPYu9Ufpf4Wk/dfAmNbL8dSXdLyf4cxfVtJsJs=; b=lyiABF6FyD5T6JqaesOU6h9kIR+cKrn1Sh7bTfLrms514h0BC0oBI8qKQ5kFm8M212 UH2rhod/YmnMU1/eLyFO1c2a+E+vdnNN1kPXazbx1W+g0MpCjxaFCzmHJlXQmAIrwaPU U2ReVax7N3j2SopCQcveKL9Yi83d2Xyn888ybrDJdvbFcCVPGLa8edUQ5RVIyzAsvL1a mfR4ba5Hss1Ze48Z/zR1LQ2HUTG5JqoZ9IDxfjoCTY7fQo7/UglYIhJUv5mnDkpGRO44 zPrxTmF8BixYWaA/YUdRu80+XpSHYlvrzqAhSPI399dUn5hUksURO5SnvohjEALl0ZBf iosg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:cc:date:in-reply-to :references:user-agent:mime-version:content-transfer-encoding; bh=AosAsdPYu9Ufpf4Wk/dfAmNbL8dSXdLyf4cxfVtJsJs=; b=EAGmXnK8SMk2wIYa80RVs1pu0iQpTn7wiNbhx8KcqF9JggHBYP60FsJZPqdyinQLte HNSGezeiw610qZRanP+AnURa81BkmmCuPENNPufYV0kqKxAfGDxHaUkd4/MtQvrRhcTf up2AJg4IlEja4lF5f5uNVHsSRK92P/K/h8K4RcRgCoqD85dH6bg8z122MmOGaMbh8Cb1 ao4jxZPDkjGBvH5EP5u9upG666zjNeKKStV1BvXWYPOkeISXnuenKipD8cDUdJg0bjFn qBixz2dLG/xMzGfVbMLaka7zfHKXcc1HKENz7xRD8AS918JS0oa2gezd8oyzkN2mWHLZ ZrAw== X-Gm-Message-State: AOAM533WMiKY3e1B2uYIQ7YtXZG3O2Ai0llmlE1fZsFWsCoWuBZYWbHP /vVO37lp8Iax1xE+0jr08Rs= X-Received: by 2002:a17:907:2d24:: with SMTP id gs36mr5152295ejc.344.1616168558515; Fri, 19 Mar 2021 08:42:38 -0700 (PDT) Received: from ubuntu-laptop (ip5f5bec5d.dynamic.kabel-deutschland.de. [95.91.236.93]) by smtp.googlemail.com with ESMTPSA id r17sm4203287edt.70.2021.03.19.08.42.37 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 19 Mar 2021 08:42:38 -0700 (PDT) Message-ID: <79ec60974875d4ac17589ea4575e36ec1204f881.camel@gmail.com> Subject: Re: [PATCH v1 2/2] mmc: cavium: Remove redundant if-statement checkup From: Bean Huo To: Ulf Hansson Cc: rric@kernel.org, Linus Walleij , linux-mmc , Linux Kernel Mailing List , "Bean Huo (beanhuo)" , "# 4.0+" Date: Fri, 19 Mar 2021 16:42:37 +0100 In-Reply-To: References: <20210319121357.255176-1-huobean@gmail.com> <20210319121357.255176-3-huobean@gmail.com> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.36.4-0ubuntu1 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 2021-03-19 at 15:09 +0100, Ulf Hansson wrote: > On Fri, 19 Mar 2021 at 13:14, Bean Huo wrote: > > > From: Bean Huo > > Currently, we have two ways to issue multiple-block read/write the > > command to the eMMC. One is by normal IO request path fs->block- > > >mmc. > > Another one is that we can issue multiple-block read/write through > > MMC ioctl interface. For the first path, mrq->stop, and mrq->stop- > > >opcode > > will be initialized in mmc_blk_data_prep(). However, for the second > > IO > > path, mrq->stop is not initialized since it is a pre-defined > > multiple > > blocks read/write. > > > As a matter of fact this way is also supported for the regular block > > I/O path. To make the mmc block driver to use it, mmc host drivers > > need to announce that it's supported by setting MMC_CAP_CMD23. > > > > It looks like that is what your patch should be targeted towards, can > > you have a look at this instead? > > Hi Ulf, Thanks for your comments. I will look at that as your suggestion. The patch [1/2] is accepted, so I will just update this patch to the next version. Kind regards, Bean > > Kind regards > > Uffe