[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250318165312.GI32661@suse.cz>
Date: Tue, 18 Mar 2025 17:53:12 +0100
From: David Sterba <dsterba@...e.cz>
To: Nick Terrell <nickrterrell@...il.com>
Cc: linux-kernel@...r.kernel.org, Nick Terrell <terrelln@...com>,
Kernel Team <Kernel-team@...com>, David Sterba <dsterba@...e.com>
Subject: Re: [PATCH 0/1] zstd: Import upstream v1.5.7
On Tue, Mar 18, 2025 at 02:16:36PM +0100, David Sterba 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'm taking a proactive step and the tag mentioned above is now merged to
my btrfs for-next branch snapshot. As it's been pulled from your tree
the commit id (65d1f5507ed2c78c64fce40e44e5574a9419eb09) is the same and
git will handle it transparently in case you update your zstd-next
branch.
Powered by blists - more mailing lists