From: Prashant Dhamdhere <pdhamdhe@redhat.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation: proc.txt: Adding 'HardwareCorrupted' parameter and description.
Date: Wed, 18 Jul 2018 19:35:24 +0530 [thread overview]
Message-ID: <CAF1GLkk6fUbpdJhfNYhDL7NBf+chvv0H5SR-9_ofTrcHmqgDfQ@mail.gmail.com> (raw)
In-Reply-To: <20180710151656.5ecaae11@lwn.net>
On Wed, Jul 11, 2018 at 2:46 AM, Jonathan Corbet <corbet@lwn.net> wrote:
> On Tue, 10 Jul 2018 20:05:22 +0530
> Prashant Dhamdhere <pdhamdhe@redhat.com> wrote:
>
>> Signed-off-by: Prashant Dhamdhere <pdhamdhe@redhat.com>
>> ---
>> Documentation/filesystems/proc.txt | 3 +++
>> 1 file changed, 3 insertions(+)
>>
>> diff --git a/Documentation/filesystems/proc.txt
>> b/Documentation/filesystems/proc.txt
>> index 520f6a84cf50..b2fa7e7c4300 100644
>> --- a/Documentation/filesystems/proc.txt
>> +++ b/Documentation/filesystems/proc.txt
>> @@ -870,6 +870,7 @@ Committed_AS: 100056 kB
>> VmallocTotal: 112216 kB
>> VmallocUsed: 428 kB
>> VmallocChunk: 111088 kB
>> +HardwareCorrupted: 0 kB
>> AnonHugePages: 49152 kB
>> ShmemHugePages: 0 kB
>> ShmemPmdMapped: 0 kB
>> @@ -915,6 +916,8 @@ MemAvailable: An estimate of how much memory is
>> available for starting new
>
> This patch, too, was corrupted by your mailer. Please resubmit it after
> fixing the issue (and with a changelog, please).
>
> Thanks,
>
> jon
Hi Jon,
I have resubmitted this patch with a changelog, please review and share feedback
so that I will be able to submit other patches.
--
Prashant
>
>> Dirty: Memory which is waiting to get written back to the disk
>> Writeback: Memory which is actively being written back to the disk
>> AnonPages: Non-file backed pages mapped into userspace page tables
>> +HardwareCorrupted: The amount of RAM/memory in KB, the kernel identified as
>> + corrupted.
>> AnonHugePages: Non-file backed huge pages mapped into userspace page tables
>> Mapped: files which have been mmaped, such as libraries
>> Shmem: Total memory used by shared memory (shmem) and tmpfs
>
prev parent reply other threads:[~2018-07-18 14:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAF1GLkkzSzUnGKprz9CroVv=xBoUaym53PUTgi1RDNiEmr6PWw@mail.gmail.com>
2018-07-10 21:16 ` [PATCH] Documentation: proc.txt: Adding 'HardwareCorrupted' parameter and description Jonathan Corbet
2018-07-18 14:05 ` Prashant Dhamdhere [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=CAF1GLkk6fUbpdJhfNYhDL7NBf+chvv0H5SR-9_ofTrcHmqgDfQ@mail.gmail.com \
--to=pdhamdhe@redhat.com \
--cc=corbet@lwn.net \
--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;
as well as URLs for NNTP newsgroup(s).