All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean-Denis Girard <jd.girard@sysnux.pf>
To: linux-crypto@vger.kernel.org
Cc: linux-next@vger.kernel.org, linux-btrfs@vger.kernel.org,
	linux-f2fs-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] zstd changes for linux-next
Date: Tue, 2 Nov 2021 18:30:20 -1000	[thread overview]
Message-ID: <slt39h$k3q$1@ciao.gmane.io> (raw)
In-Reply-To: <20211006191724.3187129-1-nickrterrell@gmail.com>


Le 06/10/2021 à 09:17, Nick Terrell a écrit :
> From: Nick Terrell <terrelln@fb.com>
> 
> The following changes since commit 9e1ff307c779ce1f0f810c7ecce3d95bbae40896:
> 
>    Linux 5.15-rc4 (2021-10-03 14:08:47 -0700)
> 
> are available in the Git repository at:
> 
>    https://github.com/terrelln/linux.git zstd-1.4.10
> 
> for you to fetch changes up to a0ccd980d5048053578f3b524e3cd3f5d980a9c5:
> 
>    MAINTAINERS: Add maintainer entry for zstd (2021-10-04 20:04:32 -0700)
> 
> I would like to merge this pull request into linux-next to bake, and then submit
> the PR to Linux in the 5.16 merge window. If you have been a part of the
> discussion, are a maintainer of a caller of zstd, tested this code, or otherwise
> been involved, thank you! And could you please respond below with an appropiate
> tag, so I can collect support for the PR
> 
> Best,
> Nick Terrell


I have used this patch for a while on 5.14.x, and on 5.15 since 
yesterday: no problem found.

Tested-by: Jean-Denis Girard <jd.girard@sysnux.pf>


Thanks,
-- 
Jean-Denis Girard

SysNux                   Systèmes   Linux   en   Polynésie  française
https://www.sysnux.pf/   Tél: +689 40.50.10.40 / GSM: +689 87.797.527


WARNING: multiple messages have this Message-ID (diff)
From: Jean-Denis Girard <jd.girard@sysnux.pf>
To: linux-next@vger.kernel.org
Cc: linux-crypto@vger.kernel.org, linux-btrfs@vger.kernel.org,
	linux-f2fs-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] zstd changes for linux-next
Date: Tue, 2 Nov 2021 18:30:20 -1000	[thread overview]
Message-ID: <slt39h$k3q$1@ciao.gmane.io> (raw)
In-Reply-To: <20211006191724.3187129-1-nickrterrell@gmail.com>


Le 06/10/2021 à 09:17, Nick Terrell a écrit :
> From: Nick Terrell <terrelln@fb.com>
> 
> The following changes since commit 9e1ff307c779ce1f0f810c7ecce3d95bbae40896:
> 
>    Linux 5.15-rc4 (2021-10-03 14:08:47 -0700)
> 
> are available in the Git repository at:
> 
>    https://github.com/terrelln/linux.git zstd-1.4.10
> 
> for you to fetch changes up to a0ccd980d5048053578f3b524e3cd3f5d980a9c5:
> 
>    MAINTAINERS: Add maintainer entry for zstd (2021-10-04 20:04:32 -0700)
> 
> I would like to merge this pull request into linux-next to bake, and then submit
> the PR to Linux in the 5.16 merge window. If you have been a part of the
> discussion, are a maintainer of a caller of zstd, tested this code, or otherwise
> been involved, thank you! And could you please respond below with an appropiate
> tag, so I can collect support for the PR
> 
> Best,
> Nick Terrell


I have used this patch for a while on 5.14.x, and on 5.15 since 
yesterday: no problem found.

Tested-by: Jean-Denis Girard <jd.girard@sysnux.pf>


Thanks,
-- 
Jean-Denis Girard

SysNux                   Systèmes   Linux   en   Polynésie  française
https://www.sysnux.pf/   Tél: +689 40.50.10.40 / GSM: +689 87.797.527


  parent reply	other threads:[~2021-11-03  4:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-06 19:17 [GIT PULL] zstd changes for linux-next Nick Terrell
2021-10-06 19:17 ` [f2fs-dev] " Nick Terrell
2021-10-06 21:39 ` Sedat Dilek
2021-10-06 21:39   ` [f2fs-dev] " Sedat Dilek
2021-10-06 23:02   ` Nick Terrell
2021-10-06 23:02     ` [f2fs-dev] " Nick Terrell via Linux-f2fs-devel
2021-10-07  1:33     ` Sedat Dilek
2021-10-06 21:57 ` Stephen Rothwell
2021-10-06 23:03   ` Nick Terrell
2021-10-06 23:03     ` [f2fs-dev] " Nick Terrell via Linux-f2fs-devel
2021-11-03  4:30 ` Jean-Denis Girard [this message]
2021-11-03  4:30   ` Jean-Denis Girard

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='slt39h$k3q$1@ciao.gmane.io' \
    --to=jd.girard@sysnux.pf \
    --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=linux-next@vger.kernel.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 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.