[PATCH] net: lan9303: fix missing error handling

Both lan9303_phy_write and regmap_write may fail. The fix adds the error handling to print error messages upon failure. Signed-off-by: Kangjie Lu --- drivers/net/dsa/lan9303-core.c | 6 ++ 1 file changed, 6 insertions(+) diff --git a/drivers/net/dsa/lan9303-core.c

[PATCH] net: 8390: fix potential NULL pointer dereferences

In case ioremap fails, the fix returns to avoid NULL pointer dereferences. Signed-off-by: Kangjie Lu --- drivers/net/ethernet/8390/pcnet_cs.c | 8 1 file changed, 8 insertions(+) diff --git a/drivers/net/ethernet/8390/pcnet_cs.c b/drivers/net/ethernet/8390/pcnet_cs.c index

[PATCH] net: liquidio: fix a NULL pointer dereference

In case octeon_alloc_soft_command fails, the fix reports the error and returns to avoid NULL pointer dereference. Signed-off-by: Kangjie Lu --- drivers/net/ethernet/cavium/liquidio/lio_main.c | 5 + 1 file changed, 5 insertions(+) diff --git

Re: [PATCH v2] iio: cros_ec: Fix the maths for gyro scale calculation

/linux/commits/Enric-Balletbo-i-Serra/iio-cros_ec-Fix-the-maths-for-gyro-scale-calculation/20190310-155057 base: https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git togreg config: i386-randconfig-x005-201910 (attached as .config) compiler: gcc-8 (Debian 8.3.0-2) 8.3.0 reproduce

Re: DRM-based Oops viewer

Hell Ahmed. Ahmed S. Darwish - 10.03.19, 02:31: > Hello DRM/UEFI maintainers, > > Several years ago, I wrote a set of patches to dump the kernel > log to disk upon panic -- through BIOS INT 0x13 services. [1] > > The overwhelming response was that it's unsafe to do this in a > generic manner.

[char-misc] mei: convert to SPDX license tags

Signed-off-by: Tomas Winkler --- drivers/misc/mei/Kconfig | 1 + drivers/misc/mei/Makefile| 2 +- drivers/misc/mei/bus-fixup.c | 13 +- drivers/misc/mei/bus.c | 14 ++- drivers/misc/mei/client.c| 13 +- drivers/misc/mei/client.h| 13

Re: [PATCH v2] iio: proximity: as3935: fix use-after-free on device remove

On Sat, 9 Mar 2019 08:03:44 -0500 Sven Van Asbroeck wrote: > On Sat, Mar 9, 2019 at 5:24 AM Tomasz Duszynski wrote: > > > > What I meant is that delayed work initialization could stay where it was. > > The reason you moved it is readability improvement so to me it is more > > of a cleanup hence

Re: [PATCH] iio: common: ssp_sensors: Initialize calculated_time in ssp_common_process_data

On Thu, 7 Mar 2019 16:35:26 -0800 Nick Desaulniers wrote: > On Thu, Mar 7, 2019 at 1:46 PM Nathan Chancellor > wrote: > > > > When building with -Wsometimes-uninitialized, Clang warns: > > > > drivers/iio/common/ssp_sensors/ssp_iio.c:95:6: warning: variable > > 'calculated_time' is used

Re: [PATCH] iio: adc: stmpe-adc: Shuffle an if statement around in stmpe_adc_isr

On Thu, 7 Mar 2019 10:31:55 -0800 Nick Desaulniers wrote: > On Thu, Mar 7, 2019 at 9:16 AM Nathan Chancellor > wrote: > > > > When building with -Wsometimes-uninitialized, Clang warns: > > > > drivers/iio/adc/stmpe-adc.c:204:13: warning: variable 'data' is used > > uninitialized whenever 'if'

Re: [PATCH v6 2/4] dt-bindings: iio/temperature: Add doc for thermocouple-type

On Thu, 7 Mar 2019 11:34:07 +0100 Patrick Havelange wrote: > This explains the new generic property "thermocouple-type" that > can be used with temperature sensors. > > Signed-off-by: Patrick Havelange I'm happy with this, but want to allow time for Rob and other devicetree types to have a

Re: [char-misc] mei: convert to SPDX license tags

On Sun, Mar 10, 2019 at 12:03:23PM +0200, Tomas Winkler wrote: > Signed-off-by: Tomas Winkler I can not take patches without any changelog text. Especially a patch that does not actually do what your subject: line says it does. > --- a/drivers/misc/mei/Makefile > +++

Re: [PATCH v6 4/4] iio:temperature: Add MAX31856 thermocouple support

