mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nick Terrell <terrelln@meta.com>
To: "dsterba@suse.cz" <dsterba@suse.cz>
Cc: Nick Terrell <nickrterrell@gmail.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Nick Terrell <terrelln@meta.com>,
	Kernel Team <kernel-team@meta.com>,
	David Sterba <dsterba@suse.com>
Subject: Re: [PATCH 0/1] zstd: Import upstream v1.5.7
Date: Wed, 19 Mar 2025 17:12:27 +0000	[thread overview]
Message-ID: <B79BD3D7-80D5-41A8-9402-571EB6205701@meta.com> (raw)
In-Reply-To: <20250318131636.GC32661@suse.cz>



> On Mar 18, 2025, at 6:16 AM, David Sterba <dsterba@suse.cz> wrote:
> 
> > 
> 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.

Thanks David, I've pushed my linux-next trees yesterday morning,
hopefully it will be early enough. Thank you for testing as well!

Best,
Nick Terrell

      parent reply	other threads:[~2025-03-19 17:12 UTC|newest]

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

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=B79BD3D7-80D5-41A8-9402-571EB6205701@meta.com \
    --to=terrelln@meta.com \
    --cc=dsterba@suse.com \
    --cc=dsterba@suse.cz \
    --cc=kernel-team@meta.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nickrterrell@gmail.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

all inboxes | Powered by JetHome®