Re: [GIT PULL][PATCH v4 0/9] Update to zstd-1.4.6

2020-10-01 Thread David Sterba
On Wed, Sep 30, 2020 at 08:49:49PM +, Nick Terrell wrote: > > On Sep 29, 2020, at 11:53 PM, Nick Terrell wrote: > > > > From: Nick Terrell > > It has been brought to my attention that patch 3 hasn’t made it to patchwork, > likely because it is too large. I’ll include a pull request in the n

Re: [PATCH 00/18] use semicolons rather than commas to separate statements

2020-10-01 Thread Mark Brown
On Wed, Sep 30, 2020 at 12:33:39PM -0700, Joe Perches wrote: > On Tue, 2020-09-29 at 12:37 +0100, Mark Brown wrote: > > Feel free to submit patches to b4. > Have you tried the existing option to send > thank you's on a specific ranges of patches? I am relying on b4 to identify which patches that

Re: [GIT PULL][PATCH v4 0/9] Update to zstd-1.4.6

2020-10-01 Thread Nick Terrell
> On Oct 1, 2020, at 3:18 AM, David Sterba wrote: > > On Wed, Sep 30, 2020 at 08:49:49PM +, Nick Terrell wrote: >>> On Sep 29, 2020, at 11:53 PM, Nick Terrell wrote: >>> >>> From: Nick Terrell >> >> It has been brought to my attention that patch 3 hasn’t made it to patchwork, >> likely

[PATCH] lib: zstd: fix semicolon.cocci warnings

2020-10-01 Thread kernel test robot
From: kernel test robot lib/zstd/compress/zstd_compress.c:3248:24-25: Unneeded semicolon Remove unneeded semicolon. Generated by: scripts/coccinelle/misc/semicolon.cocci CC: Nick Terrell Signed-off-by: kernel test robot --- url: https://github.com/0day-ci/linux/commits/Nick-Terrell/Up

Re: [PATCH v4 3/9] lib: zstd: Upgrade to latest upstream zstd version 1.4.6

2020-10-01 Thread kernel test robot
Hi Nick, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on kdave/for-next] [also build test WARNING on f2fs/dev-test linus/master v5.9-rc7 next-20201001] [cannot apply to cryptodev/master crypto/master] [If your patch is applied to the wrong git tree, kindly drop

Re: [PATCH] random: use correct memory barriers for crng_node_pool

2020-10-01 Thread Eric Biggers
On Thu, Sep 24, 2020 at 08:31:02PM -0700, Paul E. McKenney wrote: > On Thu, Sep 24, 2020 at 07:09:08PM -0700, Eric Biggers wrote: > > On Thu, Sep 24, 2020 at 05:59:34PM -0700, Paul E. McKenney wrote: > > > On Tue, Sep 22, 2020 at 02:55:58PM -0700, Eric Biggers wrote: > > > > On Tue, Sep 22, 2020 at

Re: [PATCH][next] crypto: sun8i-ss@: fix memory leak on pointer d

2020-10-01 Thread Herbert Xu
On Tue, Sep 29, 2020 at 02:38:19PM +0100, Colin King wrote: > From: Colin Ian King > > Currently the error return path on a failed dma_mapping_error call > is not kfree'ing memory allocated to d. Add an extra error exit label > to end of the function where the kfree and return occurs to fix this

get_cycles from modular code in jitterentropy, was Re: [PATCH] clocksource: clint: Export clint_time_val for modules

2020-10-01 Thread Christoph Hellwig
On Tue, Sep 29, 2020 at 11:56:18PM -0700, Palmer Dabbelt wrote: > clint_time_val will soon be used by the RISC-V implementation of > random_get_entropy(), which is a static inline function that may be used by > modules (at least CRYPTO_JITTERENTROPY=m). At very least this needs to be an EXPORT_SYM

Re: get_cycles from modular code in jitterentropy, was Re: [PATCH] clocksource: clint: Export clint_time_val for modules

2020-10-01 Thread Stephan Mueller
Am Freitag, 2. Oktober 2020, 08:49:05 CEST schrieb Christoph Hellwig: Hi Christoph, > On Tue, Sep 29, 2020 at 11:56:18PM -0700, Palmer Dabbelt wrote: > > clint_time_val will soon be used by the RISC-V implementation of > > random_get_entropy(), which is a static inline function that may be used >

Re: [PATCH v4 0/9] Update to zstd-1.4.6

2020-10-01 Thread Christoph Hellwig
On Wed, Sep 30, 2020 at 08:05:45PM +, Nick Terrell wrote: > > > > On Sep 29, 2020, at 11:53 PM, Christoph Hellwig wrote: > > > > As you keep resend this I keep retelling you that should not do it. > > Please provide a proper Linux API, and switch to that. Versioned APIs > > have absolutely

Re: [GIT PULL][PATCH v4 0/9] Update to zstd-1.4.6

2020-10-01 Thread Christoph Hellwig
On Thu, Oct 01, 2020 at 06:35:34PM +, Nick Terrell wrote: > I???m open to suggestions on how to get a zstd update done better. I don???t > know of any way to break this patch up into smaller patches that all compile. > The code is all generated directly from upstream and modified to work in the