Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <38c5d597-4e24-6933-dbf7-b98dd7458cc7@gmail.com>
Date:   Thu, 16 Jun 2022 08:38:38 +0700
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
 Thunderbird/91.10.0
Subject: Re: [PATCH v2] Documentation: highmem: Use literal block for
 *kmap_local_folio() example
Content-Language: en-US
To:     Matthew Wilcox <willy@infradead.org>
Cc:     linux-doc@vger.kernel.org,
        Andrew Morton <akpm@linux-foundation.org>,
        Ira Weiny <ira.weiny@intel.com>,
        "Fabio M. De Francesco" <fmdefrancesco@gmail.com>,
        Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
        linux-mm@kvack.org, linux-kernel@vger.kernel.org
References: <20220615101509.516520-1-bagasdotme@gmail.com>
 <YqnujWdTA+QSdMHJ@casper.infradead.org>
From:   Bagas Sanjaya <bagasdotme@gmail.com>
In-Reply-To: <YqnujWdTA+QSdMHJ@casper.infradead.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: bulk

On 6/15/22 21:37, Matthew Wilcox wrote:
> On Wed, Jun 15, 2022 at 05:15:10PM +0700, Bagas Sanjaya wrote:
>> These warnings above are due to comments in code example of
>> kmap_atomic() inside kernel-doc comment of *kmap_local_folio() are enclosed
> 
> You still seem to think this has something to do with kmap_local_folio().
> It has nothing to do with kmap_local_folio().  Your next version of this
> patch should not mention kmap_local_folio() anywhere.
> 

But I think mentioning kmap_local_folio() is necessary in the patch
subject, because we know the original warning is pointed to kernel-doc
comment of that funcion.

-- 
An old man doll... just what I always wanted! - Clara