All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Nick Terrell <nickrterrell@gmail.com>
Cc: linux-kernel@vger.kernel.org, Nick Terrell <terrelln@fb.com>,
	Kernel Team <Kernel-team@fb.com>, David Sterba <dsterba@suse.com>
Subject: Re: [PATCH 0/1] zstd: Import upstream v1.5.7
Date: Tue, 18 Mar 2025 14:16:36 +0100	[thread overview]
Message-ID: <20250318131636.GC32661@suse.cz> (raw)
In-Reply-To: <20250313205923.4105088-1-nickrterrell@gmail.com>

On Thu, Mar 13, 2025 at 01:59:20PM -0700, Nick Terrell wrote:
> From: Nick Terrell <terrelln@fb.com>
> 
> Since this is a large patch, I have also prepared a pull request as an
> alternate means of fetching the commit:
> 
> The following changes since commit 7eb172143d5508b4da468ed59ee857c6e5e01da6:
> 
>   Linux 6.14-rc5 (2025-03-02 11:48:20 -0800)
> 
> are available in the Git repository at:
> 
>   https://github.com/terrelln/linux.git tags/2025-03-13-zstd-v1.5.7-v1

This tag is not in the branch that is pulled to the linux-next tree, the
zstd-next branch still points to v6.14-rc5. This means the 1.5.7 update
hasn't been exposed to linux-next testing. Please update the branch to
the tag as well, the merge window opens next week leaving little time
before sending the pull request.

I've tested this patch with fstests and btrfs, no problems found, but
regarding the process the updates need to be in linux-next 1-2 weeks
before the merge window. We're past that. As this is restarting the zstd
merging I hope we can get away with that this time, skipping another
development cycle would be unfortunate but also not helping anything.

  parent reply	other threads:[~2025-03-18 13:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-13 20:59 [PATCH 0/1] zstd: Import upstream v1.5.7 Nick Terrell
2025-03-13 20:59 ` [PATCH 1/1] " Nick Terrell
2025-03-18 13:16 ` David Sterba [this message]
2025-03-18 16:53   ` [PATCH 0/1] " David Sterba
2025-03-19 17:12   ` Nick Terrell

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=20250318131636.GC32661@suse.cz \
    --to=dsterba@suse.cz \
    --cc=Kernel-team@fb.com \
    --cc=dsterba@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nickrterrell@gmail.com \
    --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.