From: Lorenzo Stoakes <lstoakes@gmail.com>
To: David Hildenbrand <david@redhat.com>
Cc: linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
Shuah Khan <shuah@kernel.org>,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
Vlastimil Babka <vbabka@suse.cz>,
Jakub Matena <matenajakub@gmail.com>,
Matthew Wilcox <willy@infradead.org>,
Mel Gorman <mgorman@techsingularity.net>,
Michal Hocko <mhocko@kernel.org>
Subject: Re: [PATCH v3] selftest/vm: add mremap expand merge offset test
Date: Mon, 2 Jan 2023 16:22:58 +0000 [thread overview]
Message-ID: <Y7ME4v00R7ULlxV4@lucifer> (raw)
In-Reply-To: <b6b25373-ba6b-6610-1030-7f795f01987c@redhat.com>
On Mon, Jan 02, 2023 at 05:20:49PM +0100, David Hildenbrand wrote:
> Maintainers usually apply tags that are sent to the latest version, when
> picking up the patch. Maintainers usually refrain from going through
> multiple earlier patch versions to pick up tags -- especially, because some
> changes might require a submitter from dropping tags (e.g., bigger changes)
> and the tags might no longer be valid.
>
> So better always include tags when resending, so they don't get lost.
>
Ack, apologies again, and that's completely reasonable. Would you mind adding to
the v4 thread just so we have it? Going forward I'll make sure to propagate the
tags!
Thanks for the review!
prev parent reply other threads:[~2023-01-02 16:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-02 16:01 Lorenzo Stoakes
2023-01-02 16:03 ` David Hildenbrand
2023-01-02 16:09 ` Lorenzo Stoakes
2023-01-02 16:10 ` David Hildenbrand
2023-01-02 16:16 ` Lorenzo Stoakes
2023-01-02 16:20 ` David Hildenbrand
2023-01-02 16:22 ` Lorenzo Stoakes [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=Y7ME4v00R7ULlxV4@lucifer \
--to=lstoakes@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=matenajakub@gmail.com \
--cc=mgorman@techsingularity.net \
--cc=mhocko@kernel.org \
--cc=shuah@kernel.org \
--cc=vbabka@suse.cz \
--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