All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Prashant Dhamdhere <pdhamdhe@redhat.com>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] Documentation: proc.txt: Adding 'HardwareCorrupted' field and description.
Date: Mon, 23 Jul 2018 09:25:39 -0600	[thread overview]
Message-ID: <20180723092539.177749b8@lwn.net> (raw)
In-Reply-To: <20180713172806.17387-1-pdhamdhe@redhat.com>

On Fri, 13 Jul 2018 22:58:06 +0530
Prashant Dhamdhere <pdhamdhe@redhat.com> wrote:

> This patch talks about the 'HardwareCorrupted' field currently missing from
> the 'meminfo' section of 'proc.txt' file. It also includes short description
> of 'HardwareCorrupted' field.

I've gone ahead and applied this.  Please note, though, that the "this
patch..." style of changelogging strongly irritates some developers;
please use an imperative style in the future.  I rewrote the changelog to:

	Documentation: proc.txt: Adding 'HardwareCorrupted' field and
	description. 
    	
	Fill in missing documentation for the HardwareCorrupted field in
	proc.txt.

Thanks,

jon
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: Jonathan Corbet <corbet@lwn.net>
To: Prashant Dhamdhere <pdhamdhe@redhat.com>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] Documentation: proc.txt: Adding 'HardwareCorrupted' field and description.
Date: Mon, 23 Jul 2018 09:25:39 -0600	[thread overview]
Message-ID: <20180723092539.177749b8@lwn.net> (raw)
In-Reply-To: <20180713172806.17387-1-pdhamdhe@redhat.com>

On Fri, 13 Jul 2018 22:58:06 +0530
Prashant Dhamdhere <pdhamdhe@redhat.com> wrote:

> This patch talks about the 'HardwareCorrupted' field currently missing from
> the 'meminfo' section of 'proc.txt' file. It also includes short description
> of 'HardwareCorrupted' field.

I've gone ahead and applied this.  Please note, though, that the "this
patch..." style of changelogging strongly irritates some developers;
please use an imperative style in the future.  I rewrote the changelog to:

	Documentation: proc.txt: Adding 'HardwareCorrupted' field and
	description. 
    	
	Fill in missing documentation for the HardwareCorrupted field in
	proc.txt.

Thanks,

jon

  reply	other threads:[~2018-07-23 15:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-13 17:28 [PATCH v2] Documentation: proc.txt: Adding 'HardwareCorrupted' field and description Prashant Dhamdhere
2018-07-13 17:28 ` Prashant Dhamdhere
2018-07-23 15:25 ` Jonathan Corbet [this message]
2018-07-23 15:25   ` Jonathan Corbet
2018-07-23 16:44   ` Prashant Dhamdhere
2018-07-23 16:44     ` Prashant Dhamdhere

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=20180723092539.177749b8@lwn.net \
    --to=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pdhamdhe@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.