From: Mike Rapoport <rppt@kernel.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Bagas Sanjaya <bagasdotme@gmail.com>,
David Hildenbrand <david@redhat.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Lorenzo Stoakes <lstoakes@gmail.com>,
"Matthew Wilcox (Oracle)" <willy@infradead.org>,
Mel Gorman <mgorman@suse.de>, Michal Hocko <mhocko@kernel.org>,
Vlastimil Babka <vbabka@suse.cz>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH v4 0/1] docs/mm: start filling out new structure
Date: Sun, 22 Jan 2023 20:41:52 +0200 [thread overview]
Message-ID: <Y82DcBuilEaE03wx@kernel.org> (raw)
In-Reply-To: <87tu0ilb2t.fsf@meer.lwn.net>
On Sun, Jan 22, 2023 at 10:43:06AM -0700, Jonathan Corbet wrote:
> Mike Rapoport <rppt@kernel.org> writes:
>
> > Gentle ping.
>
> Is that your way of saying that you think it's perhaps ready to be
> applied? I've been watching the discussion but wasn't sure if things
> have settled or not.
Well, everybody who participated in the discussion acked the patch, so
yeah, I think it's ready ;-)
> Thanks,
>
> jon
prev parent reply other threads:[~2023-01-22 18:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-15 18:42 Mike Rapoport
2023-01-15 18:42 ` [PATCH v4 1/1] docs/mm: Physical Memory: add structure, introduction and nodes description Mike Rapoport
2023-01-24 11:00 ` Vlastimil Babka
2023-01-24 11:16 ` Mike Rapoport
2023-01-24 13:40 ` Vlastimil Babka
2023-01-25 18:56 ` Mike Rapoport
2023-01-22 5:30 ` [PATCH v4 0/1] docs/mm: start filling out new structure Mike Rapoport
2023-01-22 17:43 ` Jonathan Corbet
2023-01-22 18:41 ` Mike Rapoport [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=Y82DcBuilEaE03wx@kernel.org \
--to=rppt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=david@redhat.com \
--cc=hannes@cmpxchg.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lstoakes@gmail.com \
--cc=mgorman@suse.de \
--cc=mhocko@kernel.org \
--cc=vbabka@suse.cz \
--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