From: Jakov Novak <jakovnovak30@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>,
Pedro Falcato <pfalcato@suse.de>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-kernel-mentees@lists.linux.dev,
David Hildenbrand <david@kernel.org>,
Lorenzo Stoakes <ljs@kernel.org>, Zi Yan <ziy@nvidia.com>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
"\\ Liam R . Howlett \\ " <liam@infradead.org>,
Nico Pache <npache@redhat.com>,
Ryan Roberts <ryan.roberts@arm.com>, Dev Jain <dev.jain@arm.com>,
Barry Song <baohua@kernel.org>, Lance Yang <lance.yang@linux.dev>,
Usama Arif <usama.arif@linux.dev>,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH v3] mm/khugepaged: replace mutex_lock/mutex_unlock usage with guard macro
Date: Fri, 31 Jul 2026 20:38:08 +0200 [thread overview]
Message-ID: <716E3F29-C75D-4373-A8CE-C2AB2DD7FFEB@gmail.com> (raw)
In-Reply-To: <20260731112541.6098017d442451a8b54345ec@linux-foundation.org>
>> > Reviewed-by: Andrew Morton <akpm@linux-foundation.org>
>>
>> Hmm, did Andrew actually give this R-b tag out? I can't find it on-list.
>
>I don't think so. Hallucination ;)
>
>I do sometimes sneak in an offlist R-b when I'm looking at things but
>I'm pretty inconsistent and lazy about it.
I saw the tag on the mm-new git [1] and I wasn't completely sure if it should be included in the next patch. Sorry about that.
As a general rule, offlist tags should never be copied?
[1] https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/mm-khugepaged-replace-mutex_lock-mutex_unlock-usage-with-guard-macro.patch
prev parent reply other threads:[~2026-07-31 18:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-30 20:47 [PATCH v3] mm/khugepaged: replace mutex_lock/mutex_unlock usage with guard macro Jakov Novak
2026-07-31 9:20 ` David Hildenbrand (Arm)
2026-07-31 10:33 ` Pedro Falcato
2026-07-31 18:25 ` Andrew Morton
2026-07-31 18:38 ` Jakov Novak [this message]
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=716E3F29-C75D-4373-A8CE-C2AB2DD7FFEB@gmail.com \
--to=jakovnovak30@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@kernel.org \
--cc=dev.jain@arm.com \
--cc=lance.yang@linux.dev \
--cc=liam@infradead.org \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=npache@redhat.com \
--cc=pfalcato@suse.de \
--cc=ryan.roberts@arm.com \
--cc=skhan@linuxfoundation.org \
--cc=usama.arif@linux.dev \
--cc=ziy@nvidia.com \
/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