From: Bagas Sanjaya <bagasdotme@gmail.com>
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
Subject: Re: [PATCH v2] Documentation: highmem: Use literal block for *kmap_local_folio() example
Date: Thu, 16 Jun 2022 08:31:31 +0700 [thread overview]
Message-ID: <62074230-52d9-83b7-df64-c00aea016150@gmail.com> (raw)
In-Reply-To: <YqnyiuaeQz6aSNUL@iweiny-server>
On 6/15/22 21:54, Ira Weiny wrote:
>> Reviewed-by: Ira Weiny <ira.weiny@intel.com>
>
> My bad...
>
>> Tested-by: Ira Weiny <ira.weiny@intel.com>
>>
>>> Cc: "Matthew Wilcox (Oracle)" <willy@infradead.org>
>>> Cc: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
>>> Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
>>> Cc: linux-mm@kvack.org
>>> Cc: linux-kernel@vger.kernel.org
>>> Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
>>> ---
>>> Changes since v1 [1]:
>>> - Point that the code example is for kmap_atomic() (suggested by
>>> Matthew Wilcox)
>
> As Willy pointed out you did not do this. I was mistaken to believe this
> statement.
My bad too...
I forget editing patch subject. I guess the subject and description could
just say "code example in *kmap_local_folio() comment" somewhere.
Willy, what do you think? Any suggestion?
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2022-06-16 1:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-15 10:15 [PATCH v2] Documentation: highmem: Use literal block for *kmap_local_folio() example Bagas Sanjaya
2022-06-15 14:37 ` Matthew Wilcox
2022-06-16 1:38 ` Bagas Sanjaya
2022-06-16 2:21 ` Matthew Wilcox
2022-06-15 14:52 ` Ira Weiny
2022-06-15 14:54 ` Ira Weiny
2022-06-16 1:31 ` Bagas Sanjaya [this message]
2022-06-16 1:33 ` Bagas Sanjaya
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=62074230-52d9-83b7-df64-c00aea016150@gmail.com \
--to=bagasdotme@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bigeasy@linutronix.de \
--cc=fmdefrancesco@gmail.com \
--cc=ira.weiny@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=willy@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).