From: Florian Schmidt <florian.schmidt@nutanix.com>
To: Daniel Jordan <daniel.m.jordan@oracle.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
Andrew Morton <akpm@linux-foundation.org>,
Kirill Tkhai <ktkhai@virtuozzo.com>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Yafang Shao <laoar.shao@gmail.com>
Subject: Re: [PATCH 1/2] trace-vmscan-postprocess: sync with tracepoints updates
Date: Wed, 11 Sep 2019 10:32:08 +0000 [thread overview]
Message-ID: <faf26ea1-ce58-2490-2b26-c31e7e6cc05c@nutanix.com> (raw)
In-Reply-To: <20190904204446.kceqzrg4zmnw3mm6@ca-dmjordan1.us.oracle.com>
Hi Daniel,
On 04/09/2019 21:44, Daniel Jordan wrote:
> On Tue, Sep 03, 2019 at 11:14:12AM +0000, Florian Schmidt wrote:
>> mm_vmscan_{direct_reclaim_begin,wakeup_kswapd,lru_isolate,lru_shrink_active}
>> changed their output to the point where the script throws warnings and
>> errors. Update it to be properly in line with those changes.
>
> Could use the appropriate Fixes tags here.
Good point, I'll add
Fixes: 3481c37ffa1d ("mm/vmscan: drop may_writepage and classzone_idx
from direct reclaim begin template")
Fixes: 3b775998eca7 ("include/trace/events/vmscan.h: drop zone id from
kswapd tracepoints")
in v2.
Thanks for the feedback,
Florian
next prev parent reply other threads:[~2019-09-11 10:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-03 11:14 [PATCH 0/2] trace-vmscan-postprocess: fix parsing and output Florian Schmidt
2019-09-03 11:14 ` [PATCH 1/2] trace-vmscan-postprocess: sync with tracepoints updates Florian Schmidt
2019-09-04 20:44 ` Daniel Jordan
2019-09-11 10:32 ` Florian Schmidt [this message]
2019-09-03 11:14 ` [PATCH 2/2] trace-vmscan-postprocess: fix output table spacing Florian Schmidt
2019-09-04 20:42 ` [PATCH 0/2] trace-vmscan-postprocess: fix parsing and output Daniel Jordan
2019-09-05 4:32 ` Yafang Shao
2019-09-05 15:27 ` Daniel Jordan
2019-09-11 10:30 ` Florian Schmidt
-- strict thread matches above, loose matches on Subject: below --
2019-08-15 17:13 Florian Schmidt
2019-08-15 17:13 ` [PATCH 1/2] trace-vmscan-postprocess: sync with tracepoints updates Florian Schmidt
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=faf26ea1-ce58-2490-2b26-c31e7e6cc05c@nutanix.com \
--to=florian.schmidt@nutanix.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=daniel.m.jordan@oracle.com \
--cc=ktkhai@virtuozzo.com \
--cc=laoar.shao@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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