Received: by 2002:a05:6a10:9848:0:0:0:0 with SMTP id x8csp383383pxf; Wed, 31 Mar 2021 06:00:48 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyQUcaTd2/GJcSYd13qJuOadjipLX8hH4xfvkF5LQ9Wxna+Z3veFkuYo1Tzin+M1oDzz6mh X-Received: by 2002:aa7:cd54:: with SMTP id v20mr3639948edw.80.1617195648013; Wed, 31 Mar 2021 06:00:48 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1617195648; cv=none; d=google.com; s=arc-20160816; b=k82Yz+dMsG+CuVzBkCeyYj7Z3RLiG2i5jz5i+RL9dBo2TejK2VYXqzhGHks+DhaziE 9Hl8sH2bR8HYrWeIXBKz+sWTmMzDuSJ1NKgnnPthUDnspCHHRWPZ0AkKqFTioNtqyoJF Qvl8rHHbUHw436lRQWyDEf/XzCFrqPTVi8wX1/dN4O/FNTtKwsgoTmzwH1LGU56rbQ78 UOJJGCXHDm3Si2h+7HFo1RJ6VupYTBVagWuvL2xRg7Q7O+zGWbNmQedOMvDafUjykGMX 45Xsns3v/5P2sax+LPSJnhiS09ecPONCpxbh1Xa/1W4/iQLjRFXKx55xUCzvMOOm+NiV iVbg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject; bh=zqX7dtt/7mwojCA7JUtflx7FPGC6S5GhPcDMIA+brAE=; b=gkhCM/bwqTp1sN37v+qZ7pjTGuoAV/A7DUb2nEREE7DaHvQA5kzpTw/lV/B8qGg5b5 XEQV5ohHf3Xyp6b9JJPXCxBSndB1GUD9in9A409ex6/kEs6yl/uWqsjcCsVg0WBwHQXQ FEMEraqIP4abpeS+tdgvLvOQPJp9FvTF9UT+588XL3vggN/G3ZeUyicYsXHVp6v+TjQw Vtsfc3N9QJySRtD6YGOkWYHS4gYjb5iKj497/4dYOQwItAwheBvVxq2LO4G3eETSsxI2 M2oTcAmCjCwy7ztzCT4Q7jgjQI3yTIOrWq4h5ijz4AaFRsIjJq5StzVg77QL/+2nb5Cf m6sQ== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=huawei.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id do3si1609456ejc.486.2021.03.31.06.00.24; Wed, 31 Mar 2021 06:00:48 -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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=huawei.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235548AbhCaM7E (ORCPT + 99 others); Wed, 31 Mar 2021 08:59:04 -0400 Received: from szxga07-in.huawei.com ([45.249.212.35]:15837 "EHLO szxga07-in.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235521AbhCaM6r (ORCPT ); Wed, 31 Mar 2021 08:58:47 -0400 Received: from DGGEMS401-HUB.china.huawei.com (unknown [172.30.72.59]) by szxga07-in.huawei.com (SkyGuard) with ESMTP id 4F9RCX0nqrz9tR4; Wed, 31 Mar 2021 20:56:40 +0800 (CST) Received: from [10.174.179.96] (10.174.179.96) by DGGEMS401-HUB.china.huawei.com (10.3.19.201) with Microsoft SMTP Server id 14.3.498.0; Wed, 31 Mar 2021 20:58:43 +0800 Subject: Re: [PATCH -next] powerpc/eeh: Remove unused inline function eeh_dev_phb_init_dynamic() To: Daniel Axtens , , , , , CC: , References: <20210324140714.19612-1-yuehaibing@huawei.com> <874kgy8ptt.fsf@linkitivity.dja.id.au> From: YueHaibing Message-ID: <238925b8-c2be-8282-1ce6-e1d92b7b527e@huawei.com> Date: Wed, 31 Mar 2021 20:58:42 +0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.5.0 MIME-Version: 1.0 In-Reply-To: <874kgy8ptt.fsf@linkitivity.dja.id.au> Content-Type: text/plain; charset="utf-8" Content-Language: en-US Content-Transfer-Encoding: 7bit X-Originating-IP: [10.174.179.96] X-CFilter-Loop: Reflected Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2021/3/26 13:08, Daniel Axtens wrote: > Hi, > >> commit 475028efc708 ("powerpc/eeh: Remove eeh_dev_phb_init_dynamic()") >> left behind this, so can remove it. > > I had a look: the inline that you are removing here is for the > !CONFIG_EEH case, which explains why it was missed the first time. > > This looks like a good change. Out of interest, what tool are you using > to find these unused inlines? If there are many more, it might make > sense to combine future patches removing them into a single patch, but > I'm not sure. Just use some grep skill, will do that if any. > > checkpatch likes this patch, so that's also good :) > > Reviewed-by: Daniel Axtens > > Kind regards, > Daniel > . >