Received: by 2002:a25:868d:0:0:0:0:0 with SMTP id z13csp33231ybk; Fri, 8 May 2020 17:40:58 -0700 (PDT) X-Google-Smtp-Source: APiQypJvs5fV7zMx1zOHy3pTPosFwTE9Ttz0MDtG6XQUSwuAc+NG47rV6BosjJKvmY2xvMTaOFiQ X-Received: by 2002:a05:6402:1766:: with SMTP id da6mr4431362edb.119.1588984858809; Fri, 08 May 2020 17:40:58 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1588984858; cv=none; d=google.com; s=arc-20160816; b=E6ABJnvVzVI4JaI06v1229R1j1FWYvfE2arMWlbAScBcQ1d1C6u3PBeZJBmUDFOerT ALK2E12zE1GKTFj00Dful0w+yrbMraBIBINvzUqmqjiWhEvc+nhNfBTQVV5HD2cTBBKT wX8rtr3Wzjws0WyFIRyTrkQAKU2coxDK5rpNuyZYAS5OgpOpJpIBaVVD6wrCYkGcT//c 3b1WbdT8w/5a7d+/MIU+HDXhQPDGdmRbVMQ31iIIlJo2QCttaOjRY7sKju4hQgF1BC+B y76WsxEcAey0FdwyRJmgroE5I/7ejq1+OYNpFW6UDhanUnEWKj8wptTROIUvhYj4is0M GW8w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=pEiY9+MtqtWtDmo45VL0h6EuUezL1BTijAiR0RuE464=; b=UD5RoJfli6WpaYVJw7azXlOrsQj9Ik4sWkXSL3hs9/OmXINfVPURTNOTLttLLJHcw6 91Y7rqhgnJVJR/yYQKgFsZ9bpn8mFWClqee2vVY6uNjV53iZljOV3qMJ5od3tb4WMpg1 NOutDZKovq/QsJK3OwQmAyRiI+s9mv3w7r/BMkUz4/g1QVoOtD9nl6PhEmdtm197baJ/ YhT8uMIGKaTbGShytYasJLzCm9m+cMNn2IfpTjMcarNziLUagPtVOKD7VDUNJx5gJ4NN ELuZcme4u2HkyXaoQNOE8WAw2Cxi74eHxJJ8nTsyxc3vtcDXJQ8UJO9UNFfpsAFBym1Z iPLQ== 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 f16si1902934edr.583.2020.05.08.17.40.36; Fri, 08 May 2020 17:40:58 -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 S1728492AbgEIAip (ORCPT + 99 others); Fri, 8 May 2020 20:38:45 -0400 Received: from szxga04-in.huawei.com ([45.249.212.190]:4358 "EHLO huawei.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1727984AbgEIAio (ORCPT ); Fri, 8 May 2020 20:38:44 -0400 Received: from DGGEMS411-HUB.china.huawei.com (unknown [172.30.72.58]) by Forcepoint Email with ESMTP id E7528D12D30C88EFBFCE; Sat, 9 May 2020 08:38:41 +0800 (CST) Received: from [127.0.0.1] (10.166.212.180) by DGGEMS411-HUB.china.huawei.com (10.3.19.211) with Microsoft SMTP Server id 14.3.487.0; Sat, 9 May 2020 08:38:40 +0800 Subject: Re: [PATCH -next] livepatch: Make klp_apply_object_relocs static To: Josh Poimboeuf CC: , , , , , References: <1588939594-58255-1-git-send-email-zou_wei@huawei.com> <20200508155335.jyfo4rhdvbyoq5kl@treble> <20200508155511.462d6pnbebcryi2j@treble> From: Samuel Zou Message-ID: Date: Sat, 9 May 2020 08:38:39 +0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0 MIME-Version: 1.0 In-Reply-To: <20200508155511.462d6pnbebcryi2j@treble> Content-Type: text/plain; charset="utf-8"; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Originating-IP: [10.166.212.180] X-CFilter-Loop: Reflected Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Josh, Thanks for your review and reply. Yes, I just copied and pasted the warning message, so I brought a question mark. I will modify the description and add the fixes tag which introduced the issue, then will send the v2 soon. On 2020/5/8 23:55, Josh Poimboeuf wrote: > On Fri, May 08, 2020 at 10:53:41AM -0500, Josh Poimboeuf wrote: >> On Fri, May 08, 2020 at 08:06:34PM +0800, Samuel Zou wrote: >>> Fix the following sparse warning: >>> >>> kernel/livepatch/core.c:748:5: warning: symbol 'klp_apply_object_relocs' >>> was not declared. Should it be static? >> >> Yes, it should :-) >> >> So instead of the question, the patch description should probably state >> that it should be static because its only caller is in the file. > > ... and it probably should also have a Fixes tag which references the > commit which introduced this issue. > >> With that change: >> >> Acked-by: Josh Poimboeuf >