All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org, senozhatsky@chromium.org,
	ngupta@vflare.org, minchan@kernel.org, avromanov@sberdevices.ru,
	akpm@linux-foundation.org, akpm@linux-foundation.org
Subject: + zsmalloc-zs_object_copy-add-clarifying-comment-fix.patch added to mm-unstable branch
Date: Thu, 11 Aug 2022 14:21:58 -0700	[thread overview]
Message-ID: <20220811212158.B732BC433C1@smtp.kernel.org> (raw)


The patch titled
     Subject: zsmalloc-zs_object_copy-add-clarifying-comment-fix
has been added to the -mm mm-unstable branch.  Its filename is
     zsmalloc-zs_object_copy-add-clarifying-comment-fix.patch

This patch will shortly appear at
     https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/zsmalloc-zs_object_copy-add-clarifying-comment-fix.patch

This patch will later appear in the mm-unstable branch at
    git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm

Before you just go and hit "reply", please:
   a) Consider who else should be cc'ed
   b) Prefer to cc a suitable mailing list as well
   c) Ideally: find the original patch on the mailing list and do a
      reply-to-all to that, adding suitable additional cc's

*** Remember to use Documentation/process/submit-checklist.rst when testing your code ***

The -mm tree is included into linux-next via the mm-everything
branch at git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
and is updated there every 2-3 working days

------------------------------------------------------
From: Andrew Morton <akpm@linux-foundation.org>
Subject: zsmalloc-zs_object_copy-add-clarifying-comment-fix
Date: Thu Aug 11 02:20:45 PM PDT 2022

tweak comment layout

Cc: Alexey Romanov <avromanov@sberdevices.ru>
Cc: Minchan Kim <minchan@kernel.org>
Cc: Nitin Gupta <ngupta@vflare.org>
Cc: Sergey Senozhatsky <senozhatsky@chromium.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---

 mm/zsmalloc.c |    9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

--- a/mm/zsmalloc.c~zsmalloc-zs_object_copy-add-clarifying-comment-fix
+++ a/mm/zsmalloc.c
@@ -1555,10 +1555,11 @@ static void zs_object_copy(struct size_c
 		d_off += size;
 		d_size -= size;
 
-		/* Calling kunmap_atomic(d_addr) is necessary. kunmap_atomic() calls
-		 * must occurs in reverse order of calls to kmap_atomic().
-		 * So, to call kunmap_atomic(s_addr) we should first call kunmap_atomic(d_addr).
-		 * For more details see:
+		/*
+		 * Calling kunmap_atomic(d_addr) is necessary. kunmap_atomic()
+		 * calls must occurs in reverse order of calls to kmap_atomic().
+		 * So, to call kunmap_atomic(s_addr) we should first call
+		 * kunmap_atomic(d_addr).  For more details see
 		 * https://lore.kernel.org/linux-mm/5512421D.4000603@samsung.com/
 		 */
 		if (s_off >= PAGE_SIZE) {
_

Patches currently in -mm which might be from akpm@linux-foundation.org are

zsmalloc-zs_object_copy-add-clarifying-comment-fix.patch


                 reply	other threads:[~2022-08-11 21:22 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=20220811212158.B732BC433C1@smtp.kernel.org \
    --to=akpm@linux-foundation.org \
    --cc=avromanov@sberdevices.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=minchan@kernel.org \
    --cc=mm-commits@vger.kernel.org \
    --cc=ngupta@vflare.org \
    --cc=senozhatsky@chromium.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.