All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Rapoport <rppt@linux.ibm.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Christoph Lameter <cl@linux.com>,
	Pekka Enberg <penberg@kernel.org>,
	David Rientjes <rientjes@google.com>,
	Joonsoo Kim <iamjoonsoo.kim@lge.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-doc@vger.kernel.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] docs/mm-api: link kernel-doc comments from slab_common.c
Date: Fri, 21 Dec 2018 16:29:45 +0200	[thread overview]
Message-ID: <1E20B2F5-93F6-4763-9068-75630DF2541C@linux.ibm.com> (raw)
In-Reply-To: <20181220083423.40233348@lwn.net>



On December 20, 2018 5:34:23 PM GMT+02:00, Jonathan Corbet <corbet@lwn.net> wrote:
>On Thu, 20 Dec 2018 09:59:13 +0200
>Mike Rapoport <rppt@linux.ibm.com> wrote:
>
>> ping?
>
>Sorry, been traveling,

No problem, I just wanted to make sure it didn't fall between the cracks.

> and I still don't really know what to do with
>patches that are more mm/ than Documentation/. 

Well, these seem to be quite documentation, although they touch mm files ;-)

> I've just applied these, though.

Thanks!

>Thanks,
>
>jon

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.


      reply	other threads:[~2018-12-21 14:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-06 21:12 [PATCH 0/2] docs/mm-api: link kernel-doc comments from slab_common.c Mike Rapoport
2018-12-06 21:13 ` [PATCH 1/2] slab: make kmem_cache_create{_usercopy} description proper kernel-doc Mike Rapoport
2018-12-09 23:02   ` David Rientjes
2018-12-06 21:13 ` [PATCH 2/2] docs/mm-api: link slab_common.c to "The Slab Cache" section Mike Rapoport
2018-12-09 23:02   ` David Rientjes
2018-12-20  7:59 ` [PATCH 0/2] docs/mm-api: link kernel-doc comments from slab_common.c Mike Rapoport
2018-12-20 15:34   ` Jonathan Corbet
2018-12-21 14:29     ` 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=1E20B2F5-93F6-4763-9068-75630DF2541C@linux.ibm.com \
    --to=rppt@linux.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=cl@linux.com \
    --cc=corbet@lwn.net \
    --cc=iamjoonsoo.kim@lge.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=penberg@kernel.org \
    --cc=rientjes@google.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.