From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org, hch@infradead.org,
ira.weiny@intel.com, akpm@linux-foundation.org
Subject: [folded-merged] highmem-document-kunmap_local-v2.patch removed from -mm tree
Date: Tue, 22 Mar 2022 12:16:47 -0700 [thread overview]
Message-ID: <20220322191648.7FBE5C340EC@smtp.kernel.org> (raw)
The patch titled
Subject: highmem-document-kunmap_local-v2
has been removed from the -mm tree. Its filename was
highmem-document-kunmap_local-v2.patch
This patch was dropped because it was folded into highmem-document-kunmap_local.patch
------------------------------------------------------
From: Ira Weiny <ira.weiny@intel.com>
Subject: highmem-document-kunmap_local-v2
updates per Christoph
Link: https://lkml.kernel.org/r/20220124182138.816693-1-ira.weiny@intel.com
Signed-off-by: Ira Weiny <ira.weiny@intel.com>
Cc: Christoph Hellwig <hch@infradead.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
include/linux/highmem-internal.h | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
--- a/include/linux/highmem-internal.h~highmem-document-kunmap_local-v2
+++ a/include/linux/highmem-internal.h
@@ -250,9 +250,8 @@ do { \
* kunmap_local - Unmap a page mapped via kmap_local_page().
* @__addr: An address within the page mapped
*
- * __addr is often an address returned from kmap_local_page(). However,
- * this address can be any address within the mapped page. It does not need to
- * be the exact address returned from kmap_local_page()
+ * @__addr can be any address within the mapped page. Commonly it is the
+ * address return from kmap_local_page(), but it can also include offsets.
*
* Unmapping should be done in the reverse order of the mapping. See
* kmap_local_page() for details.
_
Patches currently in -mm which might be from ira.weiny@intel.com are
highmem-document-kunmap_local.patch
reply other threads:[~2022-03-22 19:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220322191648.7FBE5C340EC@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=hch@infradead.org \
--cc=ira.weiny@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.