From: Minchan Kim <minchan@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Nitin Gupta <ngupta@vflare.org>,
linux-kernel@vger.kernel.org, Jens Axboe <axboe@kernel.dk>,
linux-mm@kvack.org, Minchan Kim <minchan@kernel.org>
Subject: [PATCH 0/5] zram/zsmalloc copyright and maintainers
Date: Tue, 17 Dec 2013 15:11:58 +0900 [thread overview]
Message-ID: <1387260723-15817-1-git-send-email-minchan@kernel.org> (raw)
I and Nitin discussed how to maintain zsmalloc and zram.
Nitin wanted me to maintain zram because he doesn't have enough
bandwidth to quickly handle any issues that might arise and
I have maintained zram/zsmalloc during last two years so he
will be listed as co-maintainer.
Minchan Kim (5):
zram: remove old private project comment
zram: add copyright
zsmalloc: add copyright
zram: add zram maintainers
zsmalloc: add maintainers
Documentation/blockdev/zram.txt | 6 ------
MAINTAINERS | 16 ++++++++++++++++
drivers/block/zram/Kconfig | 1 -
drivers/block/zram/zram_drv.c | 2 +-
drivers/block/zram/zram_drv.h | 2 +-
include/linux/zsmalloc.h | 1 +
mm/zsmalloc.c | 1 +
7 files changed, 20 insertions(+), 9 deletions(-)
--
1.7.9.5
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2013-12-17 6:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-17 6:11 Minchan Kim [this message]
2013-12-17 6:11 ` [PATCH 1/5] zram: remove old private project comment Minchan Kim
2013-12-17 6:12 ` [PATCH 2/5] zram: add copyright Minchan Kim
2013-12-17 6:12 ` [PATCH 3/5] zsmalloc: " Minchan Kim
2013-12-17 6:12 ` [PATCH 4/5] zram: add zram maintainers Minchan Kim
2013-12-17 6:12 ` [PATCH 5/5] zsmalloc: add maintainers Minchan Kim
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=1387260723-15817-1-git-send-email-minchan@kernel.org \
--to=minchan@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ngupta@vflare.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;
as well as URLs for NNTP newsgroup(s).