From: Andrew Morton <akpm@linux-foundation.org>
To: howaboutsynergy@protonmail.com
Cc: Mel Gorman <mgorman@techsingularity.net>,
Vlastimil Babka <vbabka@suse.cz>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm: compaction: Avoid 100% CPU usage during compaction when a task is killed
Date: Thu, 18 Jul 2019 14:22:03 -0700 [thread overview]
Message-ID: <20190718142203.22f4672a520a5394afd54fd7@linux-foundation.org> (raw)
In-Reply-To: <Wnnv8a76Tvw9MytP99VFfepO4X71QaFWTMyYNrCv1KvQrfDitFfdgbYvH8ibLZ9b1oe_dpPfDdQ1I2wwayzXkRJiYf1fnFOx6sC6udVFveE=@protonmail.com>
On Thu, 18 Jul 2019 11:48:10 +0000 howaboutsynergy@protonmail.com wrote:
> > "howaboutsynergy" reported via kernel buzilla number 204165 that
> <SNIP>
>
> > I haven't included a Reported-and-tested-by as the reporters real name
> > is unknown but this was caught and repaired due to their testing and
> > tracing. If they want a tag added then hopefully they'll say so before
> > this gets merged.
> >
> nope, don't want :)
I added them:
Reported-by: <howaboutsynergy@protonmail.com>
Tested-by: <howaboutsynergy@protonmail.com>
Having a contact email address is potentially useful. I'd be more
concerned about anonymity if it involved an actual code modification.
And thanks for your persistence and assistance.
next prev parent reply other threads:[~2019-07-18 21:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-18 8:57 [PATCH] mm: compaction: Avoid 100% CPU usage during compaction when a task is killed Mel Gorman
2019-07-18 11:48 ` howaboutsynergy
2019-07-18 21:22 ` Andrew Morton [this message]
2019-07-25 13:02 ` Vlastimil Babka
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=20190718142203.22f4672a520a5394afd54fd7@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=howaboutsynergy@protonmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--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;
as well as URLs for NNTP newsgroup(s).