All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jerome Glisse <jglisse@redhat.com>
To: John Hubbard <jhubbard@nvidia.com>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>,
	David Nellans <dnellans@nvidia.com>
Subject: Re: [HMM 2/2] hmm: heterogeneous memory management documentation
Date: Fri, 17 Mar 2017 23:54:02 -0400 (EDT)	[thread overview]
Message-ID: <511871248.8852779.1489809242452.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <d1dd967c-69e6-f673-0c88-06bb4e234872@nvidia.com>

> On 03/17/2017 12:27 PM, Jérôme Glisse wrote:
> > This add documentation for HMM (Heterogeneous Memory Management). It
> > presents the motivation behind it, the features necessary for it to
> > be usefull and and gives an overview of how this is implemented.
> 
> For this patch, I will leave it to others to decide how to proceed, given the
> following:
> 
> 1. This hmm.txt has a lot of critical information in it.
> 
> 2. It is, however, more of a first draft than a final draft: lots of errors
> in each sentence, and
> lots of paragraphs that need re-doing, for example. After a quick pass
> through a few other
> Documentation/vm/*.txt documents to gage the quality bar, I am inclined to
> recommend (or do) a
> second draft of this, before submitting it.
> 
> Since I'm the one being harsh here (and Jerome, you already know I'm harsh!
> haha), I can provide a
> second draft. But it won't look much like the current draft, so brace
> yourself before saying yes... :)

Feel free to take a stab at it :)

Cheers,
Jérôme

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

WARNING: multiple messages have this Message-ID (diff)
From: Jerome Glisse <jglisse@redhat.com>
To: John Hubbard <jhubbard@nvidia.com>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>,
	David Nellans <dnellans@nvidia.com>
Subject: Re: [HMM 2/2] hmm: heterogeneous memory management documentation
Date: Fri, 17 Mar 2017 23:54:02 -0400 (EDT)	[thread overview]
Message-ID: <511871248.8852779.1489809242452.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <d1dd967c-69e6-f673-0c88-06bb4e234872@nvidia.com>

> On 03/17/2017 12:27 PM, Jérôme Glisse wrote:
> > This add documentation for HMM (Heterogeneous Memory Management). It
> > presents the motivation behind it, the features necessary for it to
> > be usefull and and gives an overview of how this is implemented.
> 
> For this patch, I will leave it to others to decide how to proceed, given the
> following:
> 
> 1. This hmm.txt has a lot of critical information in it.
> 
> 2. It is, however, more of a first draft than a final draft: lots of errors
> in each sentence, and
> lots of paragraphs that need re-doing, for example. After a quick pass
> through a few other
> Documentation/vm/*.txt documents to gage the quality bar, I am inclined to
> recommend (or do) a
> second draft of this, before submitting it.
> 
> Since I'm the one being harsh here (and Jerome, you already know I'm harsh!
> haha), I can provide a
> second draft. But it won't look much like the current draft, so brace
> yourself before saying yes... :)

Feel free to take a stab at it :)

Cheers,
Jérôme

  reply	other threads:[~2017-03-18  3:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-17 19:27 [HMM 0/2] Build fix and documentation Jérôme Glisse
2017-03-17 19:27 ` Jérôme Glisse
2017-03-17 19:27 ` [HMM 1/2] mm/hmm: Fix build on 32 bit systems Jérôme Glisse
2017-03-17 19:27   ` Jérôme Glisse
2017-03-17 19:27 ` [HMM 2/2] hmm: heterogeneous memory management documentation Jérôme Glisse
2017-03-17 19:27   ` Jérôme Glisse
2017-03-18  1:32   ` John Hubbard
2017-03-18  1:32     ` John Hubbard
2017-03-18  3:54     ` Jerome Glisse [this message]
2017-03-18  3:54       ` Jerome Glisse

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=511871248.8852779.1489809242452.JavaMail.zimbra@redhat.com \
    --to=jglisse@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=dnellans@nvidia.com \
    --cc=jhubbard@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=n-horiguchi@ah.jp.nec.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.