From patchwork Wed Jan 6 13:30:50 2021 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Patchwork-Submitter: Zheng Yongjun X-Patchwork-Id: 357777 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=-10.6 required=3.0 tests=BAYES_00, CHARSET_FARAWAY_HEADER, HEADER_FROM_DIFFERENT_DOMAINS, INCLUDES_CR_TRAILER, INCLUDES_PATCH, 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 93162C433E0 for ; Wed, 6 Jan 2021 13:31:46 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 5AF2A2311A for ; Wed, 6 Jan 2021 13:31:46 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726638AbhAFNbq (ORCPT ); Wed, 6 Jan 2021 08:31:46 -0500 Received: from szxga01-in.huawei.com ([45.249.212.187]:2544 "EHLO szxga01-in.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726614AbhAFNbp (ORCPT ); Wed, 6 Jan 2021 08:31:45 -0500 Received: from dggeme710-chm.china.huawei.com (unknown [172.30.72.54]) by szxga01-in.huawei.com (SkyGuard) with ESMTP id 4D9qvz2xRgzVxRF; Wed, 6 Jan 2021 21:29:19 +0800 (CST) Received: from dggeme760-chm.china.huawei.com (10.3.19.106) by dggeme710-chm.china.huawei.com (10.1.199.106) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1913.5; Wed, 6 Jan 2021 21:30:50 +0800 Received: from dggeme760-chm.china.huawei.com ([10.6.80.70]) by dggeme760-chm.china.huawei.com ([10.6.80.70]) with mapi id 15.01.1913.007; Wed, 6 Jan 2021 21:30:50 +0800 From: zhengyongjun To: "linus.walleij@linaro.org" , "bgolaszewski@baylibre.com" , "linux-gpio@vger.kernel.org" , "linux-kernel@vger.kernel.org" Subject: =?gb2312?b?tPC4tDogW1BBVENIIC1uZXh0XSBncGlvOiB1c2UgcmVzb3VyY2Vf?= =?gb2312?b?c2l6ZQ==?= Thread-Topic: [PATCH -next] gpio: use resource_size Thread-Index: AQHW5C5q+s91KXd8Pkm1FNgcLEyCcaoal7uQ Date: Wed, 6 Jan 2021 13:30:50 +0000 Message-ID: <54742734960f410095dde662359fe9a5@huawei.com> References: <20210106131900.517-1-zhengyongjun3@huawei.com> In-Reply-To: <20210106131900.517-1-zhengyongjun3@huawei.com> Accept-Language: zh-CN, en-US Content-Language: zh-CN X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.174.178.249] MIME-Version: 1.0 X-CFilter-Loop: Reflected Precedence: bulk List-ID: X-Mailing-List: linux-gpio@vger.kernel.org Sorry, this is my fault, all this five gpio related patch commit msg is wrong, I will send patch v2, please ignore it. -----邮件原件----- 发件人: zhengyongjun 发送时间: 2021年1月6日 21:19 收件人: linus.walleij@linaro.org; bgolaszewski@baylibre.com; linux-gpio@vger.kernel.org; linux-kernel@vger.kernel.org 抄送: zhengyongjun 主题: [PATCH -next] gpio: use resource_size Use resource_size rather than a verbose computation on the end and start fields. Signed-off-by: Zheng Yongjun --- drivers/gpio/gpio-mc33880.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- 2.22.0 diff --git a/drivers/gpio/gpio-mc33880.c b/drivers/gpio/gpio-mc33880.c index f8194f7c6186..704cd4e6171f 100644 --- a/drivers/gpio/gpio-mc33880.c +++ b/drivers/gpio/gpio-mc33880.c @@ -99,7 +99,7 @@ static int mc33880_probe(struct spi_device *spi) mc->spi = spi; - mc->chip.label = DRIVER_NAME, + mc->chip.label = DRIVER_NAME; mc->chip.set = mc33880_set; mc->chip.base = pdata->base; mc->chip.ngpio = PIN_NUMBER;