[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <025719a2-2432-8204-201f-adbbd293fa9a@toxicpanda.com>
Date: Fri, 6 Nov 2020 12:15:36 -0500
From: Josef Bacik <josef@...icpanda.com>
To: Nick Terrell <nickrterrell@...il.com>,
Herbert Xu <herbert@...dor.apana.org.au>
Cc: linux-crypto@...r.kernel.org, linux-btrfs@...r.kernel.org,
squashfs-devel@...ts.sourceforge.net,
linux-f2fs-devel@...ts.sourceforge.net,
linux-kernel@...r.kernel.org, Kernel Team <Kernel-team@...com>,
Nick Terrell <terrelln@...com>, Chris Mason <clm@...com>,
Petr Malat <oss@...at.biz>, Johannes Weiner <jweiner@...com>,
Niket Agarwal <niketa@...com>, Yann Collet <cyan@...com>
Subject: Re: [GIT PULL][PATCH v5 0/9] Update to zstd-1.4.6
On 11/3/20 1:05 AM, Nick Terrell wrote:
> From: Nick Terrell <terrelln@...com>
>
> Please pull from
>
> git@...hub.com:terrelln/linux.git tags/v5-zstd-1.4.6
>
> to get these changes. Alternatively the patchset is included.
>
Where did we come down on the code formatting question? Personally I'm of the
mind that as long as the consumers themselves adhere to the proper coding style
I'm fine not maintaining the code style as long as we get the benefit of easily
syncing in code from the upstream project. Thanks,
Josef
Powered by blists - more mailing lists