On Thu, 7 Mar 2019 11:34:09 +0100 Patrick Havelange wrote: > From: Paresh Chaudhary > > This patch adds support for Maxim MAX31856 thermocouple > temperature sensor support. > > More information can be found in: > https://www.maximintegrated.com/en/ds/MAX31856.pdf > > NOTE: Driver support

Re: [PATCH] drivers: iio: Kconfig: pedantic cleanup

On Wed, 6 Mar 2019 15:52:23 +0100 "Enrico Weigelt, metux IT consult" wrote: > Formatting of Kconfig files doesn't look so pretty, so just > take damp cloth and clean it up. > > Signed-off-by: Enrico Weigelt, metux IT consult Thanks for sorting this. Every now and then I notice one of these

[PATCH v2 1/2] arm64, vmcoreinfo : Append 'PTRS_PER_PGD' to vmcoreinfo

With ARMv8.2-LVA architecture extension availability, arm64 hardware which supports this extension can support a virtual address-space upto 52-bits. Since at the moment we enable the support of this extension in kernel via CONFIG flags, e.g. - User-space 52-bit LVA via

[PATCH v2 0/2] Append new variables to vmcoreinfo (PTRS_PER_PGD for arm64 and MAX_PHYSMEM_BITS for all archs)

Changes since v1: - v1 was sent out as a single patch which can be seen here: http://lists.infradead.org/pipermail/kexec/2019-February/022411.html - v2 breaks the single patch into two independent patches: [PATCH 1/2] appends 'PTRS_PER_PGD' to vmcoreinfo for arm64 arch,

[PATCH v2 2/2] crash_core, vmcoreinfo: Append 'MAX_PHYSMEM_BITS' to vmcoreinfo

