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: <4c566329-b2ce-80a5-00da-f3048bdbed3e@gmail.com>
Date:   Wed, 22 Jun 2022 15:36:14 +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 v3] Documentation: highmem: Use literal block for code
 example in highmem.h comment
Content-Language: en-US
To:     Ira Weiny <ira.weiny@intel.com>
Cc:     linux-doc@vger.kernel.org,
        Andrew Morton <akpm@linux-foundation.org>,
        "Matthew Wilcox (Oracle)" <willy@infradead.org>,
        "Fabio M. De Francesco" <fmdefrancesco@gmail.com>,
        Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
        linux-mm@kvack.org, linux-kernel@vger.kernel.org
References: <20220620083649.18172-1-bagasdotme@gmail.com>
 <YrDqJB0J1PT8VlwA@iweiny-desk3>
From:   Bagas Sanjaya <bagasdotme@gmail.com>
In-Reply-To: <YrDqJB0J1PT8VlwA@iweiny-desk3>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: bulk

On 6/21/22 04:44, Ira Weiny wrote:

>> Fix these warnings by indenting the code example with literal block
>> indentation and prefixing comments inside the example with C comment
>> symbol (#).
> 
> "//"?
> 
> Frankly I'd just drop "(#)".
> 
> Perhaps:
> 
> ... indentation and making the comments C comments.
> 

Ah! I had overlooked that. Thanks.

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