[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <B79BD3D7-80D5-41A8-9402-571EB6205701@meta.com>
Date: Wed, 19 Mar 2025 17:12:27 +0000
From: Nick Terrell <terrelln@...a.com>
To: "dsterba@...e.cz" <dsterba@...e.cz>
CC: Nick Terrell <nickrterrell@...il.com>,
"linux-kernel@...r.kernel.org"
<linux-kernel@...r.kernel.org>,
Nick Terrell <terrelln@...a.com>, Kernel Team
<kernel-team@...a.com>,
David Sterba <dsterba@...e.com>
Subject: Re: [PATCH 0/1] zstd: Import upstream v1.5.7
> On Mar 18, 2025, at 6:16 AM, David Sterba <dsterba@...e.cz> wrote:
>
> >
> On Thu, Mar 13, 2025 at 01:59:20PM -0700, Nick Terrell wrote:
>> From: Nick Terrell <terrelln@...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
Powered by blists - more mailing lists