From: Hui Su <sh_def@163.com>
To: Joe Perches <joe@perches.com>
Cc: akpm@linux-foundation.org, cgroups@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] mm: fix some comments in page_alloc.c and mempolicy.c
Date: Thu, 8 Oct 2020 20:33:33 +0800 [thread overview]
Message-ID: <20201008123333.GA7424@rlk> (raw)
In-Reply-To: <11c9c699aaa873847b4d14dfa5e2435b94c08569.camel@perches.com>
On Thu, Oct 01, 2020 at 09:17:29AM -0700, Joe Perches wrote:
> On Thu, 2020-10-01 at 14:27 +0200, David Hildenbrand wrote:
> > On 25.09.20 18:06, Hui Su wrote:
> > > 1. the cpuset.c has been moved from kernel/cpuset.c to
> > > kernel/cgroup/cpuset.c long time ago, but the comment is stale,
> > > so we update it.
> []
> > > diff --git a/kernel/cgroup/cpuset.c b/kernel/cgroup/cpuset.c
> []
> > > @@ -1,5 +1,5 @@
> > > /*
> > > - * kernel/cpuset.c
> > > + * kernel/cgroup/cpuset.c
>
> It's probably better to remove this altogether instead.
Please ignore this change, thanks.
prev parent reply other threads:[~2020-10-08 12:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-25 16:06 [PATCH] mm: fix some comments in page_alloc.c and mempolicy.c Hui Su
2020-10-01 12:27 ` David Hildenbrand
2020-10-01 16:17 ` Joe Perches
2020-10-08 12:33 ` Hui Su [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=20201008123333.GA7424@rlk \
--to=sh_def@163.com \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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;
as well as URLs for NNTP newsgroup(s).