Received: by 2002:a05:6a10:22f:0:0:0:0 with SMTP id 15csp3569213pxk; Mon, 28 Sep 2020 23:45:19 -0700 (PDT) X-Google-Smtp-Source: ABdhPJw49XPHmahn+hCkogzmzIZ8XDJBhgoInkNa6aFX7UDtJ0zVVrY3TBscOQFGObUOP3AcvyOI X-Received: by 2002:a17:906:46d5:: with SMTP id k21mr2305878ejs.247.1601361919540; Mon, 28 Sep 2020 23:45:19 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1601361919; cv=none; d=google.com; s=arc-20160816; b=D5lWW9P2KakIjK2eSWgDkxM//0nbv+ejlflnq6V79aBqmvLQViI1ZSO/CAJa8Rw/BX Hlz9kM9vwenkQGEfgyNf+wi/TyfCTpqvtlhxwF9Tb0JwEFx5/tg/7T25Hvy5BE+3e7ke eqDHw4o9lJD/Oe0NKqqrRuxtDGsZc3TYUD40EX8bKXTsC+8Ce3coyKLzUEljgAhBn80F 9fSJuKRzI3MclxWI071SBSdvIdAWr+aKXzLPZ/70KjjZ3qWP7hzCMH6Ngf+8pWIi5MYc tsl4WsRfUq0nA9KU0FOIn/hUBxDIdASnGnSyHdIRHTbKQOyUuThP8/n+ui15fgqEr/Cc zrow== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to :mime-version:user-agent:date:message-id:from:references:cc:to :subject; bh=j92tTZ34ncRIZu697i2WV/BPEYnEojNyFZiJwrOcLcQ=; b=RU399F6mUW/kJ9+8TLJ/xktA78oJ0NRPxJCx7ueCvlVOyJc5nEnOqeRrA5Hr4Q9AyC 9iHrx4LwMXc82tV+lmldtxF+q5p5UhWWVRN1G6FVS0g4Dxy6UU/mPZ4KYGnpY26VmT0l 5XG72JbjN0IgxeYF24ejH6wEZQ+EK8QsLuWd7qXgFrcXyy92BUpV9MEybYQ2vJfwxFp9 B34RVkL+1LbEJoNPb9AcfzFCMtCca3hsyieEX2asmLChg21W4AiAYriivqDWjAYBiduO kWNFlqt3oeyolyEfCCu/VP1TYx19sBQERAHn6Bf89EcmC6ZLTlsTwW3GQaK72hO9lMsc ATkA== ARC-Authentication-Results: i=1; mx.google.com; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id q13si2152658eju.462.2020.09.28.23.44.55; Mon, 28 Sep 2020 23:45:19 -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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1725554AbgI2Gle (ORCPT + 99 others); Tue, 29 Sep 2020 02:41:34 -0400 Received: from szxga06-in.huawei.com ([45.249.212.32]:34462 "EHLO huawei.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1725355AbgI2Gle (ORCPT ); Tue, 29 Sep 2020 02:41:34 -0400 Received: from DGGEMS413-HUB.china.huawei.com (unknown [172.30.72.60]) by Forcepoint Email with ESMTP id 3ECB952FDC07AFB705E2; Tue, 29 Sep 2020 14:41:29 +0800 (CST) Received: from [10.174.179.91] (10.174.179.91) by DGGEMS413-HUB.china.huawei.com (10.3.19.213) with Microsoft SMTP Server id 14.3.487.0; Tue, 29 Sep 2020 14:41:28 +0800 Subject: Re: linux-next: build warning after merge of the tty tree To: Greg KH CC: Stephen Rothwell , Linux Next Mailing List , Linux Kernel Mailing List References: <20200929160111.18719071@canb.auug.org.au> From: miaoqinglang Message-ID: <2e36e978-1276-6b86-3956-4346fc04093f@huawei.com> Date: Tue, 29 Sep 2020 14:41:27 +0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0 MIME-Version: 1.0 In-Reply-To: <20200929160111.18719071@canb.auug.org.au> Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 8bit X-Originating-IP: [10.174.179.91] X-CFilter-Loop: Reflected Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 在 2020/9/29 14:01, Stephen Rothwell 写道: > Hi all, > > After merging the tty tree, today's linux-next build (x86_64 allmodconfig) > produced this warning: > > drivers/tty/serial/mvebu-uart.c: In function 'mvebu_uart_probe': > drivers/tty/serial/mvebu-uart.c:806:6: warning: unused variable 'ret' [-Wunused-variable] > 806 | int ret, id, irq; > | ^~~ > > Introduced by commit > > b63537020db3 ("serial: mvebu-uart: simplify the return expression of mvebu_uart_probe()") > Hi Greg, Sorry about the noise for remaining the unused variable 'ret' in commit b63537020db3. Should I send another patch to clean up this warning or send another v2 patch instead? Thanks.