From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Lorenzo Stoakes <ljs@kernel.org>, Suren Baghdasaryan <surenb@google.com>
Cc: akpm@linux-foundation.org, liam@infradead.org, vbabka@kernel.org,
willy@infradead.org, jannh@google.com, paulmck@kernel.org,
pfalcato@suse.de, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 2/2] fs/proc/task_mmu: read proc/pid/smaps_rollup under per-vma lock
Date: Mon, 8 Jun 2026 17:32:36 +0200 [thread overview]
Message-ID: <13f428df-7922-4870-85bc-90039453f247@kernel.org> (raw)
In-Reply-To: <aiZ5qFTc6XDMsqB9@lucifer>
On 6/8/26 10:14, Lorenzo Stoakes wrote:
> On Sun, Jun 07, 2026 at 12:45:23PM -0700, Suren Baghdasaryan wrote:
>> On Sat, Jun 6, 2026 at 1:12 AM Lorenzo Stoakes <ljs@kernel.org> wrote:
>>>
>>> (Will review separately)
>>>
>>> Sorry to be a pain :) and I know it's a petty thing, but even for a 2 patch
>>> series it's easier to handle if sent with patches in-reply-to a cover
>>> letter :>) also makes it easier to track overall updates in cover letter
>>> changelog.
>>
>> Yeah but the first patch is a simple cleanup of about 10 lines, and
>> writing a cover-letter for a single patch seemed excessive. Andrew
>> would have folded it in with this patch anyway, I think.
>
> Makes sense, sorry to nag but I want to be consistent in nagging everybody
> the same :P no matter how well I know them or otherwise ;)
I mean, it always looks like there is something missing in my inbox (e.g.,
people CCing on patches but not on the cover letter). So then I dig for a
missing cover letter and find ... nothing.
--
Cheers,
David
next prev parent reply other threads:[~2026-06-08 15:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-06 1:57 [PATCH 1/2] fs/proc/task_mmu: change lock_vma_range() to return error code Suren Baghdasaryan
2026-06-06 1:57 ` [PATCH 2/2] fs/proc/task_mmu: read proc/pid/smaps_rollup under per-vma lock Suren Baghdasaryan
2026-06-06 2:00 ` Suren Baghdasaryan
2026-06-06 8:12 ` Lorenzo Stoakes
2026-06-07 19:45 ` Suren Baghdasaryan
2026-06-08 8:14 ` Lorenzo Stoakes
2026-06-08 15:32 ` David Hildenbrand (Arm) [this message]
2026-06-08 15:44 ` Suren Baghdasaryan
2026-06-08 15:43 ` Suren Baghdasaryan
2026-06-08 15:52 ` David Hildenbrand (Arm)
2026-06-08 16:20 ` Suren Baghdasaryan
2026-06-09 10:00 ` Lorenzo Stoakes
2026-06-09 17:11 ` Suren Baghdasaryan
2026-06-10 7:05 ` Lorenzo Stoakes
2026-06-10 14:56 ` Suren Baghdasaryan
2026-06-10 15:01 ` David Hildenbrand (Arm)
2026-06-10 16:00 ` Suren Baghdasaryan
2026-06-08 15:38 ` [PATCH 1/2] fs/proc/task_mmu: change lock_vma_range() to return error code David Hildenbrand (Arm)
2026-06-08 15:43 ` Suren Baghdasaryan
2026-06-09 8:27 ` Lorenzo Stoakes
2026-06-09 17:13 ` Suren Baghdasaryan
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=13f428df-7922-4870-85bc-90039453f247@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=jannh@google.com \
--cc=liam@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=paulmck@kernel.org \
--cc=pfalcato@suse.de \
--cc=surenb@google.com \
--cc=vbabka@kernel.org \
--cc=willy@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome