Re: [PATCH v2 4/5] iio: dac: stm32: add support for trigger events

On 06/04/17 17:11, Fabrice Gasnier wrote: > STM32 DAC supports triggers to synchronize conversions. When trigger > occurs, data is transferred from DHR (data holding register) to DOR > (data output register) so output voltage is updated. > Both hardware and software triggers are supported. > >

Re: ia64: fix module loading for gcc-5.4

>>> That caused ia64 module loader to choke >>> on such instructions: >>> fuse: invalid slot number 1 for IMM64 >> >> Why does it matter to check such a value? > > I'm not sure I follow the question. Is your question about > linux kernel relocation code handler, gcc or ia64 instruction

Re: [PATCH] net: netfilter: Replace explicit NULL comparisons

2017-04-09 16:26 GMT+08:00 Jan Engelhardt : > > On Sunday 2017-04-09 05:42, Arushi Singhal wrote: >>On Sun, Apr 9, 2017 at 1:44 AM, Pablo Neira Ayuso wrote: >> On Sat, Apr 08, 2017 at 08:21:56PM +0200, Jan Engelhardt wrote: >> > On Saturday

Re: [PATCH v2] fault-inject: support systematic fault injection

2017-04-09 2:40 GMT+09:00 Dmitry Vyukov : > On Fri, Apr 7, 2017 at 6:47 PM, Akinobu Mita wrote: >> 2017-04-07 3:33 GMT+09:00 Michal Hocko : >>> [Let's add linux-api - please always cc this list when adding/modifying >>> user visible

Re: ia64: fix module loading for gcc-5.4

On Sun, 9 Apr 2017 11:02:43 +0200 SF Markus Elfring wrote: > >>> That caused ia64 module loader to choke > >>> on such instructions: > >>> fuse: invalid slot number 1 for IMM64 > >> > >> Why does it matter to check such a value? > > > > I'm not sure I

Re: [PATCH 1/9] IB/IPoIB: Use kcalloc() in two functions

Reviewed-by: Sagi Grimberg

Re: [PATCH 2/9] IB/IPoIB: Delete an error message for a failed memory allocation

Reviewed-by: Sagi Grimberg

Re: audit regressions in 4.11

On Sat, Apr 8, 2017 at 11:02 PM, Seth Forshee wrote: > I've observed audit regressions in 4.11-rc when not using a userspace > audit daemon. The most obvious issue is that audit messages are not > appearing in dmesg anymore. If a sufficient number of audit messages are

[PATCH 2/2] checkpatch: Improve MULTISTATEMENT_MACRO_USE_DO_WHILE test

The logic currrently misses macros that start with an if statement. e.g.:#define foo(bar) if (bar) baz; Add a test for macro content that starts with if Original-patch-by: Alfonso Lima Reported-by: Andreas Mohr Signed-off-by: Joe Perches

Re: [PATCH 2/2] checkpatch: Improve MULTISTATEMENT_MACRO_USE_DO_WHILE test

On Sun, 2017-04-09 at 10:45 -0700, Joe Perches wrote: > checkpatch Sorry, ignore this.

[PATCH 1/2] checkpatch: Clarify the EMBEDDED_FUNCTION_NAME message

Try to make the conversion of embedded function names to "%s: ", __func__ a bit clearer. Add a bit more information to the comment describing the test too. Signed-off-by: Joe Perches --- scripts/checkpatch.pl | 12 +++- 1 file changed, 7 insertions(+), 5 deletions(-)

Re: [RFC][PATCHv2 4/8] pm: switch to printk.emergency mode in unsafe places

On Thu, Apr 06, 2017 at 07:20:52PM +0200, Pavel Machek wrote: > On Wed 2017-03-29 18:25:07, Sergey Senozhatsky wrote: > > It's not always possible/safe to wake_up() printk kernel > > thread. For example, late suspend/early resume may printk() > > while timekeeping is not initialized yet, so

Re: crypto_memneq not backported to 3.10

Hi Jason, On Sun, Apr 09, 2017 at 02:59:53PM +0200, Jason A. Donenfeld wrote: > Hey Willy, > > Linux 3.10 is inexplicably missing crypto_memneq, making all crypto > mac comparisons use non constant-time comparisons. Bad news bears. > > 3.12 got these backported with >

[PATCH 2/2] hp-wmi: Fix detection for dock and tablet mode

From: Carlo Caione The current driver code is not checking for the error values returned by 'hp_wmi_dock_state()' and 'hp_wmi_tablet_state()' before passing the returned values down to 'input_report_switch()'. This error code is being translated to '1' in the input subsystem,

[PATCH 0/2] hp-wmi: Fix dock status and tablet mode reporting

From: Carlo Caione Several HP laptops cannot be put to sleep using the LID since systemd complains that the system is docked even though the laptop is not even dockable (see [1]). This is due to a bug in hp-wmi where the driver is failing to check for errors before creating

[PATCH 1/2] hp-wmi: Fix error value for hp_wmi_tablet_state

From: Carlo Caione hp_wmi_tablet_state() fails to return the correct error code when hp_wmi_perform_query() returns the HP WMI query specific error code that is a positive value. Signed-off-by: Carlo Caione --- drivers/platform/x86/hp-wmi.c | 2 +- 1

[PATCH 3/3] iscsi-target: Improve size determinations in four functions

From: Markus Elfring Date: Sun, 9 Apr 2017 16:00:39 +0200 Replace the specification of four data structures by pointer dereferences as the parameter for the operator "sizeof" to make the corresponding size determinations a bit safer according to the Linux coding

[PATCH v5] dt-bindings: fpga: Add bindings document for Xilinx LogiCore PR Decoupler

This adds the binding documentation for the Xilinx LogiCORE PR Decoupler soft core. Signed-off-by: Moritz Fischer Signed-off-by: Michal Simek Acked-by: Alan Tull Cc: Sören Brinkmann Cc:

Re: Linux 4.11: Reported regressions as of Sunday, 2017-04-09

On Sun, Apr 09, 2017 at 07:15:49PM +0200, Thorsten Leemhuis wrote: > Desc: i915 gpu hangs under load > Repo: 2017-03-22 > https://www.mail-archive.com/intel-gfx@lists.freedesktop.org/msg116227.html > https://bugs.freedesktop.org/show_bug.cgi?id=100181 >

Re: [PATCH v3 1/1] perf tools: fix perf build with ARCH=x86_64

On Tue, Apr 04, 2017 at 11:25:44PM -0700, jiada_w...@mentor.com wrote: > From: Jiada Wang > > with commit: 0a943cb10ce78 (tools build: Add HOSTARCH Makefile variable) > the following build failure is seen when build with ARCH=x86_64 is that described somewhere as a valid

Re: [PATCH v2 2/5] iio: dac: add support for stm32 DAC

On 06/04/17 17:11, Fabrice Gasnier wrote: > Add support for STMicroelectronics STM32 DAC. It's a 12-bit, voltage > output digital-to-analog converter. It has two output channels, each > with its own converter. > It supports 8 bits or 12bits left/right aligned data format. Only > 12bits

[PATCH RFC v2 1/3] LSM: Allow per LSM module per "struct task_struct" blob.

From: Tetsuo Handa Since several modules are planning to use per "struct task_struct" blob, we need a layer for isolating it. Therefore, this patch introduces per LSM module per "struct task_struct" blob. It would be possible to remember location in

[PATCH RFC v2 2/3] security: add the ModAutoRestrict Linux Security Module

This adds the ModAutoRestrict Linux Security Module. The new module is a stackable LSM that has been tested with Yama and SELinux, all the three modules running. The module applies restrictions on automatic module loading operations. If it is selected, every request to use a kernel feature that

[PATCH RFC v2 0/3] security: Add ModAutoRestrict LSM

Hi List, This is RFC v2 of the Module auto-loading restriction feature. The module has been renamed ModAutoRestrict LSM. This RFC is a work in progress update. There are still minor things to fix which are listed in the TODO section. Also I used Tetsuo approach of stacking task->security, since

[PATCH RFC v2 3/3] Documentation: add ModAutoRestrict LSM documentation

Cc: Andy Lutomirski Cc: James Morris Cc: Tetsuo Handa Cc: Kees Cook Signed-off-by: Djalal Harouni --- Documentation/security/00-INDEX| 2 +

crypto_memneq not backported to 3.10

Hey Willy, Linux 3.10 is inexplicably missing crypto_memneq, making all crypto mac comparisons use non constant-time comparisons. Bad news bears. 3.12 got these backported with d68e944a8fcb2c6212b38064771c9f5af7b0b92c, afe5a791d374e50a06ada7f4eda4e921e1b77996, and possibly others. I'd suggest

[PATCHv2] x86/intel_rdt: Add cpus_list rdtgroup file

On Fri, Mar 31, 2017 at 05:55:12PM +0200, Jiri Olsa wrote: > On Fri, Mar 31, 2017 at 11:15:22AM +0200, Thomas Gleixner wrote: > > On Wed, 29 Mar 2017, Fenghua Yu wrote: > > > > static int rdtgroup_cpus_show(struct kernfs_open_file *of, > > > > - struct seq_file *s,

Re: [PATCHv2] x86/intel_rdt: Add cpus_list rdtgroup file

On Sun, Apr 09, 2017 at 06:49:29PM +0200, Jiri Olsa wrote: > On Fri, Mar 31, 2017 at 05:55:12PM +0200, Jiri Olsa wrote: > > On Fri, Mar 31, 2017 at 11:15:22AM +0200, Thomas Gleixner wrote: > > > On Wed, 29 Mar 2017, Fenghua Yu wrote: > > > > > static int rdtgroup_cpus_show(struct kernfs_open_file

Re: [PATCH v2 5/5] iio: dac: stm32: add support for waveform generator

On 06/04/17 17:11, Fabrice Gasnier wrote: > STM32 DAC has built-in noise or triangle waveform generator. > - "wavetype" extended attribute selects noise or triangle. > - "amplitude" extended attribute selects amplitude for waveform generator > > A DC offset can be added to waveform generator

Re: [PATCH] irqchip/atmel-aic5: handle suspend to RAM

On Thu, 6 Apr 2017 18:17:53 +0200 Alexandre Belloni wrote: > On sama5d2, VDD core may be cut while suspending to RAM. This means the > AIC5 registers content is lost. Restore it at resume time. > > Signed-off-by: Alexandre Belloni

Re: [PATCH 1/2] leds: Add driver for Qualcomm LPG

Hi, On 04/08/2017 03:39 PM, Pavel Machek wrote: > Hi! > >> [..] For the patterns I don't know how a trigger for this would look like, how would setting the pattern of a trigger be propagated down to the hardware? >>> >>> We'd need a new op and API similar to

Re: [PATCH v2] Extend pca9532 device tree support

Hello Jacek, On 09.04.2017 14:37, Jacek Anaszewski wrote: > Hello Felix, > > On 04/07/2017 10:22 AM, Felix Brack wrote: >> Hello Jacek, >> >> On 06.04.2017 21:00, Jacek Anaszewski wrote: >>> Hi Pavel, >>> >>> On 04/06/2017 05:50 PM, Pavel Machek wrote: Hi! >> diff --git

[PATCH] x86/irq: Do not check available vectors if current CPU has no irq to migrate

This is an optimization to bypass the free vector checking if the current CPU has no irq to migrate. This can especially speed up the CPU offline process when there are many CPUs in the system. Cc: Thomas Gleixner Cc: Ingo Molnar Cc: "H. Peter Anvin"

[PATCH 1/3] iscsi-target: Use kcalloc() in iscsit_allocate_iovecs()

From: Markus Elfring Date: Sun, 9 Apr 2017 15:06:00 +0200 * A multiplication for the size determination of a memory allocation indicated that an array data structure should be processed. Thus use the corresponding function "kcalloc". This issue was detected

Re: audit regressions in 4.11

On Sun, Apr 9, 2017 at 10:40 AM, Seth Forshee wrote: > On Sun, Apr 09, 2017 at 09:14:03AM -0400, Paul Moore wrote: >> On Sat, Apr 8, 2017 at 11:02 PM, Seth Forshee >> wrote: >> > I've observed audit regressions in 4.11-rc when not using a

Re: [PATCH] Staging: comedidev.h comedi_lrange should be const struct

/Staging-comedidev-h-comedi_lrange-should-be-const-struct/20170409-224503 config: x86_64-allyesdebian (attached as .config) compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901 reproduce: # save the attached .config to linux build tree make ARCH=x86_64 All warnings (new ones prefixed

Linux 4.11: Reported regressions as of Sunday, 2017-04-09

Hi! Find below my third regression report for Linux 4.11. It lists 15 regressions I'm currently aware of. 5 regressions mentioned in last weeks report got fixed. As always: Are you aware of any other regressions? Then please let me know (simply CC regressi...@leemhuis.info). And please tell me if

Re: [PATCH v3] ia64: fix module loading for gcc-5.4

> Starting from gcc-5.4+ gcc generates MLX How do you think about to omit the plus character? > instructions in more cases to refer local > symbols: I wonder about your choice of a line length limit here. > That caused ia64 module loader to choke > on such instructions: > fuse: invalid

Re: [patch 0/7] staging: speakup: introduce tty-based comms

Hi, Any updates on this? We can start working in tty_port_register_serdev_device() if that's okay? Thanks, Okash On Wed, Mar 22, 2017 at 01:05:24AM +0100, Samuel Thibault wrote: > Hello, > > So Rob, how do you see this going? Shall we introduce a serdev_device >

[PATCH] tty:tty_ldisc: add tty_ldisc_lock|unlock to prevent concurrent update to ldisc in tty_ldisc_reinit

This patch could fix the issue that tty_reopen in tty_io calling tty_ldisc_reinit without holding tty->ldisc_sem. Signed-off-by: Wang YanQing --- drivers/tty/tty_ldisc.c | 23 --- 1 file changed, 12 insertions(+), 11 deletions(-) diff --git

Re: [PATCH v3] lightnvm: physical block device (pblk) target

Hi Bart, Thanks for reviewing the code. > On 8 Apr 2017, at 22.56, Bart Van Assche wrote: > > On 04/07/17 11:50, Javier González wrote: >> Documentation/lightnvm/pblk.txt | 21 + >> drivers/lightnvm/Kconfig | 19 + >> drivers/lightnvm/Makefile|

Re: [printk] fbc14616f4: BUG:kernel_reboot-without-warning_in_test_stage

On Fri 2017-04-07 10:29:17, Steven Rostedt wrote: > On Fri, 7 Apr 2017 10:14:49 +0200 > Pavel Machek wrote: > > > > serial console can be quite slow. and port->lock, that is acquired by > > > console_unlock()->call_console_drivers()->write(), is also accessible > > > by serial

Re: [printk] fbc14616f4: BUG:kernel_reboot-without-warning_in_test_stage

On Sat 2017-04-08 00:13:06, Sergey Senozhatsky wrote: > On (04/07/17 14:44), Pavel Machek wrote: > [..] > > > [..] > > > > I believe "spend at most 2 seconds in printk(), then print a warning > > > > and offload" is a solution closer to what we had before. > > > > > > a warning here can be very

Re: [kernel-hardening] Re: [RFC v2][PATCH 04/11] x86: Implement __arch_rare_write_begin/unmap()

* Andy Lutomirski wrote: > On Sat, Apr 8, 2017 at 12:33 AM, Daniel Micay wrote: > > The > > submitted code is aimed at rare writes to globals, but this feature is > > more than that and design decisions shouldn't be based on just the > > short term. > >

Re: [PATCH 15/24] asus-wmi: Restrict debugfs interface when the kernel is locked down

On Fri, Apr 7, 2017 at 3:50 PM, David Howells wrote: > Andy Shevchenko wrote: > >> > From: Matthew Garrett >> > >> > We have no way of validating what all of the Asus WMI methods do on a given >> > machine - and there's

Re: [PATCH 4/9] IB/IPoIB: Delete unwanted spaces behind usages of the sizeof operator

Reviewed-by: Sagi Grimberg

Re: [PATCH 3/9] IB/IPoIB: Enclose six expressions for the sizeof operator by parentheses

Reviewed-by: Sagi Grimberg

Re: [PATCH v2] Extend pca9532 device tree support

Hello Felix, On 04/07/2017 10:22 AM, Felix Brack wrote: > Hello Jacek, > > On 06.04.2017 21:00, Jacek Anaszewski wrote: >> Hi Pavel, >> >> On 04/06/2017 05:50 PM, Pavel Machek wrote: >>> Hi! >>> > diff --git a/Documentation/devicetree/bindings/leds/leds-pca9532.txt >

[PATCH] Staging: comedidev.h comedi_lrange should be const struct

According to checkpatch.pl, comedi_lrange should be declared as `const struct` instead of `struct` in driver/staging/comedidev.h Signed-off-by: Arthur Brainville (Ybalrid) --- drivers/staging/comedi/comedidev.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff

Re: [PATCH v3 14/37] mtd: nand: denali: support "nand-ecc-strength" DT property

On Mon, 3 Apr 2017 12:16:34 +0900 Masahiro Yamada wrote: > Hi Boris, > > > > 2017-03-31 18:46 GMT+09:00 Boris Brezillon > : > > > You can try something like that when no explicit ecc.strength and > > ecc.size has been set in

[PATCH] tty:tty_ldisc: add tty_ldisc_lock|unlock to prevent concurrent update to ldisc in tty_ldisc_deinit

This patch could fix the issue that free_tty_struct in tty_io calling tty_ldisc_deinit without holding tty->ldisc_sem. Signed-off-by: Wang YanQing --- drivers/tty/tty_ldisc.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/tty/tty_ldisc.c

Re: [PATCH v3] ia64: fix module loading for gcc-5.4

On Sun, 9 Apr 2017 10:27:52 +0200 SF Markus Elfring wrote: > > That caused ia64 module loader to choke > > on such instructions: > > fuse: invalid slot number 1 for IMM64 > > Why does it matter to check such a value? I'm not sure I follow the question. Is

Re: [regression] Re: 4.11-rc0, thinkpad x220: GPU hang

On Mon 2017-03-06 12:23:41, Chris Wilson wrote: > On Mon, Mar 06, 2017 at 01:10:48PM +0100, Pavel Machek wrote: > > On Mon 2017-03-06 11:15:28, Chris Wilson wrote: > > > On Mon, Mar 06, 2017 at 12:01:51AM +0100, Pavel Machek wrote: > > > > Hi! > > > > > > > > > > mplayer stopped working after a

Re: [PATCH v3 33/37] mtd: nand: allocate aligned buffers if NAND_OWN_BUFFERS is unset

On Thu, 30 Mar 2017 17:15:04 +0900 Masahiro Yamada wrote: > Some NAND controllers are using DMA engine requiring a specific > buffer alignment. The core provides no guarantee on the nand_buffers > pointers, which forces some drivers to allocate their own buffers >

[PATCH 2/3] iscsi-target: Delete error messages for failed memory allocations

From: Markus Elfring Date: Sun, 9 Apr 2017 15:34:50 +0200 The script "checkpatch.pl" pointed information out like the following. WARNING: Possible unnecessary 'out of memory' message Thus remove such statements here. Link:

Re: audit regressions in 4.11

On Sun, Apr 09, 2017 at 09:14:03AM -0400, Paul Moore wrote: > On Sat, Apr 8, 2017 at 11:02 PM, Seth Forshee > wrote: > > I've observed audit regressions in 4.11-rc when not using a userspace > > audit daemon. The most obvious issue is that audit messages are not > >

[PATCH V2] checkpatch: Improve MULTISTATEMENT_MACRO_USE_DO_WHILE test

The logic currrently misses macros that start with an if statement. e.g.:#define foo(bar) if (bar) baz; Add a test for macro content that starts with if Original-patch-by: Alfonso Lima Reported-by: Andreas Mohr Signed-off-by: Joe Perches

Re: [PATCH v2 3/5] iio: trigger: add set_trigger callback to notify device

On 06/04/17 17:11, Fabrice Gasnier wrote: > Add 'set_trigger' callback to iio info structure. This allows device > to be notified when a trigger (or no trigger) has been assigned. This > maybe useful for instance in non buffered mode (e.g. event triggered). > This is called, after trigger and

Re: [PATCH 6/9] IB/iser: Use kmalloc_array() in iser_alloc_rx_descriptors()

Acked-by: Sagi Grimberg

Re: [bug report] checkpatch: if statement does not need to be enclosed in parentheses

On Sat, Apr 08, 2017 at 10:33:19AM -0700, Joe Perches wrote: > On Sat, 2017-04-08 at 17:07 +0100, Alfonso Lima wrote: > > Hi, > > > > In current linux-next, if you run the script on this piece of > > code: > > > > #define FOO(a) \ > > if (a) {

Re: [PATCH 7/9] IB/iser: Add spaces for better code readability

Acked-by: Sagi Grimberg

Re: [PATCH 9/9] IB/isert: Improve size determinations in three functions

Acked-by: Sagi Grimberg

Re: [PATCH 8/9] IB/isert: Use kcalloc() in isert_alloc_rx_descriptors()

Acked-by: Sagi Grimberg

patch to candidate for stable kernel 4.10

Dear stable kernel maintainers, Please consider commit f17f8a14e82cdf34cd6473e3644f3c672b3884f6 to be included into 4.10 kernel. As long as it crashes kernels used by some distors, we have to disable corresponding functionality on the NFS servers. Thanks in advance, Tigran.

[PATCH 2/2] x86/smp: Remove the redundant #ifdef CONFIG_SMP directive

According to: ... config X86_LOCAL_APIC def_bool y depends on X86_64 || SMP || X86_32_NON_STANDARD ... ... in arch/x86/Kconfig If X86_LOCAL_APIC is n, the SMP must be n. So, Remove the redundant #ifdef CONFIG_SMP directive in the case of !X86_LOCAL_APIC. Signed-off-by: Dou

[PATCH 1/2] x86/smp: Refine the code in the case of X86_32_SMP

Current code in CONFIG_X86_32_SMP is redundant. Merge the raw_smp_processor_id() macro and refine the #if directive. Signed-off-by: Dou Liyang --- BTW, what's the purpose of commit 96b89dc6598a ("x86: smp.h move safe_smp_processor_id declartion to cpu.h")? Reduce

Re: 8250: Possible race between console message vs DMA?

On Fri, Apr 7, 2017 at 2:08 PM, Vignesh R wrote: > Hi All, > > I seem to be hitting a race condition using 8250_dma (and 8250_omap > specific dma) support: > > Kernel writes log messages to console via > serial8250_console_write()->serial8250_console_putchar() which directly >

[PATCH v3 1/2] staging: vc04_services: bcm2835-audio: bcm2835-pcm.c Fixed checkpatch warning about unaligned function params

Fixed unaligned function parameters issues, as per checkpatch warning Signed-off-by: Andrea della Porta --- Changes in v3: - rebased on staging-testing .../vc04_services/bcm2835-audio/bcm2835-pcm.c | 43 ++ 1 file changed, 20 insertions(+), 23

[PATCH v3 0/2] staging: vc04_services: bcm2835-audio: bcm2835-pcm.c - Fixed several checkpatch issues

Andrea della Porta (2): staging: vc04_services: bcm2835-audio: bcm2835-pcm.c Fixed checkpatch warning about unaligned function params staging: vc04_services: bcm2835-audio: bcm2835-pcm.c Fixed codepatch coding style issue, line over 80 .../vc04_services/bcm2835-audio/bcm2835-pcm.c

[PATCH v3 2/2] staging: vc04_services: bcm2835-audio: bcm2835-pcm.c Fixed codepatch coding style issue, line over 80

Fixed checkpatch warning about line over 80 chars Signed-off-by: Andrea della Porta --- Changes in v3: - rebased on staging-testing drivers/staging/vc04_services/bcm2835-audio/bcm2835-pcm.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git

[PATCH 0/1] pwm: pca9685: fix gpio-only operation.

The solution to the bug presented here (always keep SLEEP cleared) works for me, but perhaps other users might want to set SLEEP at some point while the driver instance is still loaded ? If so, I'd love to hear feedback, so we can find a solution which works for all users. Sven Van Asbroeck (1):

[PATCH 1/1] pwm: pca9685: fix gpio-only operation.

gpio-only driver operation never clears the SLEEP bit, which can cause the gpios to become unusable. Example: 1. user requests first pwm -> driver clears SLEEP bit 2. user frees last pwm -> driver sets SLEEP bit 3. user requests gpio 4. user switches gpio on-> output does

Re: [PATCH v2] perf: fix double free at function perf_hpp__reset_output_field

On Wed, Apr 05, 2017 at 10:44:22AM +0800, Du, Changbin wrote: > On Tue, Apr 04, 2017 at 12:51:03PM -0300, Arnaldo Carvalho de Melo wrote: > > Em Wed, Apr 05, 2017 at 12:34:59AM +0900, Namhyung Kim escreveu: > > > Hi Arnaldo, > > > > > > On Wed, Apr 5, 2017 at 12:19 AM, Arnaldo Carvalho de Melo >

Re: [kernel-hardening] Re: [RFC v2][PATCH 04/11] x86: Implement __arch_rare_write_begin/unmap()

On 7 Apr 2017 at 21:58, Andy Lutomirski wrote: > On Fri, Apr 7, 2017 at 12:58 PM, PaX Team wrote: > > On 7 Apr 2017 at 9:14, Andy Lutomirski wrote: > >> Then someone who cares about performance can benchmark the CR0.WP > >> approach against it and try to argue that it's a

[PATCH] kconfig: Check for libncurses before menuconfig

From: Borislav Petkov There is a check and a nice user-friendly message when the curses library is not present on the system and the user wants to do "make menuconfig". It doesn't get issued, though. Instead, we fail the build when mconf.c doesn't find the curses.h header:

Re: USB Type-C Port Manager API concern

Hi Mats, On Sun, Apr 09, 2017 at 01:09:57AM +0200, Mats Karrman wrote: > Hi Guenter, > > From a previous thread: > > On 03/08/2017 02:38 AM, Guenter Roeck wrote: > >On 03/07/2017 02:30 PM, Mats Karrman wrote: > >[ ... ] > > > >> > >>I'm still struggling to catch up on what you guys have been up

Linux 4.11-rc6

Things are looking fairly normal, so here's the regular weekly rc. It's a bit bigger than rc5, but not alarmingly so, and nothing looks particularly worrisome. Knock wood. The only slightly unusual thing is how the patches are spread out, with almost equal parts of arch updates, drivers,

Re: [PATCH v2 1/2] arm64: dts: rk3399: add support for firefly-rk3399 board

Hi Heiko, On 04/08/2017 07:01 AM, Heiko Stuebner wrote: Hi Kever, Am Mittwoch, 5. April 2017, 17:33:19 CEST schrieb Kever Yang: Firefly-rk3399 is a bord from T-Firefly, you can find detail about it here: http://en.t-firefly.com/en/firenow/Firefly_RK3399/ This patch add basic node for the

[PATCH v3 0/2] drivers: serial: Aspeed VUART driver

This is v3 of a driver for the Aspeed VUART. This version addresses feedback from Andy and Greg, and includes Rob's ack for the bindings change. The VUART is a serial device on the BMC side of the LPC bus that connects a BMC to it's host processor. We add a flag to the serial core to allow the

[PATCH v3 1/2] serial: 8250: Add flag so drivers can avoid THRE probe

The probing of THRE irq behaviour assumes the other end will be reading bytes out of the buffer in order to probe the port at driver init. In some cases the other end cannot be relied upon to read these bytes, so provide a flag for them to skip this step. Bit 19 was chosen as the flags are a int

[PATCH v3 0/2] drivers: serial: Aspeed VUART driver

This is v3 of a driver for the Aspeed VUART. This version addresses feedback from Andy and Greg, and includes Rob's ack for the bindings change. The VUART is a serial device on the BMC side of the LPC bus that connects a BMC to it's host processor. We add a flag to the serial core to allow the

[PATCH] drivers/staging/iio: braces {} are not necessary for single statement blocks

Handling checkpatch.pl warning for if block. For single if statement block, braces are not neccessary. Making code consistent with linux kernel coding guidelines. Signed-off-by: Pushkar Jambhlekar --- drivers/staging/iio/accel/adis16203.c | 4 ++-- 1 file changed, 2

Re: [printk] fbc14616f4: BUG:kernel_reboot-without-warning_in_test_stage

On (04/09/17 12:12), Pavel Machek wrote: [..] > > a side note, > > that's rather unclear to me how would "message delayed" really help. > > if your system hard-lockup so badly and there are no printk messages > > even from NMI watchdog, then we won't be able to print that message. > > We are

Re: [PATCH 0/2] drm: dw-hdmi: various improvements

Hi, On 04/07/2017 07:49 PM, Romain Perier wrote: This set of patches split the stream handling functions in two parts. It introduces new callbacks that are specific to each variant, one for I2S and one for AHB. Then, as requested by the datasheet for the I2S variant, it adds support for gating

Re: patch to candidate for stable kernel 4.10

On Sun, Apr 09, 2017 at 11:36:30AM +0200, Mkrtchyan, Tigran wrote: > > Dear stable kernel maintainers, > > Please consider commit > > f17f8a14e82cdf34cd6473e3644f3c672b3884f6 > > to be included into 4.10 kernel. As long as it crashes > kernels used by some distors, we have to disable

Re: [PATCH v5 2/6] mtd: m25p80: add support of SPI 1-2-2 and 1-4-4 protocols

Hi Marek, Le 07/04/2017 à 01:37, Marek Vasut a écrit : > On 03/23/2017 12:33 AM, Cyrille Pitchen wrote: >> Before this patch, m25p80_read() supported few SPI protocols: >> - regular SPI 1-1-1 >> - SPI Dual Output 1-1-2 >> - SPI Quad Output 1-1-4 >> On the other hand, m25p80_write() only supported

[PATCH 5/5] target: Use kmalloc_array() in transport_kmap_data_sg()

From: Markus Elfring Date: Sun, 9 Apr 2017 21:07:14 +0200 A multiplication for the size determination of a memory allocation indicated that an array data structure should be processed. Thus use the corresponding function "kmalloc_array". This issue was detected by

Re: [PATCH v4 19/23] drivers/fsi: Add GPIO based FSI master

On 4/4/17 5:19 PM, Benjamin Herrenschmidt wrote: On Tue, 2017-04-04 at 12:32 -0500, Christopher Bostic wrote: Agreed that there is room for improvement. I intend to look further into your suggestions from here and our private conversation on the matter and make changes as appropriate. I

Re: [PATCH v5 1/6] mtd: spi-nor: introduce more SPI protocols and the Dual Transfer Mode

On 04/09/2017 11:16 PM, Cyrille Pitchen wrote: > Hi Marek, Hi, > thanks for the review. [...] >>> +struct spi_nor_flash_parameter { >>> + u64 size; >>> + u32 page_size; >>> + >>> + struct spi_nor_hwcaps hwcaps; >>> +

Re: [PATCH v4 19/23] drivers/fsi: Add GPIO based FSI master

On Mon, 2017-04-10 at 07:53 +1000, Benjamin Herrenschmidt wrote: > FYI. pdbg in userspace operates without any  delays in practice, the > overhead between the various load/store instructions seems > sufficient. > > The only delay that's needed is when going through the FSI2PIB (to do > SCOMs)

[PATCH v7 3/6] watchdog: iTCO_wdt: cleanup set/unset no_reboot_bit functions

iTCO_wdt no_reboot_bit set/unset functions has lot of common code between them. So merging these two functions into a single update function would remove these unnecessary code duplications. This patch fixes this issue by creating a no_reboot_bit update function to handle both set/unset functions.

Re: [kernel-hardening] Re: [RFC v2][PATCH 04/11] x86: Implement __arch_rare_write_begin/unmap()

On Sun, Apr 9, 2017 at 1:24 PM, PaX Team wrote: > >> In the context of virtually mapped stacks / KSTACKOVERFLOW, this >> naturally leads to different solutions. The upstream kernel had a >> bunch of buggy drivers that played badly with virtually mapped stacks. >> grsecurity

Re: [PATCH v3 1/1] perf tools: fix perf build with ARCH=x86_64

Hello Jiri On 04/09/2017 10:27 AM, Jiri Olsa wrote: On Tue, Apr 04, 2017 at 11:25:44PM -0700, jiada_w...@mentor.com wrote: From: Jiada Wang with commit: 0a943cb10ce78 (tools build: Add HOSTARCH Makefile variable) the following build failure is seen when build with

Re: [PATCH] Staging: comedidev.h comedi_lrange should be const struct

/Staging-comedidev-h-comedi_lrange-should-be-const-struct/20170409-224503 config: x86_64-allmodconfig compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901 reproduce: make ARCH=x86_64 allmodconfig make ARCH=x86_64 All warnings (new ones prefixed by >>): vim +629 drivers/staging/

[PATCH v4 0/1] fix perf build issue when ARCH=x86_64

From: Jiada Wang Changes from v4: update changlog to describe the reason of build failure replace ARCH with SRCARCH in pmu-events/Build and util/header.c Changes from v3: replace ARCH with SRCARCH in perf Changes from v2: added function purify-arch, transforms both

[PATCH v4 1/1] perf tools: fix perf build with ARCH=x86_64

From: Jiada Wang with commit: 0a943cb10ce78 (tools build: Add HOSTARCH Makefile variable) when build for ARCH=x86_64, ARCH=x86_64 is passed to perf instead of ARCH=x86, so perf package searchs header files from tools/arch/x86_64/include, which doesn't exist. the following

Re: [PATCH v2 2/2] drivers/serial: Add driver for Aspeed virtual UART

On Wed, Apr 5, 2017 at 8:24 PM, Andy Shevchenko wrote: > On Wed, Apr 5, 2017 at 7:03 AM, Joel Stanley wrote: > >> + port.port.irq = irq_of_parse_and_map(np, 0); > > Isn't better to get this via platform_get_irq() ? I can't see the benefit. > >>

Re: [PATCH] Documentation: vm, add hugetlbfs reservation overview

On April 08, 2017 1:43 AM Mike Kravetz wrote: > > Adding a brief overview of hugetlbfs reservation design and implementation > as an aid to those making code modifications in this area. > > Signed-off-by: Mike Kravetz > --- You are doing more than I can double thank

linux-next: manual merge of the clockevents tree with the arm-soc tree

Hi Daniel, Today's linux-next merge of the clockevents tree got a conflict in: arch/arm/boot/dts/rk3188.dtsi between commit: 2e1aa605fadd ("ARM: dts: rockchip: fix PPI misconfiguration on Cortex-A9 socs") from the arm-soc tree and commit: 500d0aa918a2 ("ARM: dts: rockchip: disable

Re: WARNING: at arch/x86/kernel/cpu/perf_event_intel_cqm.c:186 __put_rmid+0x28/0x80()

On 2017/3/2 14:55, Xishi Qiu wrote: ping > Hi, I test Trinity, and got the following log. > My OS version is RHEL 7.2, I'm not sure if it has fixed in mainline. > Any comment is welcome. > > [57676.532593] [ cut here ] > [57676.537415] WARNING: at

  1   2   3   4   5   >