linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Matthew Wilcox <willy@infradead.org>
Cc: linux-mm@kvack.org, linux-doc@vger.kernel.org,
	John Hubbard <jhubbard@nvidia.com>,
	Randy Dunlap <rdunlap@infradead.org>,
	Johannes Weiner <hannes@cmpxchg.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH v2] mm,doc: Add new documentation structure
Date: Mon, 09 May 2022 16:40:50 -0600	[thread overview]
Message-ID: <87zgjqba8d.fsf@meer.lwn.net> (raw)
In-Reply-To: <YnmQ4yQMuv44n8aR@casper.infradead.org>

Matthew Wilcox <willy@infradead.org> writes:

> On Mon, May 09, 2022 at 03:50:22PM -0600, Jonathan Corbet wrote:
>> "Matthew Wilcox (Oracle)" <willy@infradead.org> writes:
>> 
>> > Closely following the outline of Mel Gorman's book "Understanding the
>> > Linux Virtual Memory Manager", add a new outline.  Preserve the current
>> > contents of the mm underneath the new outline so we can transition those
>> > documents to a more sensible place later.
>> >
>> > Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>
>> > Reviewed-by: John Hubbard <jhubbard@nvidia.com>
>> > Acked-by: Randy Dunlap <rdunlap@infradead.org>
>> > Acked-by: Johannes Weiner <hannes@cmpxchg.org>
>> 
>> So this seems like a good start to me.
>> 
>> What's your intended path for merging this?  You didn't copy me so I'm
>> assuming you had some other way in mind.
>
> Uh, good point.  I didn't cc either you or Andrew.  I don't think it
> matters which one of you takes it.  Since you responded first, do you
> want to take it?

Will do.

Thanks,

jon


  reply	other threads:[~2022-05-09 22:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-07 13:49 Matthew Wilcox (Oracle)
2022-05-09 21:50 ` Jonathan Corbet
2022-05-09 22:08   ` Matthew Wilcox
2022-05-09 22:40     ` Jonathan Corbet [this message]
2022-05-11  8:38 ` Mike Rapoport

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=87zgjqba8d.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=akpm@linux-foundation.org \
    --cc=hannes@cmpxchg.org \
    --cc=jhubbard@nvidia.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=rdunlap@infradead.org \
    --cc=willy@infradead.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