Right now user-space tools like 'makedumpfile' and 'crash' need to rely on a best-guess method of determining value of 'MAX_PHYSMEM_BITS' supported by underlying kernel. This value is used in user-space code to calculate the bit-space required to store a section for SPARESMEM (similar to the

Re: [PATCH 1/8] iio: adc: stm32-dfsdm: make spi_master_freq more accurate

On Wed, 6 Mar 2019 09:55:17 +0100 Fabrice Gasnier wrote: > When SPI clock isn't accurate, 'spi_master_freq' is filled in with > expected frequency. Use computed value instead: > - e.g. source clock / (CKOUTDIV + 1) > Also, current divider may be set to value that makes CKOUT to exceed >

Re: [tip:sched/core] sched/core: Fix a potential double-fetch bug in sched_copy_attr()

On Mon, 28 Jan 2019, Thomas Gleixner wrote: > On Mon, 28 Jan 2019, Peter Zijlstra wrote: > > On Sun, Jan 27, 2019 at 12:04:44PM +0100, Thomas Gleixner wrote: > > > On Mon, 21 Jan 2019, tip-bot for Kangjie Lu wrote: > > > > diff --git a/kernel/sched/core.c b/kernel/sched/core.c > > > > index

RE: [char-misc] mei: convert to SPDX license tags

> On Sun, Mar 10, 2019 at 12:03:23PM +0200, Tomas Winkler wrote: > > Signed-off-by: Tomas Winkler > > I can not take patches without any changelog text. Ok, my mistake. > > Especially a patch that does not actually do what your subject: line says it > does. Yep, I should be more verbose. >

Re: [PATCH 7/8] iio: adc: stm32-dfsdm: add support for buffer modes

On Wed, 6 Mar 2019 09:55:23 +0100 Fabrice Gasnier wrote: > DFSDM can operate using these buffer modes: > - INDIO_BUFFER_SOFTWARE: regular continuous conversions (no trigger) > but limited to 1 channel. User can set sampling frequency in this case. > - INDIO_BUFFER_TRIGGERED: triggered

Re: [char-misc] mei: convert to SPDX license tags

On Sun, Mar 10, 2019 at 10:14:03AM +, Winkler, Tomas wrote: > > Please break this up into two (at the least) patches and resend as a series. > > Can you be please, more specific what split are you expecting. You are doing lots of different types of things in the same patch. Break up the

RE: [char-misc] mei: convert to SPDX license tags

> > On Sun, Mar 10, 2019 at 10:14:03AM +, Winkler, Tomas wrote: > > > Please break this up into two (at the least) patches and resend as a > > > series. > > > > Can you be please, more specific what split are you expecting. > > You are doing lots of different types of things in the same

Re: [GIT PULL] arm64 updates for 5.1-rc1

Hi Linus, On Fri, Mar 08, 2019 at 04:42:23PM +, Catalin Marinas wrote: > The following changes since commit 6e4933a006616343f66c4702dc4fc56bb25e7b02: > > irqdesc: Add domain handler for NMIs (2019-02-05 14:37:05 +) > > are available in the Git repository at: > >

Re: [PATCH] iio: hmc5843_spi: fix a NULL pointer dereference

On Sat, 9 Mar 2019 12:56:27 -0600 Kangjie Lu wrote: > In case devm_regmap_init_spi fails and returns NULL, the fix > returns an error to avoid NULL pointer dereference > > Signed-off-by: Kangjie Lu Hi. The fix is good, but please do the same for the i2c element of the driver. I'd like them

[PATCH] static_assert: move before people start using it

Userspace places static_assert() macro at Signed-off-by: Alexey Dobriyan --- include/assert.h | 19 +++ include/linux/build_bug.h | 19 --- include/linux/fs.h|2 +- lib/vsprintf.c|1 + 4 files changed, 21 insertions(+),

Re: [PATCH v11 1/4] dmaengine: 8250_mtk_dma: add MediaTek uart DMA support

On Thu, Mar 7, 2019 at 9:45 AM Long Cheng wrote: > > In DMA engine framework, add 8250 uart dma to support MediaTek uart. > If MediaTek uart enabled(SERIAL_8250_MT6577), and want to improve > the performance, can enable the function. > > Signed-off-by: Long Cheng > --- >

[GIT pull] x86 fixes for 5.1

Linus, please pull the latest x86-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-urgent-for-linus A set of fixes for x86: - Make the unwinder more robust when it encounters a NULL pointer call, so the backtrace becomes more useful - Fix

[GIT pull] x86/asm for 5.1

Linus, please pull the latest x86-asm-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-asm-for-linus The following updates for 5.1 are available: - Add pinning of sensitive CR0/CR4 bits, i.e. WP and SMAP/SMEP as these have been targets of recent

[GIT pull] timer fix for 5.1

Linus, please pull the latest timers-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git timers-urgent-for-linus A single fix to prevent a unmet dependencies warning in Kconfig. Thanks, tglx --> Arnd Bergmann (1): time:

[GIT pull] core udpate for 5.1

Linus, please pull the latest core-core-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git core-core-for-linus A single commit adding a command line parameter which allows to set the watchdog threshold on the kernel command-line, so kernels with massive debug

[GIT pull] x86/boot fix for 5.1

Linus, please pull the latest x86-boot-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-boot-for-linus A trivial fix for the previous x86/boot pull request which did not make it in time. Thanks, tglx --> Louis Taylor (1):

[GIT pull] locking fixes for 5.1

Linus, please pull the latest locking-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git locking-urgent-for-linus A few fixes for lockdep: - Initialize lockdep internal RCU head after initializing RCU - Prevent use after free in a alloc_workqueue()

[GIT pull] perf updates for 5.1

Linus, please pull the latest perf-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git perf-urgent-for-linus Perf updates and fixes: Kernel: - Handle events which have the bpf_event attribute set as side band events as they carry information about

[GIT pull] scheduler updates for 5.1

Linus, please pull the latest sched-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git sched-urgent-for-linus A small set of fixes for the scheduler: - Prevent a 32bit math overflow in the cpufreq code - Fix a buffer overflow when scanning the

[PATCH] staging: e1000: e1000_main.c: remove extern declarations in .c file.

This patch fixes the checkpatch.pl warning: WARNING: externs should be avoided in .c files Some of the driver's function declared in e1000.h were declared a second time in e1000_main.c, triggering checkpatch.pl warnings. Signed-off-by: Quentin Deslandes ---

[PATCH] clk: rockchip: fix wrong clock definitions for rk3328

This patch fixes definition of several clock gate and select register that is wrong for rk3328 referring to the TRM and vendor kernel. Also use correct number of softrst registers. Fix clock definition for: - clk_crypto - aclk_h265 - pclk_h265 - aclk_h264 - hclk_h264 - aclk_axisram - aclk_gmac -

Re: [PATCH RESEND v5 2/5] namei: O_BENEATH-style path resolution flags

On 2019-03-09, Linus Torvalds wrote: > On Sat, Mar 9, 2019 at 9:26 AM Christian Brauner wrote: > > Aside from that I want to point out that it is non-trivial to do this in > > user space. > > Oh, absolutely agreed. It's easy to do it in the kernel, and doing it > anywhere else ends up having

Re: [PATCH v11 2/3] ipc: Conserve sequence numbers in ipcmni_extend mode

On 2/27/19 9:30 PM, Waiman Long wrote: On 11/20/2018 02:41 PM, Manfred Spraul wrote: From 6bbade73d21884258a995698f21ad3128df8e98a Mon Sep 17 00:00:00 2001 From: Manfred Spraul Date: Sat, 29 Sep 2018 15:43:28 +0200 Subject: [PATCH 2/2] ipc/util.c: use idr_alloc_cyclic() for ipc allocations A

Re: [PATCH 0/5] x86/percpu semantics and fixes

On Fri, Mar 08, 2019 at 09:56:37PM +0100, Peter Zijlstra wrote: > Anyway, can anybody explain percpu_stable_op() vs percpu_from_op() ? > > I'm thinking of a variant of Linus' patch, but I'm confused about the > above. So whatever I tried with +m only made things worse and always affects

Re: [PATCH] mmc_spi: add a status check for spi_sync_locked

Hi Kangjie, Thank you for the patch. On Sun, Mar 10, 2019 at 01:53:05AM -0600, Kangjie Lu wrote: > In case spi_sync_locked fails, the fix reports the error and > returns the error code upstream. > > Signed-off-by: Kangjie Lu > --- > drivers/mmc/host/mmc_spi.c | 4 > 1 file changed, 4

Re: [PATCH 18/20] objtool: Add UACCESS validation

On Fri, Mar 08, 2019 at 03:02:09PM -0600, Josh Poimboeuf wrote: > These gotos make my head spin. Again I would much prefer a small amount > of code duplication over this. something like so then? --- a/tools/objtool/check.c +++ b/tools/objtool/check.c @@ -1888,6 +1888,23 @@ static inline const

Re: [PATCH 19/20] objtool: uaccess PUSHF/POPF support

On Fri, Mar 08, 2019 at 03:11:22PM -0600, Josh Poimboeuf wrote: > On Thu, Mar 07, 2019 at 12:45:30PM +0100, Peter Zijlstra wrote: > > Add PUSHF / POPF state.uaccess restore logic. > > > > XXX: should possibly be merged with the previous patch such that KASAN > > doesn't explode in between. Split

Re: [PATCH 20/20] objtool: Add Direction Flag validation

On Fri, Mar 08, 2019 at 03:56:02PM -0600, Josh Poimboeuf wrote: > On Fri, Mar 08, 2019 at 10:33:43PM +0100, Peter Zijlstra wrote: > > On Fri, Mar 08, 2019 at 03:16:03PM -0600, Josh Poimboeuf wrote: > > > Can you elaborate on why (in the patch description)? Did this actually > > > find any

Re: [PATCH 00/20] objtool: UACCESS validation v3

On Thu, Mar 07, 2019 at 01:18:41PM -0500, Steven Rostedt wrote: > On Thu, 7 Mar 2019 09:45:35 -0800 > Linus Torvalds wrote: > > > On Thu, Mar 7, 2019 at 9:38 AM Peter Zijlstra wrote: > > > > > > Also; it seems to me that something PT, or maybe even simply: > > > > > > perf -e branches -e

Re: [PATCH 05/20] x86/uaccess/xen: Suppress SMAP warnings

On Fri, Mar 08, 2019 at 01:03:34PM -0600, Josh Poimboeuf wrote: > On Fri, Mar 08, 2019 at 01:00:38PM -0600, Josh Poimboeuf wrote: > > On Thu, Mar 07, 2019 at 12:45:16PM +0100, Peter Zijlstra wrote: > > > XXX: arguably we should rename ANNOTATE_NOSPEC_ALTERNATIVE to > > >

Re: [PATCH 03/20] x86/uaccess: Move copy_user_handle_tail into asm

On Fri, Mar 08, 2019 at 01:53:02PM -0600, Josh Poimboeuf wrote: > On Fri, Mar 08, 2019 at 08:48:35PM +0100, Peter Zijlstra wrote: > > On Fri, Mar 08, 2019 at 12:53:21PM -0600, Josh Poimboeuf wrote: > > > On Thu, Mar 07, 2019 at 12:45:14PM +0100, Peter Zijlstra wrote: > > > > /* > > > > + * Try to

[PATCH] Drop -Wdeclaration-after-statement

Newly added static_assert() is formally a declaration, which will give a warning if used in the middle of the function. Signed-off-by: Alexey Dobriyan --- Makefile |3 --- 1 file changed, 3 deletions(-) --- a/Makefile +++ b/Makefile @@ -792,9 +792,6 @@ endif # arch Makefile may override

Re: [PATCH] net: can: Increase tx queue length

On 09. 03. 19 15:40, Appana Durga Kedareswara Rao wrote: > Hi Andre, > > >> >> On 3/9/19 3:07 PM, Appana Durga Kedareswara rao wrote: >>> While stress testing the CAN interface on xilinx axi can in loopback >>> mode getting message "write: no buffer space available" >>> Increasing device tx

Re: r8169 only works in promisc mode

On Sat, 9 Mar 2019 10:33:40 +0100 Heiner Kallweit wrote: > On 09.03.2019 03:16, Alex Xu (Hello71) wrote: > > After suspending, my r8169 (not actually 8169, just that driver) only > > receives packets when in promiscuous mode. I have tried disabling all > > offload features except highdma

Re: r8169 only works in promisc mode

On 10.03.2019 15:18, Stephen Hemminger wrote: > On Sat, 9 Mar 2019 10:33:40 +0100 > Heiner Kallweit wrote: > >> On 09.03.2019 03:16, Alex Xu (Hello71) wrote: >>> After suspending, my r8169 (not actually 8169, just that driver) only >>> receives packets when in promiscuous mode. I have tried

Re: KASAN: use-after-free Read in x25_device_event

syzbot has found a reproducer for the following crash on: HEAD commit:d9862cfb Merge tag 'mips_5.1' of git://git.kernel.org/pub/.. git tree: net-next console output: https://syzkaller.appspot.com/x/log.txt?x=1531cf2320 kernel config:

[PATCH] regulator: palmas: Remove *rdev[PALMAS_NUM_REGS] from struct palmas_pmic

This driver is using devm_regulator_register() so it is not necessary to save *rdev for clean up. Actually the pmic->rdev[id] is not used now. Signed-off-by: Axel Lin --- drivers/regulator/palmas-regulator.c | 12 include/linux/mfd/palmas.h | 1 - 2 files changed, 13

[PATCH v2] ARM: dts: rockchip: remove disable-wp from rv1108-elgin-r1 emmc node

The mmc.txt didn't explicitly say disable-wp is for SD card slot only, but that is what it was designed for in the first place. Remove all disable-wp from emmc or sdio controllers. Signed-off-by: Johan Jonker Reviewed-by: Shawn Lin --- arch/arm/boot/dts/rv1108-elgin-r1.dts | 1 - 1 file

[PATCHv6 0/5] perf record: Add support to store data in directory

hi, this patchset adds the --dir option to record command (and all the other record command that overload cmd_record) that allows the data to be stored in directory with multiple data files. It's next step for multiple threads implementation in record. It's now possible to make directory data via

[PATCH 1/5] perf session: Add __perf_session__process_dir_events function

Adding __perf_session__process_dir_events function to process events over the directory data. All directory events are pushed into sessions ordered data and flushed for processing. Link: http://lkml.kernel.org/n/tip-n3zl0wo3z18tatv5x7epm...@git.kernel.org Signed-off-by: Jiri Olsa ---

[PATCH 4/5] perf record: Add --output-dir option to store data in directory

Adding --output-dir option to mimic -o and --dir options. following commands do the same: $ perf record -o perf.dir.data --dir ... $ perf record --output-dir perf.dir.data ... User cannot use both -o and output-dir together, error is displayed. Link:

[PATCH 2/5] perf session: Add path to reader object

Adding path to reader object, so we can display file the processing fails for (string in [] brackets). $ perf report --stdio 0x5e0 [perf.data/data.3] [0xa200]: failed to process type: -1577027574 Link: http://lkml.kernel.org/n/tip-4bjnoy4sln7adqtd3505q...@git.kernel.org Signed-off-by: Jiri

[PATCH 5/5] perf record: Describe perf.data directory format

Adding perf.data-directory-format.txt to describe the directory data layout. Link: http://lkml.kernel.org/n/tip-1c8u1thx63v2ldwfdas4x...@git.kernel.org Signed-off-by: Jiri Olsa --- .../perf.data-directory-format.txt| 54 +++ 1 file changed, 54 insertions(+) create

[PATCH 3/5] perf record: Add --dir option to store data in directory

Adding --dir option to store data in directory. It's next step for multiple threads in record. It's now possible to make directory data via --dir option, like: $ perf record --dir perf bench sched messaging $ ls -l perf.data total 344 -rw---. 1 jolsa jolsa 43864 Jan 20 22:26 data.0

[GIT PULL REQUEST] watchdog - v5.1 Merge window

Hi Linus, Please pull the watchdog changes for the v4.21 release cycle. This series contains: * A new watchdog driver for the Mellanox systems * renesas-wdt: Document r8a77470 support * numerous Mark expected switch fall-throughs * qcom: Add suspend/resume support * some small fixes and

Re: [PATCH] drm/vkms: fix use-after-free when drm_gem_handle_create() fails

On 03/05, Dmitry Vyukov wrote: > On Tue, Mar 5, 2019 at 12:23 AM Rodrigo Siqueira > wrote: > > > > On 02/28, Dmitry Vyukov wrote: > > > On Thu, Feb 28, 2019 at 12:12 AM Rodrigo Siqueira > > > wrote: > > > > > > > > On 02/26, Eric Biggers wrote: > > > > > From: Eric Biggers > > > > > > > > > >

[PATCH] fs: file: fixed a long comment style issue.

Fixed a long comment style issue. Signed-off-by: Youngjun Park --- fs/file.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/fs/file.c b/fs/file.c index 7ffd6e9d103d..1d2ae917424d 100644 --- a/fs/file.c +++ b/fs/file.c @@ -154,7 +154,8 @@ static int expand_fdtable(struct

Re: [PATCH v5 07/10] perf record: implement -z,--compression_level=n option and compression

On 08.03.2019 13:46, Jiri Olsa wrote: > On Thu, Mar 07, 2019 at 06:26:47PM +0300, Alexey Budankov wrote: >> >> On 07.03.2019 15:14, Jiri Olsa wrote: >>> On Thu, Mar 07, 2019 at 11:39:46AM +0300, Alexey Budankov wrote: On 05.03.2019 15:25, Jiri Olsa wrote: > On Fri, Mar 01, 2019 at

[PATCH] kconfig: fix 'Save As' menu of xconfig

The 'Save As' menu of xconfig is not working; it always saves the kernel configuration into the default file irrespective of the file chosen in the dialog box. The 'Save' menu always writes into the default file, but it would make more sense to write into the file previously chosen by 'Load' or

Re: [PATCH v5 07/10] perf record: implement -z,--compression_level=n option and compression

On 08.03.2019 13:46, Jiri Olsa wrote: > On Thu, Mar 07, 2019 at 06:26:47PM +0300, Alexey Budankov wrote: >> >> On 07.03.2019 15:14, Jiri Olsa wrote: >>> On Thu, Mar 07, 2019 at 11:39:46AM +0300, Alexey Budankov wrote: On 05.03.2019 15:25, Jiri Olsa wrote: > On Fri, Mar 01, 2019 at

[PATCH 04/10] x86, olpc: Use a correct version when making up a battery node

The XO-1 and XO-1.5 batteries apparently differ in an ability to report ambient temperature. We need to use a different compatible string for the XO-1.5 battery. Previously olpc_dt_fixup() used the presence od the battery node's compatible property to decide whether the DT is up to date. Now we

[PATCH 00/10] Add support for XO 1.75 to OLPC battery driver

Hello! This patch set modifies the OLPC battery driver so that it could eventually be used on an Arm-based OLPC XO 1.75 machine. Compared to the previous version, it splits the x86 platform patch into three so that it's hopefully easier to review. Patch 10/10 ("power: supply: olpc_battery: Have

[PATCH 02/10] x86, olpc: Don't split string literals when fixing up the DT

It was pointed out in a review, and checkpatch.pl complains about this. Breaking it down into multiple ofw evaluations works just as well, and perhaps even reads better. Signed-off-by: Lubomir Rintel --- Changes since v5: - This patch was split off from "x86, olpc: Use a correct version when

[PATCH 01/10] dt-bindings: olpc_battery: Add XO-1.5 battery

The XO-1 and XO-1.5 batteries apparently differ in an ability to report ambient temperature. Signed-off-by: Lubomir Rintel Reviewed-by: Rob Herring Acked-by: Pavel Machek Reviewed-by: Sebastian Reichel --- Changes since v1: - Collected Reviewed-by and Acked-by tags

[PATCH 07/10] power: supply: olpc_battery: Use devm_power_supply_register()

This simplifies the error handling. Signed-off-by: Lubomir Rintel Reviewed-by: Sebastian Reichel --- Changes since v1: - This was split off the "power: supply: olpc_battery: Move priv data to a struct" patch. drivers/power/supply/olpc_battery.c | 19 +-- 1 file changed, 5

[PATCH 05/10] power: supply: olpc_battery: Use DT to get battery version

Avoid using the x86 OLPC platform specific call to get the board version. That wouldn't work on FDT-based ARM MMP2 platform. Add the XO 1.5 compatible string too. This is actually not completely necessary as the battery nodes on XO 1.5 claim to be compatible with "olpc,xo1-battery", but there

[PATCH 03/10] x86, olpc: Trivial code move in DT fixup

This makes the following patch more concise. Signed-off-by: Lubomir Rintel --- Changes since v5: - This patch was split off from "x86, olpc: Use a correct version when making up a battery node" arch/x86/platform/olpc/olpc_dt.c | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-)

[PATCH 08/10] power: supply: olpc_battery: Avoid using platform_info

This wouldn't work on the DT-based ARM platform. Let's read the EC version directly from the EC driver instead. This removes x86 specific bits that would prevent this driver from being used with the EC of ARM-based OLPC XO 1.75. Signed-off-by: Lubomir Rintel Acked-by: Pavel Machek Reviewed-by:

[PATCH 09/10] power: supply: olpc_battery: Add OLPC XO 1.75 support

The battery and the protocol are essentially the same as OLPC XO 1.5, but the responses from the EC are LSB first. Signed-off-by: Lubomir Rintel Acked-by: Pavel Machek --- Changes since v5: - s/int little_endian/bool little_endian/ Changes since v2: - Fix the version conditional Changes

[PATCH 10/10] power: supply: olpc_battery: Have the framework register sysfs files for us

The power framework gained ability to register groups of sysfs attributes in commit cef8fe6a382c ("power: supply: core: add support for custom sysfs attributes"). Signed-off-by: Lubomir Rintel Suggested-by: Sebastian Reichel --- Changes since v5: - Added this patch

[PATCH 06/10] power: supply: olpc_battery: Move priv data to a struct

The global variables for private data are not too nice. I'd like some more, and that would clutter the global name space even further. Signed-off-by: Lubomir Rintel Reviewed-by: Andy Shevchenko --- Changes since v4: - Bring some more code that was misplaced here. Changes since v2: - Bring the

Re: [PATCH] clk: rockchip: fix wrong clock definitions for rk3328

On 3/10/2019 8:00 AM, Jonas Karlman wrote: This patch fixes definition of several clock gate and select register that is wrong for rk3328 referring to the TRM and vendor kernel. Also use correct number of softrst registers. Fix clock definition for: - clk_crypto - aclk_h265 - pclk_h265 -

PROBLEM: kernel build fails with CONFIG_BPFILTER_UMH=y

hallo care to look into this: https://bugzilla.kernel.org/show_bug.cgi?id=202681 -- bis neulich... ;-) Ronald

Re: PROBLEM: kernel build fails with CONFIG_BPFILTER_UMH=y

[add other mailing lists] On 3/10/19 9:47 AM, rwar...@gmx.de wrote: > hallo > > care to look into this: > > https://bugzilla.kernel.org/show_bug.cgi?id=202681 > > -- ~Randy

[PATCH v1 2/6] lib: scanf: handle integer overflows in vsscanf

Traditional scanf implementations ignore integer overflows because C language standard allows here undefined behavior (§7.21.6.2 #10). So, sane and safe behavior wouldn't harm anything. This patch carefully checks integer overflows and stops matching if result does not fit into appropriate type

[PATCH v1 0/6] Make sscanf safer

Standard sscanf isn't well designed for input validation: * no way to detect interger overflow * unmached tail text is ignored * no mandatory buffer overflow checks All these problems were found in the wild in cgroup interfaces: https://patchwork.kernel.org/patch/10831387/

[PATCH v1 3/6] lib: scanf: add vsscanf feature for matching end of text

Traditional sscanf ignores trailing unmatched characters, because it derives from design of streaming fscanf(). Without extra care this leads to confusing parsing results: "%d" successfully parses "0x1" as 0 and "1M" as 1. Silent ignore of trailing input also could hide bugs and unexpectedly

[PATCH v1 1/6] lib: scanf: document features of scanf format string

Kernel implementation of vsscanf() has some limitations. Signed-off-by: Konstantin Khlebnikov --- lib/vsprintf.c | 28 1 file changed, 28 insertions(+) diff --git a/lib/vsprintf.c b/lib/vsprintf.c index 791b6fa36905..276a0bc3b019 100644 --- a/lib/vsprintf.c +++

[PATCH v1 5/6] lib: scanf: mark sscanf and vsscanf as __must_check

Caller must check returned count of matched arguments. Signed-off-by: Konstantin Khlebnikov --- include/linux/kernel.h |4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/include/linux/kernel.h b/include/linux/kernel.h index 32726b25eaa5..3142a456f00b 100644 ---

[PATCH v1 4/6] lib: scanf: handle character ranges in %[...]

Complete implementation isn't much bigger than present one. This patch adds missing standard features: %[a-z] - matches 'a'..'z' %[][] - matches '[' and ']' (']' must be first) %[_-] - matches '_' and '-' ('-' must be last) Signed-off-by: Konstantin Khlebnikov --- lib/vsprintf.c |

[PATCH v1 6/6] lib: scanf: add test module

Module is under config option CONFIG_TEST_SCANF. This is just basic cases, complete coverage isn't that easy for such complicated function. Signed-off-by: Konstantin Khlebnikov --- lib/Kconfig.debug |3 + lib/Makefile |1 lib/test_scanf.c | 252

Re: [GIT PULL] arm64 updates for 5.1-rc1

On Sun, Mar 10, 2019 at 3:24 AM Catalin Marinas wrote: > > Were there any issues with this pull request or you haven't got around > to merging it yet? All good, just hadn't gotten around to it yet. Your pull request hadn't come in when I did the first round of architecture updates, so then it

Re: [PATCH] net: can: Increase tx queue length

Hi all, On 3/10/19 6:07 AM, Dave Taht wrote: Toke Høiland-Jørgensen writes: Appana Durga Kedareswara Rao writes: Hi Andre, On 3/9/19 3:07 PM, Appana Durga Kedareswara rao wrote: While stress testing the CAN interface on xilinx axi can in loopback mode getting message "write: no

[PATCH v3 0/7] move out of staging

This series of patches make code style adjusts on comments and include order. It adds a SPDX license identifier of GPL-2.0. It makes Kconfig help message more compact and correct. It adds an ABI documentation for the device attributes. It changes device attributes to use more suitable ABI

[PATCH v3 2/7] staging: iio: ad5933: organize includes

Organize includes to list them in lexicographic order. Signed-off-by: Marcelo Schmitt --- .../staging/iio/impedance-analyzer/ad5933.c| 18 +- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/drivers/staging/iio/impedance-analyzer/ad5933.c

[PATCH v3 3/7] staging: iio: ad5933: add SPDX identifier

Add SPDX identifier of GPL-2.0 for the ad5933 driver. Signed-off-by: Marcelo Schmitt --- drivers/staging/iio/impedance-analyzer/ad5933.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/drivers/staging/iio/impedance-analyzer/ad5933.c

[PATCH v3 1/7] staging: iio: ad5933: change multi-line comment style

Make multi-line comments compliant with the preferred code style. Signed-off-by: Marcelo Schmitt --- drivers/staging/iio/impedance-analyzer/ad5933.c | 9 ++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/drivers/staging/iio/impedance-analyzer/ad5933.c

[PATCH v3 5/7] staging: iio: ad5933: add ABI documentation

Add an ABI documentation for the ad5933 driver. Signed-off-by: Marcelo Schmitt --- .../ABI/testing/sysfs-bus-iio-ad5933 | 39 +++ 1 file changed, 39 insertions(+) create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-ad5933 diff --git

[PATCH v3 4/7] staging: iio: ad5933: change help rule message

Remove the previous comment about direct access via sysfs which would lead one think ad5933 driver has limitations it actually doesn't. Signed-off-by: Marcelo Schmitt --- drivers/staging/iio/impedance-analyzer/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH v3 7/7] staging: iio: ad5933: move out of staging

Move ad5933 impedance-analyzer driver from staging to mainline. The ad5933 is a high precision impedance converter system solution that combines an on-board frequency generator with an analog-to-digital converter (ADC). This driver was designed to be compatible with both ad5933 and ad5934 chips.

[PATCH v3 6/7] staging: iio: ad5933: change attributes' ABI call

Change device attributes to use more suitable ABI functions when setting and displaying AC output excitation voltage. It better complies with device hardware since these attributes are used to manage DDS peak-to-peak output voltage. Signed-off-by: Marcelo Schmitt ---

Re: [PATCH v2 4/5] selftests/ima: kexec_file_load syscall test

On Thu, 2019-02-28 at 23:00 +0100, Petr Vorel wrote: > > + local keypair1="$2" > > + local keypair2="$3" > > + > > + mount_securityfs > > + > > + local ima_policy=$SECURITYFS/ima/policy > > + if [ ! -e $ima_policy ]; then > > + log_fail "$ima_policy not found" > > + fi > > +

Re: [PATCH v6 04/17] media: rkisp1: add Rockchip MIPI Synopsys DPHY driver

Hi Jacob, A few more comments on the code this time. First of all, this has bit-rotten a bit and doesn't compile. The following patch fixes it. Feel free to squash it into this patch (no need to credit me or add my SoB line). commit 297399bb5e3ac8d50f27f1c911fe7e5f26983e56 Author: Laurent

Re: [PATCH v2 5/5] selftests/ima: loading kernel modules

On Thu, 2019-02-28 at 23:32 +0100, Petr Vorel wrote: > Hi Mimi, > > > While the appended kernel module signature can be verified, when loading > > a kernel module via either the init_module or the finit_module syscall, > > verifying the IMA signature requires access to the file descriptor, > >

Re: [PATCH] isdn: hfcpci: fix potential NULL pointer dereference

From: Kangjie Lu Date: Fri, 8 Mar 2019 23:46:04 -0600 > In case ioremap fails, the fix reports an error and returns. > > Signed-off-by: Kangjie Lu First, you shouldn't print the information log message if this fails. Second you are leaking hc->hw.fifos, you have to clean up any resources

  1   2   3   >