From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>,
Sandeep Patil <sspatil@android.com>,
vbabka@suse.cz, adobriyan@gmail.com, akpm@linux-foundation.org
Cc: linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
stable@vger.kernel.org
Subject: Re: [PATCH] mm: proc: smaps_rollup: Fix pss_locked calculation
Date: Wed, 23 Jan 2019 22:57:45 +0000 [thread overview]
Message-ID: <20190123225746.5B3DF218A4@mail.kernel.org> (raw)
In-Reply-To: <20190121011049.160505-1-sspatil@android.com>
Hi,
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag,
fixing commit: 493b0e9d945f mm: add /proc/pid/smaps_rollup.
The bot has tested the following trees: v4.20.3, v4.19.16, v4.14.94.
v4.20.3: Build OK!
v4.19.16: Build OK!
v4.14.94: Failed to apply! Possible dependencies:
8526d84f8171 ("fs/proc/task_mmu.c: do not show VmExe bigger than total executable virtual memory")
8e68d689afe3 ("mm: /proc/pid/smaps: factor out mem stats gathering")
af5b0f6a09e4 ("mm: consolidate page table accounting")
b4e98d9ac775 ("mm: account pud page tables")
c4812909f5d5 ("mm: introduce wrappers to access mm->nr_ptes")
d1be35cb6f96 ("proc: add seq_put_decimal_ull_width to speed up /proc/pid/smaps")
How should we proceed with this patch?
--
Thanks,
Sasha
WARNING: multiple messages have this Message-ID (diff)
From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: Sandeep Patil <sspatil@android.com>
To: vbabka@suse.cz, adobriyan@gmail.com, akpm@linux-foundation.org,
Cc: linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
Cc: stable@vger.kernel.org
Subject: Re: [PATCH] mm: proc: smaps_rollup: Fix pss_locked calculation
Date: Wed, 23 Jan 2019 22:57:45 +0000 [thread overview]
Message-ID: <20190123225746.5B3DF218A4@mail.kernel.org> (raw)
Message-ID: <20190123225745.TSlgRxoNfexwifvzDqRN5hSLYhBIoP38IZbqscYyifI@z> (raw)
In-Reply-To: <20190121011049.160505-1-sspatil@android.com>
Hi,
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag,
fixing commit: 493b0e9d945f mm: add /proc/pid/smaps_rollup.
The bot has tested the following trees: v4.20.3, v4.19.16, v4.14.94.
v4.20.3: Build OK!
v4.19.16: Build OK!
v4.14.94: Failed to apply! Possible dependencies:
8526d84f8171 ("fs/proc/task_mmu.c: do not show VmExe bigger than total executable virtual memory")
8e68d689afe3 ("mm: /proc/pid/smaps: factor out mem stats gathering")
af5b0f6a09e4 ("mm: consolidate page table accounting")
b4e98d9ac775 ("mm: account pud page tables")
c4812909f5d5 ("mm: introduce wrappers to access mm->nr_ptes")
d1be35cb6f96 ("proc: add seq_put_decimal_ull_width to speed up /proc/pid/smaps")
How should we proceed with this patch?
--
Thanks,
Sasha
next prev parent reply other threads:[~2019-01-23 22:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-21 1:10 [PATCH] mm: proc: smaps_rollup: Fix pss_locked calculation Sandeep Patil
2019-01-23 22:57 ` Sasha Levin [this message]
2019-01-23 22:57 ` Sasha Levin
2019-01-24 21:39 ` Sandeep Patil
2019-01-25 6:21 ` Greg KH
2019-01-29 0:15 ` Andrew Morton
2019-01-29 15:52 ` Vlastimil Babka
2019-02-03 6:21 ` Sandeep Patil
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=20190123225746.5B3DF218A4@mail.kernel.org \
--to=sashal@kernel.org \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=sspatil@android.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;
as well as URLs for NNTP newsgroup(s).