From: Mike Rapoport <rppt@linux.vnet.ibm.com>
To: Jonathan Corbet <corbet@lwn.net>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Randy Dunlap <rdunlap@infradead.org>,
linux-doc <linux-doc@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 00/11] docs/mm: add boot time memory management docs
Date: Wed, 18 Jul 2018 20:00:43 +0300 [thread overview]
Message-ID: <20180718170043.GA23770@rapoport-lnx> (raw)
In-Reply-To: <20180718060249.6b45605d@lwn.net>
(added Andrew)
On Wed, Jul 18, 2018 at 06:02:49AM -0600, Jonathan Corbet wrote:
> On Wed, 18 Jul 2018 14:47:30 +0300
> Mike Rapoport <rppt@linux.vnet.ibm.com> wrote:
>
> > > So this seems like good stuff overall. It digs pretty deeply into the mm
> > > code, though, so I'm a little reluctant to apply it without an ack from an
> > > mm developer. Alternatively, I'm happy to step back if Andrew wants to
> > > pick the set up.
> >
> > Jon, does Michal's reply [1] address your concerns?
> > Or should I respin and ask Andrew to pick it up?
> >
> > [1] https://lore.kernel.org/lkml/20180712080006.GA328@dhcp22.suse.cz/
>
> Michal acked #11 (the docs patch) in particular but not the series as a
> whole. But it's the rest of the series that I was most worried about :)
> I'm happy for the patches to take either path, but I'd really like an
> explicit ack before I apply that many changes directly to the MM code...
Andrew,
Can you please take a look at this series? The thread starts at [1] and if
it'd be more convenient to you I can respin the whole set.
[1] https://lore.kernel.org/lkml/1530370506-21751-1-git-send-email-rppt@linux.vnet.ibm.com/
> Thanks,
>
> jon
>
--
Sincerely yours,
Mike.
--
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: Mike Rapoport <rppt@linux.vnet.ibm.com>
To: Jonathan Corbet <corbet@lwn.net>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Randy Dunlap <rdunlap@infradead.org>,
linux-doc <linux-doc@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 00/11] docs/mm: add boot time memory management docs
Date: Wed, 18 Jul 2018 20:00:43 +0300 [thread overview]
Message-ID: <20180718170043.GA23770@rapoport-lnx> (raw)
In-Reply-To: <20180718060249.6b45605d@lwn.net>
(added Andrew)
On Wed, Jul 18, 2018 at 06:02:49AM -0600, Jonathan Corbet wrote:
> On Wed, 18 Jul 2018 14:47:30 +0300
> Mike Rapoport <rppt@linux.vnet.ibm.com> wrote:
>
> > > So this seems like good stuff overall. It digs pretty deeply into the mm
> > > code, though, so I'm a little reluctant to apply it without an ack from an
> > > mm developer. Alternatively, I'm happy to step back if Andrew wants to
> > > pick the set up.
> >
> > Jon, does Michal's reply [1] address your concerns?
> > Or should I respin and ask Andrew to pick it up?
> >
> > [1] https://lore.kernel.org/lkml/20180712080006.GA328@dhcp22.suse.cz/
>
> Michal acked #11 (the docs patch) in particular but not the series as a
> whole. But it's the rest of the series that I was most worried about :)
> I'm happy for the patches to take either path, but I'd really like an
> explicit ack before I apply that many changes directly to the MM code...
Andrew,
Can you please take a look at this series? The thread starts at [1] and if
it'd be more convenient to you I can respin the whole set.
[1] https://lore.kernel.org/lkml/1530370506-21751-1-git-send-email-rppt@linux.vnet.ibm.com/
> Thanks,
>
> jon
>
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2018-07-18 17:01 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-30 14:54 [PATCH v2 00/11] docs/mm: add boot time memory management docs Mike Rapoport
2018-06-30 14:54 ` Mike Rapoport
2018-06-30 14:54 ` [PATCH v2 01/11] mm/bootmem: drop duplicated kernel-doc comments Mike Rapoport
2018-06-30 14:54 ` Mike Rapoport
2018-06-30 14:54 ` [PATCH v2 02/11] docs/mm: nobootmem: fixup " Mike Rapoport
2018-06-30 14:54 ` Mike Rapoport
2018-06-30 14:54 ` [PATCH v2 03/11] docs/mm: bootmem: fix kernel-doc warnings Mike Rapoport
2018-06-30 14:54 ` Mike Rapoport
2018-06-30 14:54 ` [PATCH v2 04/11] docs/mm: bootmem: add kernel-doc description of 'struct bootmem_data' Mike Rapoport
2018-06-30 14:54 ` Mike Rapoport
2018-06-30 14:55 ` [PATCH v2 05/11] docs/mm: bootmem: add overview documentation Mike Rapoport
2018-06-30 14:55 ` Mike Rapoport
2018-06-30 14:55 ` [PATCH v2 06/11] mm/memblock: add a name for memblock flags enumeration Mike Rapoport
2018-06-30 14:55 ` Mike Rapoport
2018-07-12 8:00 ` Michal Hocko
2018-07-12 8:00 ` Michal Hocko
2018-06-30 14:55 ` [PATCH v2 07/11] docs/mm: memblock: update kernel-doc comments Mike Rapoport
2018-06-30 14:55 ` Mike Rapoport
2018-06-30 14:55 ` [PATCH v2 08/11] docs/mm: memblock: add kernel-doc comments for memblock_add[_node] Mike Rapoport
2018-06-30 14:55 ` Mike Rapoport
2018-06-30 14:55 ` [PATCH v2 09/11] docs/mm: memblock: add kernel-doc description for memblock types Mike Rapoport
2018-06-30 14:55 ` Mike Rapoport
2018-06-30 14:55 ` [PATCH v2 10/11] docs/mm: memblock: add overview documentation Mike Rapoport
2018-06-30 14:55 ` Mike Rapoport
2018-06-30 14:55 ` [PATCH v2 11/11] docs/mm: add description of boot time memory management Mike Rapoport
2018-06-30 14:55 ` Mike Rapoport
2018-07-03 12:23 ` Michal Hocko
2018-07-03 12:23 ` Michal Hocko
2018-07-12 7:26 ` Mike Rapoport
2018-07-12 7:26 ` Mike Rapoport
2018-07-01 15:26 ` [PATCH v2 00/11] docs/mm: add boot time memory management docs Randy Dunlap
2018-07-01 15:26 ` Randy Dunlap
2018-07-02 17:32 ` Jonathan Corbet
2018-07-02 17:32 ` Jonathan Corbet
2018-07-18 11:47 ` Mike Rapoport
2018-07-18 11:47 ` Mike Rapoport
2018-07-18 12:02 ` Jonathan Corbet
2018-07-18 12:02 ` Jonathan Corbet
2018-07-18 17:00 ` Mike Rapoport [this message]
2018-07-18 17:00 ` Mike Rapoport
2018-07-26 21:45 ` Jonathan Corbet
2018-07-26 21:45 ` Jonathan Corbet
2018-08-02 18:36 ` Jonathan Corbet
2018-08-02 18:36 ` Jonathan Corbet
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=20180718170043.GA23770@rapoport-lnx \
--to=rppt@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rdunlap@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 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.