Received: by 10.223.185.116 with SMTP id b49csp2154932wrg; Mon, 12 Feb 2018 05:21:31 -0800 (PST) X-Google-Smtp-Source: AH8x2262HeuHtV+h3XDe/djjSJqHccO1W9v2E30wBKSqQEcgZOs3DOLnAJzyGPx167/9V+jB8c3z X-Received: by 10.98.106.10 with SMTP id f10mr2117030pfc.222.1518441691051; Mon, 12 Feb 2018 05:21:31 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1518441691; cv=none; d=google.com; s=arc-20160816; b=Hep2jpzgntbOFVagzR0E6loFpsS9YbDiql2GzbNWxgQhZ2isT80Gk7y0B7wBMjv3eG 7RrFFVdjf9vJK+umnE20hjnQTD5YfLMgBZXbLxRHqbOEUuAxFDO53b/6jYTS2fDH37NB jdPzsSGSg5sIrqCGacc6FXvKtNdPdoPdp860Wt1sYnuz7ocQ4mpV3yNuGd1cI5Sx6dlA BZWmfUIg3yA4+l6NeszxXmWJd+0Nq6KIf9ZLXGHV59nedkScKCaiR4gIek7w0tGGf4/c XIaLJOpkdcT+dexuL7rOpQbgdXNygjh6w7DvgV9pBDnjbmrci76mOLQVCmWXeuyD2StT qVfQ== 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:arc-authentication-results; bh=wYJUd4yW9v2OfT5uIbAhBukfylchivPFheewcPEP4Fo=; b=LuKZBKfl2UXRjr4VODK69kS7bJAhcVgAEz4ZSaDzID69jKZPFIa0iga+34y5UE+urH kGwf2CZeUCDIQtE/pOyZRrbXWCt/mHjdoXM3kF1oItoecc7IHI8ri1r2+sV5yglES2Qd tbYGBcOXWc9noCViMOkGEqfG+74TrO1tnNJiUpgXqF4KFenSFl+hN5eHlrN5MjLlVO+S hIbT4M45JTp8K8ZyxxhOytaVQZE9yrWF40/BeB7KJVj2yIrmEFqsQoq/ajgWc1WSdw8o SmabFb1XYANrZrQ+AlUTwGsyygQm1RmG2uohN+t7chS6yM0ZZtR6+iyZaQIqKeSJ8RVR JEAg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id f5si5144311pgo.320.2018.02.12.05.21.16; Mon, 12 Feb 2018 05:21:31 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934001AbeBLL0u (ORCPT + 99 others); Mon, 12 Feb 2018 06:26:50 -0500 Received: from lhrrgout.huawei.com ([194.213.3.17]:26134 "EHLO huawei.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S933898AbeBLL0t (ORCPT ); Mon, 12 Feb 2018 06:26:49 -0500 Received: from LHREML712-CAH.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 8BF072788D26E; Mon, 12 Feb 2018 11:26:45 +0000 (GMT) Received: from [10.122.225.51] (10.122.225.51) by smtpsuk.huawei.com (10.201.108.35) with Microsoft SMTP Server (TLS) id 14.3.361.1; Mon, 12 Feb 2018 11:26:43 +0000 Subject: Re: [PATCH 4/6] Protectable Memory To: Mike Rapoport CC: , , , , , , , , , , , , References: <20180211031920.3424-1-igor.stoppa@huawei.com> <20180211031920.3424-5-igor.stoppa@huawei.com> <20180211123743.GC13931@rapoport-lnx> From: Igor Stoppa Message-ID: Date: Mon, 12 Feb 2018 13:26:28 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <20180211123743.GC13931@rapoport-lnx> Content-Type: text/plain; charset="utf-8" Content-Language: en-US Content-Transfer-Encoding: 7bit X-Originating-IP: [10.122.225.51] X-CFilter-Loop: Reflected Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 11/02/18 14:37, Mike Rapoport wrote: > On Sun, Feb 11, 2018 at 05:19:18AM +0200, Igor Stoppa wrote: >> + * Return: 0 if the object does not belong to pmalloc, 1 if it belongs to >> + * pmalloc, -1 if it partially overlaps pmalloc meory, but incorectly. > > typo: ^ memory thanks :-( [...] >> +/** >> + * When the sysfs is ready to receive registrations, connect all the >> + * pools previously created. Also enable further pools to be connected >> + * right away. >> + */ > > This does not seem as kernel-doc comment. Please either remove the second * > from the opening comment mark or reformat the comment. For this too, I thought I had caught them all, but I was wrong ... I didn't find any mention of automated checking for comments. Is there such tool? -- thanks, igor