From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org, akpm@linux-foundation.org,
fmdefrancesco@gmail.com, akpm@linux-foundation.org
Subject: [folded-merged] mm-highmem-add-notes-about-conversions-from-kmap_atomic-v3.patch removed from -mm tree
Date: Thu, 02 Feb 2023 21:37:07 -0800 [thread overview]
Message-ID: <20230203053708.8CEB1C433D2@smtp.kernel.org> (raw)
The quilt patch titled
Subject: mm-highmem-add-notes-about-conversions-from-kmap_atomic-v3
has been removed from the -mm tree. Its filename was
mm-highmem-add-notes-about-conversions-from-kmap_atomic-v3.patch
This patch was dropped because it was folded into mm-highmem-add-notes-about-conversions-from-kmap_atomic.patch
------------------------------------------------------
From: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
Subject: mm-highmem-add-notes-about-conversions-from-kmap_atomic-v3
Date: Thu, 19 Jan 2023 13:39:45 +0100
merge two sentences into one, per Bagas
Link: https://lkml.kernel.org/r/20230119123945.10471-1-fmdefrancesco@gmail.com
Signed-off-by: Fabio M. De Francesco <fmdefrancesco@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
--- a/Documentation/mm/highmem.rst~mm-highmem-add-notes-about-conversions-from-kmap_atomic-v3
+++ a/Documentation/mm/highmem.rst
@@ -57,8 +57,8 @@ list shows them in order of preference o
It can be invoked from any context (including interrupts) but the mappings
can only be used in the context which acquired them.
- This function should always be used. kmap_atomic() and kmap() have been
- deprecated.
+ This function should always be used, whereas kmap_atomic() and kmap() have
+ been deprecated.
These mappings are thread-local and CPU-local, meaning that the mapping
can only be accessed from within this thread and the thread is bound to the
_
Patches currently in -mm which might be from fmdefrancesco@gmail.com are
mm-highmem-add-notes-about-conversions-from-kmap_atomic.patch
reply other threads:[~2023-02-03 5:37 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=20230203053708.8CEB1C433D2@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=fmdefrancesco@gmail.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.