linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nick Terrell <nickrterrell@gmail.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: linux-crypto@vger.kernel.org, linux-btrfs@vger.kernel.org,
	squashfs-devel@lists.sourceforge.net,
	linux-f2fs-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org, "Kernel Team" <Kernel-team@fb.com>,
	"Nick Terrell" <nickrterrell@gmail.com>,
	"Nick Terrell" <terrelln@fb.com>, "Chris Mason" <clm@fb.com>,
	"Petr Malat" <oss@malat.biz>, "Johannes Weiner" <jweiner@fb.com>,
	"Niket Agarwal" <niketa@fb.com>, "Yann Collet" <cyan@fb.com>,
	"Christoph Hellwig" <hch@infradead.org>,
	"Michał Mirosław" <mirq-linux@rere.qmqm.pl>,
	"David Sterba" <dsterba@suse.cz>,
	"Oleksandr Natalenko" <oleksandr@natalenko.name>,
	"Felix Handte" <felixh@fb.com>,
	"Eric Biggers" <ebiggers@kernel.org>,
	"Randy Dunlap" <rdunlap@infradead.org>
Subject: [PATCH v11 4/4] MAINTAINERS: Add maintainer entry for zstd
Date: Thu, 29 Apr 2021 18:31:57 -0700	[thread overview]
Message-ID: <20210430013157.747152-5-nickrterrell@gmail.com> (raw)
In-Reply-To: <20210430013157.747152-1-nickrterrell@gmail.com>

From: Nick Terrell <terrelln@fb.com>

Adds a maintainer entry for zstd listing myself as the maintainer for
all zstd code, pointing to the upstream issues tracker for bugs, and
listing my linux repo as the tree.

Signed-off-by: Nick Terrell <terrelln@fb.com>
---
 MAINTAINERS | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/MAINTAINERS b/MAINTAINERS
index 9450e052f1b1..7025c67248f7 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -19912,6 +19912,18 @@ F:	Documentation/vm/zsmalloc.rst
 F:	include/linux/zsmalloc.h
 F:	mm/zsmalloc.c
 
+ZSTD
+M:	Nick Terrell <terrelln@fb.com>
+S:	Maintained
+B:	https://github.com/facebook/zstd/issues
+T:	git git://github.com/terrelln/linux.git
+F:	include/linux/zstd*
+F:	lib/zstd/
+F:	lib/decompress_unzstd.c
+F:	crypto/zstd.c
+N:	zstd
+K:	zstd
+
 ZSWAP COMPRESSED SWAP CACHING
 M:	Seth Jennings <sjenning@redhat.com>
 M:	Dan Streetman <ddstreet@ieee.org>
-- 
2.31.1


  parent reply	other threads:[~2021-04-30  1:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-30  1:31 [GIT PULL][PATCH v11 0/4] Update to zstd-1.4.10 Nick Terrell
2021-04-30  1:31 ` [PATCH v11 1/4] lib: zstd: Add kernel-specific API Nick Terrell
2021-04-30  1:31 ` [PATCH v11 2/4] lib: zstd: Add decompress_sources.h for decompress_unzstd Nick Terrell
2021-04-30  1:31 ` [PATCH v11 3/4] lib: zstd: Upgrade to latest upstream zstd version 1.4.10 Nick Terrell
2021-04-30  1:31 ` Nick Terrell [this message]
2021-05-11 20:53 ` [GIT PULL][PATCH v11 0/4] Update to zstd-1.4.10 Nick Terrell
2021-05-12 19:49   ` David Sterba

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=20210430013157.747152-5-nickrterrell@gmail.com \
    --to=nickrterrell@gmail.com \
    --cc=Kernel-team@fb.com \
    --cc=clm@fb.com \
    --cc=cyan@fb.com \
    --cc=dsterba@suse.cz \
    --cc=ebiggers@kernel.org \
    --cc=felixh@fb.com \
    --cc=hch@infradead.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=jweiner@fb.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mirq-linux@rere.qmqm.pl \
    --cc=niketa@fb.com \
    --cc=oleksandr@natalenko.name \
    --cc=oss@malat.biz \
    --cc=rdunlap@infradead.org \
    --cc=squashfs-devel@lists.sourceforge.net \
    --cc=terrelln@fb.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;
as well as URLs for NNTP newsgroup(s).