All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,rppt@kernel.org,pratyush@kernel.org,pasha.tatashin@soleen.com,akpm@linux-foundation.org,akpm@linux-foundation.org
Subject: [folded-merged] liveupdate-luo_file-remember-retrieve-status-fix.patch removed from -mm tree
Date: Thu, 05 Feb 2026 15:32:04 -0800	[thread overview]
Message-ID: <20260205233205.41D4CC4CEF7@smtp.kernel.org> (raw)


The quilt patch titled
     Subject: liveupdate-luo_file-remember-retrieve-status-fix
has been removed from the -mm tree.  Its filename was
     liveupdate-luo_file-remember-retrieve-status-fix.patch

This patch was dropped because it was folded into liveupdate-luo_file-remember-retrieve-status.patch

------------------------------------------------------
From: Andrew Morton <akpm@linux-foundation.org>
Subject: liveupdate-luo_file-remember-retrieve-status-fix
Date: Sat Jan 31 11:43:34 AM PST 2026

fix kerneldoc, per Pasha

Cc: Mike Rapoport <rppt@kernel.org>
Cc: Pasha Tatashin <pasha.tatashin@soleen.com>
Cc: "Pratyush Yadav (Google)" <pratyush@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---

 include/linux/liveupdate.h |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

--- a/include/linux/liveupdate.h~liveupdate-luo_file-remember-retrieve-status-fix
+++ a/include/linux/liveupdate.h
@@ -23,7 +23,7 @@ struct file;
 /**
  * struct liveupdate_file_op_args - Arguments for file operation callbacks.
  * @handler:          The file handler being called.
- * @retrieved:        The retrieve status for the 'can_finish / finish'
+ * @retrieve_sts:     The retrieve status for the 'can_finish / finish'
  *                    operation. A value of 0 means the retrieve has not been
  *                    attempted, a positive value means the retrieve was
  *                    successful, and a negative value means the retrieve failed,
_

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

mm-update-shmem__file_-functions-to-use-vma_flags_t-fix.patch
maple_tree-start-using-maple-copy-node-for-destination-checkpatch-fixes.patch
maple_tree-add-cp_is_new_root-helper-fix-fix.patch
liveupdate-luo_file-remember-retrieve-status.patch


                 reply	other threads:[~2026-02-05 23:32 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=20260205233205.41D4CC4CEF7@smtp.kernel.org \
    --to=akpm@linux-foundation.org \
    --cc=mm-commits@vger.kernel.org \
    --cc=pasha.tatashin@soleen.com \
    --cc=pratyush@kernel.org \
    --cc=rppt@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.