All of lore.kernel.org
 help / color / mirror / Atom feed
From: Herbert Xu <herbert@gondor.apana.org.au>
To: Nick Terrell <terrelln@fb.com>
Cc: "Eric Biggers" <ebiggers@kernel.org>,
	"Nick Terrell" <nickrterrell@gmail.com>,
	"squashfs-devel@lists.sourceforge.net"
	<squashfs-devel@lists.sourceforge.net>,
	"Christoph Hellwig" <hch@infradead.org>,
	"Yann Collet" <cyan@fb.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-f2fs-devel@lists.sourceforge.net"
	<linux-f2fs-devel@lists.sourceforge.net>,
	"Petr Malat" <oss@malat.biz>, "Chris Mason" <clm@fb.com>,
	"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
	"Kernel Team" <Kernel-team@fb.com>,
	"Michał Mirosław" <mirq-linux@rere.qmqm.pl>,
	"Niket Agarwal" <niketa@fb.com>,
	"Btrfs BTRFS" <linux-btrfs@vger.kernel.org>,
	"Johannes Weiner" <jweiner@fb.com>
Subject: Re: [f2fs-dev] [PATCH v7 0/3] Update to zstd-1.4.6
Date: Wed, 16 Dec 2020 11:58:07 +1100	[thread overview]
Message-ID: <20201216005806.GA26841@gondor.apana.org.au> (raw)
In-Reply-To: <B3F00261-E977-4B85-84CD-66B07DA79D9D@fb.com>

On Wed, Dec 16, 2020 at 12:48:51AM +0000, Nick Terrell wrote:
>
> Thanks for the advice! The first zstd patches went through Herbert’s tree, which is
> why I’ve sent them this way.

Sorry, but I'm not touch these patches as Christoph's objections
don't seem to have been addressed.

Cheers,
-- 
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt

WARNING: multiple messages have this Message-ID (diff)
From: Herbert Xu <herbert@gondor.apana.org.au>
To: Nick Terrell <terrelln@fb.com>
Cc: "Christoph Hellwig" <hch@infradead.org>,
	"Petr Malat" <oss@malat.biz>,
	"squashfs-devel@lists.sourceforge.net"
	<squashfs-devel@lists.sourceforge.net>,
	"Nick Terrell" <nickrterrell@gmail.com>,
	"Yann Collet" <cyan@fb.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-f2fs-devel@lists.sourceforge.net"
	<linux-f2fs-devel@lists.sourceforge.net>,
	"Eric Biggers" <ebiggers@kernel.org>, "Chris Mason" <clm@fb.com>,
	"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
	"Kernel Team" <Kernel-team@fb.com>,
	"Michał Mirosław" <mirq-linux@rere.qmqm.pl>,
	"Niket Agarwal" <niketa@fb.com>,
	"Btrfs BTRFS" <linux-btrfs@vger.kernel.org>,
	"Johannes Weiner" <jweiner@fb.com>
Subject: Re: [f2fs-dev] [PATCH v7 0/3] Update to zstd-1.4.6
Date: Wed, 16 Dec 2020 11:58:07 +1100	[thread overview]
Message-ID: <20201216005806.GA26841@gondor.apana.org.au> (raw)
In-Reply-To: <B3F00261-E977-4B85-84CD-66B07DA79D9D@fb.com>

On Wed, Dec 16, 2020 at 12:48:51AM +0000, Nick Terrell wrote:
>
> Thanks for the advice! The first zstd patches went through Herbert’s tree, which is
> why I’ve sent them this way.

Sorry, but I'm not touch these patches as Christoph's objections
don't seem to have been addressed.

Cheers,
-- 
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt


_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

  reply	other threads:[~2020-12-16  0:59 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-03 20:51 [PATCH v7 0/3] Update to zstd-1.4.6 Nick Terrell
2020-12-03 20:51 ` [f2fs-dev] " Nick Terrell
2020-12-03 20:51 ` [PATCH v7 1/3] lib: zstd: Add kernel-specific API Nick Terrell
2020-12-03 20:51   ` [f2fs-dev] " Nick Terrell
2020-12-03 20:51 ` [PATCH v7 2/3] lib: zstd: Add decompress_sources.h for decompress_unzstd Nick Terrell
2020-12-03 20:51   ` [f2fs-dev] " Nick Terrell
2020-12-03 20:51 ` [PATCH v7 3/3] lib: zstd: Upgrade to latest upstream zstd version 1.4.6 Nick Terrell
2020-12-03 20:51   ` [f2fs-dev] " Nick Terrell
2020-12-15 20:58 ` [PATCH v7 0/3] Update to zstd-1.4.6 Nick Terrell
2020-12-15 20:58   ` [f2fs-dev] " Nick Terrell via Linux-f2fs-devel
2020-12-16  0:00   ` Eric Biggers
2020-12-16  0:00     ` Eric Biggers
2020-12-16  0:48     ` Nick Terrell
2020-12-16  0:48       ` Nick Terrell via Linux-f2fs-devel
2020-12-16  0:58       ` Herbert Xu [this message]
2020-12-16  0:58         ` Herbert Xu
2020-12-16  1:12         ` Nick Terrell
2020-12-16  1:12           ` Nick Terrell via Linux-f2fs-devel
2020-12-16 18:50         ` David Sterba
2020-12-16 18:50           ` David Sterba
2020-12-16 22:07           ` Nick Terrell
2020-12-16 22:07             ` Nick Terrell via Linux-f2fs-devel
2020-12-17  1:23             ` Michał Mirosław
2020-12-17  1:23               ` Michał Mirosław
2020-12-18 18:57               ` Nick Terrell
2020-12-18 18:57                 ` Nick Terrell via Linux-f2fs-devel
2021-02-27  9:33 ` Oleksandr Natalenko
2021-02-27  9:33   ` [f2fs-dev] " Oleksandr Natalenko via Linux-f2fs-devel

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=20201216005806.GA26841@gondor.apana.org.au \
    --to=herbert@gondor.apana.org.au \
    --cc=Kernel-team@fb.com \
    --cc=clm@fb.com \
    --cc=cyan@fb.com \
    --cc=ebiggers@kernel.org \
    --cc=hch@infradead.org \
    --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=nickrterrell@gmail.com \
    --cc=niketa@fb.com \
    --cc=oss@malat.biz \
    --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 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.