From: Michal Hocko <mhocko@kernel.org>
To: Mike Rapoport <rppt@linux.ibm.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] MAINTAINERS: add entry for memblock
Date: Thu, 14 Feb 2019 12:30:47 +0100 [thread overview]
Message-ID: <20190214113047.GB4525@dhcp22.suse.cz> (raw)
In-Reply-To: <20190214093630.GC9063@rapoport-lnx>
On Thu 14-02-19 11:36:31, Mike Rapoport wrote:
> Hi,
>
> I was surprised to see lots of activity around memblock (beside the churn
> I create there), so I'm going to look after it.
>
> >From 7b3d02797ef18fb1c515f32125fb9b0055a312de Mon Sep 17 00:00:00 2001
> From: Mike Rapoport <rppt@linux.ibm.com>
> Date: Thu, 14 Feb 2019 11:21:26 +0200
> Subject: [PATCH] MAINTAINERS: add entry for memblock
>
> Add entry for memblock in MAINTAINERS file
It is great that this code gains an official maintainer finaly. Thanks
for stepping in.
> Signed-off-by: Mike Rapoport <rppt@linux.ibm.com>
Acked-by: Michal Hocko <mhocko@suse.com>
> ---
> MAINTAINERS | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 41ce5f4ad838..4e870d8b31af 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -9792,6 +9792,14 @@ F: kernel/sched/membarrier.c
> F: include/uapi/linux/membarrier.h
> F: arch/powerpc/include/asm/membarrier.h
>
> +MEMBLOCK
> +M: Mike Rapoport <rppt@linux.ibm.com>
> +L: linux-mm@kvack.org
> +S: Maintained
> +F: include/linux/memblock.h
> +F: mm/memblock.c
> +F: Documentation/core-api/boot-time-mm.rst
> +
> MEMORY MANAGEMENT
> L: linux-mm@kvack.org
> W: http://www.linux-mm.org
> --
> 2.7.4
--
Michal Hocko
SUSE Labs
prev parent reply other threads:[~2019-02-14 11:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-14 9:36 Mike Rapoport
2019-02-14 11:30 ` Michal Hocko [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=20190214113047.GB4525@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rppt@linux.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox