mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: Zi Yan <ziy@nvidia.com>, "Huang, Ying" <ying.huang@intel.com>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: Kefeng Wang <wangkefeng.wang@huawei.com>,
	Baolin Wang <baolin.wang@linux.alibaba.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH 1/2] mm/numa: no task_numa_fault() call if page table is changed
Date: Fri, 9 Aug 2024 15:49:17 +0200	[thread overview]
Message-ID: <17712a89-58bb-4e1a-99bb-9571a6dbfbad@redhat.com> (raw)
In-Reply-To: <6233DD66-9A2E-4885-875D-1E79179146D7@nvidia.com>

> Hi Andrew,
> 
> Can you fold the fixup below to this patch? Thanks.

It might be reasonable to send out a new version. At least I am confused 
now what the latest state is :D

-- 
Cheers,

David / dhildenb


  reply	other threads:[~2024-08-09 13:49 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-07 18:47 Zi Yan
2024-08-07 18:47 ` [PATCH 2/2] mm/migrate: move common code to numa_migrate_check (was numa_migrate_prep) Zi Yan
2024-08-08  4:14   ` Huang, Ying
2024-08-08 14:59     ` Zi Yan
2024-08-08 23:13       ` Zi Yan
2024-08-08  3:19 ` [PATCH 1/2] mm/numa: no task_numa_fault() call if page table is changed Baolin Wang
2024-08-08  8:22   ` David Hildenbrand
2024-08-08  9:25     ` Baolin Wang
2024-08-08 14:13     ` Zi Yan
2024-08-08 14:14       ` David Hildenbrand
2024-08-08 14:21         ` Zi Yan
2024-08-08 14:36           ` Kefeng Wang
2024-08-08 14:57             ` Zi Yan
2024-08-08 15:12               ` Zi Yan
2024-08-09  1:25             ` Huang, Ying
2024-08-09  2:05               ` Zi Yan
2024-08-09  7:52                 ` Huang, Ying
2024-08-09 13:28                   ` Zi Yan
2024-08-09 13:49                     ` David Hildenbrand [this message]
2024-08-09 14:17                       ` Zi Yan

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=17712a89-58bb-4e1a-99bb-9571a6dbfbad@redhat.com \
    --to=david@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=baolin.wang@linux.alibaba.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=stable@vger.kernel.org \
    --cc=wangkefeng.wang@huawei.com \
    --cc=ying.huang@intel.com \
    --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

all inboxes | Powered by JetHome®