From: Suren Baghdasaryan <surenb@google.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: kent.overstreet@linux.dev, david@redhat.com, vbabka@suse.cz,
pasha.tatashin@soleen.com, souravpanda@google.com,
keescook@chromium.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, stable@vger.kernel.org
Subject: Re: [PATCH v3 2/2] alloc_tag: mark pages reserved during CMA activation as not tagged
Date: Tue, 13 Aug 2024 12:37:35 -0700 [thread overview]
Message-ID: <CAJuCfpHX_QYBUrbWPLx3c5_Dh1+VdH_GcYs1v=Q7yriLHyvvqg@mail.gmail.com> (raw)
In-Reply-To: <20240813114029.4bc61d6fe731a533eb88ba64@linux-foundation.org>
On Tue, Aug 13, 2024 at 11:40 AM Andrew Morton
<akpm@linux-foundation.org> wrote:
>
> On Tue, 13 Aug 2024 08:07:57 -0700 Suren Baghdasaryan <surenb@google.com> wrote:
>
> > Fixes: d224eb0287fb ("codetag: debug: mark codetags for reserved pages as empty")
>
> I copied this into [1/2] so everything lands nicely.
Yeah, technically this does not "fix" that patch but since it's needed
for the next patch I think that's fine.
next prev parent reply other threads:[~2024-08-13 19:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-13 15:07 [PATCH v3 1/2] alloc_tag: introduce clear_page_tag_ref() helper function Suren Baghdasaryan
2024-08-13 15:07 ` [PATCH v3 2/2] alloc_tag: mark pages reserved during CMA activation as not tagged Suren Baghdasaryan
2024-08-13 15:09 ` David Hildenbrand
2024-08-13 16:06 ` Suren Baghdasaryan
2024-08-13 18:40 ` Andrew Morton
2024-08-13 19:37 ` Suren Baghdasaryan [this message]
2024-08-13 15:08 ` [PATCH v3 1/2] alloc_tag: introduce clear_page_tag_ref() helper function David Hildenbrand
2024-08-14 18:42 ` Pasha Tatashin
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='CAJuCfpHX_QYBUrbWPLx3c5_Dh1+VdH_GcYs1v=Q7yriLHyvvqg@mail.gmail.com' \
--to=surenb@google.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=keescook@chromium.org \
--cc=kent.overstreet@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pasha.tatashin@soleen.com \
--cc=souravpanda@google.com \
--cc=stable@vger.kernel.org \
--cc=vbabka@suse.cz \
/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