Re: Question about ctr mode 3des-ede IV len

Hi Jussi, On 2016/12/7 21:15, Jussi Kivilinna wrote: > Hello, > > 07.12.2016, 14:43, Longpeng (Mike) kirjoitti: >> Hi Jussi and Herbert, >> >> I saw serveral des3-ede testcases(in crypto/testmgr.h) has 16-bytes IV, and >> the >> libgcrypt/nettle/RFC1851 said the IV-len is 8-bytes. >> >> Would y

[PATCH 1/5] staging: comedi: serial2002: Combine four kcalloc() calls into one in serial2002_setup_subdevs()

From: Markus Elfring Date: Thu, 8 Dec 2016 07:37:29 +0100 The function "kcalloc" was called in three cases by the function "serial2002_setup_subdevs" without checking immediately if it failed. This issue was detected by using the Coccinelle software. * Perform the desired memory allocation (and

[PATCH 2/5] staging: comedi: usbdux: Split a condition check in usbdux_alloc_usb_buffers()

From: Markus Elfring Date: Thu, 8 Dec 2016 10:01:54 +0100 The functions "kcalloc" and "kzalloc" were called in four cases by the function "usbdux_alloc_usb_buffers" without checking immediately if they succeded. This issue was detected by using the Coccinelle software. Allocated memory was also

Re: [PATCH] arm64: Work around Falkor erratum 1009

On 08/12/16 11:20, Will Deacon wrote: > On Wed, Dec 07, 2016 at 03:04:31PM -0500, Christopher Covington wrote: >> From: Shanker Donthineni >> >> During a TLB invalidate sequence targeting the inner shareable >> domain, Falkor may prematurely complete the DSB before all loads >> and stores using th

[PATCH 3/5] staging: comedi: usbdux: Move an assignment in usbdux_alloc_usb_buffers()

From: Markus Elfring Date: Thu, 8 Dec 2016 10:13:56 +0100 Move one assignment for the local variable "usb" so that its setting will only be performed after some memory allocations succeeded by this function. Signed-off-by: Markus Elfring --- drivers/staging/comedi/drivers/usbdux.c | 3 ++- 1 f

[PATCH 0/5] staging-COMEDI: Fine-tuning for three functions

From: Markus Elfring Date: Thu, 8 Dec 2016 11:37:37 +0100 Some update suggestions were taken into account from static source code analysis. Markus Elfring (5): Combine four kcalloc() calls into one in serial2002_setup_subdevs() Split a condition check in usbdux_alloc_usb_buffers() Move an

[PATCH 4/5] staging: comedi: usbduxsigma: Split a condition check in usbduxsigma_alloc_usb_buffers()

From: Markus Elfring Date: Thu, 8 Dec 2016 11:15:40 +0100 The functions "kcalloc" and "kzalloc" were called in four cases by the function "usbduxsigma_alloc_usb_buffers" without checking immediately if they succeded. This issue was detected by using the Coccinelle software. Allocated memory was

Re: [PATCH 2/3] arm64: Work around Falkor erratum 1003

On Wed, Dec 07, 2016 at 03:00:26PM -0500, Christopher Covington wrote: > From: Shanker Donthineni > > On the Qualcomm Datacenter Technologies Falkor v1 CPU, memory accesses may > allocate TLB entries using an incorrect ASID when TTBRx_EL1 is being > updated. Changing the TTBRx_EL1[ASID] and TTBRx

[PATCH 5/5] staging: comedi: usbduxsigma: Move an assignment in usbduxsigma_alloc_usb_buffers()

From: Markus Elfring Date: Thu, 8 Dec 2016 11:20:38 +0100 Move one assignment for the local variable "usb" so that its setting will only be performed after some memory allocations succeeded by this function. Signed-off-by: Markus Elfring --- drivers/staging/comedi/drivers/usbduxsigma.c | 3 ++-

Re: [BUG 4.9] New led trigger usbport gets the kernel to panic

On 8 December 2016 at 09:40, Jacek Anaszewski wrote: > On 12/06/2016 06:29 PM, Rafał Miłecki wrote: >> >> On 6 December 2016 at 18:26, Pavel Machek wrote: >>> >>> On Fri 2016-12-02 09:48:18, Ralph Sennhauser wrote: On Thu, 1 Dec 2016 17:56:07 +0100 Rafał Miłecki wrote: >

Re: [PATCH v5 2/5] i2c: Add STM32F4 I2C driver

Hi M'boumba, [auto build test WARNING on wsa/i2c/for-next] [also build test WARNING on v4.9-rc8 next-20161208] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/M-boumba-Cedric-Madiang

Re: Tearing down DMA transfer setup after DMA client has finished

Vinod Koul writes: > On Wed, Dec 07, 2016 at 04:44:55PM +, Måns Rullgård wrote: >> Vinod Koul writes: >> >> >> >> What you're proposing, Vinod, is to make a channel exclusive >> >> to a driver, as long as the driver has not explicitly released >> >> the channel, via dma_release_channel(), r

Re: [PATCH] x86/vm86: fix compilation warning on a unused variable

On Thu, Dec 08, 2016 at 01:50:11PM +0300, Kirill A. Shutemov wrote: > On Wed, Dec 07, 2016 at 11:38:33PM -0500, Jérémy Lefaure wrote: > > When CONFIG_TRANSPARENT_HUGEPAGE is disabled, split_huge_pmd is a no-op > > stub. In such case, vma is unused and a compiler raises a warning: > > > > arch/x86/

Re: Tearing down DMA transfer setup after DMA client has finished

Vinod Koul writes: > On Wed, Dec 07, 2016 at 04:45:58PM +, Måns Rullgård wrote: >> Vinod Koul writes: >> >> > On Tue, Dec 06, 2016 at 01:14:20PM +, Måns Rullgård wrote: >> >> >> >> That's not going to work very well. Device drivers typically request >> >> dma channels in their probe f

Re: [PATCH] arm64: Work around Falkor erratum 1009

On Wed, Dec 07, 2016 at 03:04:31PM -0500, Christopher Covington wrote: > From: Shanker Donthineni > > During a TLB invalidate sequence targeting the inner shareable > domain, Falkor may prematurely complete the DSB before all loads > and stores using the old translation are observed; instruction

[GIT PULL] efi: Pass secure boot mode to kernel

ernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git tags/efi-secure-boot-20161208 for you to fetch changes up to e71dd6bffca41faf7b4458c230e5c3d3c2b16d3e: efi: Add EFI_SECURE_BOOT bit (2016-12-08 08:19:04 +)

Re: Tearing down DMA transfer setup after DMA client has finished

Geert Uytterhoeven writes: > On Thu, Dec 8, 2016 at 11:54 AM, Mason wrote: >> On 08/12/2016 11:39, Vinod Koul wrote: >>> On Wed, Dec 07, 2016 at 04:45:58PM +, Måns Rullgård wrote: Vinod Koul writes: > On Tue, Dec 06, 2016 at 01:14:20PM +, Måns Rullgård wrote: >> That's not

Re: [PATCH v4 1/2] mmc: sdhci: export sdhci_execute_tuning()

On 05/12/16 04:10, Masahiro Yamada wrote: > Some SDHCI-compat controllers support not only SD, but also eMMC, > but they use different commands for tuning: CMD19 for SD, CMD21 for > eMMC. > > Due to the difference of the underlying mechanism, some controllers > (at least, the Cadence IP is the cas

[PATCH] usb: gadget: f_fs: Fix possibe deadlock

When system try to close /dev/usb-ffs/adb/ep0 on one core, at the same time another core try to attach new UDC, which will cause deadlock as below scenario. Thus we should release ffs lock before issuing unregister_gadget_item(). [ 52.642225] c1 ==

Re: [GIT PULL] efi: Pass secure boot mode to kernel

On Thu, 08 Dec, at 11:45:17AM, David Howells wrote: > Hi Matt, Ard, > > Is it too late to request this for the upcoming merge window? For something as non-trivial as this, yes, it's too late. We generally close the EFI tree window for new features around -rc5 time. > Also, I've made > Lukas's re

Re: [PATCH v4 1/2] mmc: sdhci: export sdhci_execute_tuning()

On 08/12/16 13:49, Adrian Hunter wrote: > On 05/12/16 04:10, Masahiro Yamada wrote: >> Some SDHCI-compat controllers support not only SD, but also eMMC, >> but they use different commands for tuning: CMD19 for SD, CMD21 for >> eMMC. >> >> Due to the difference of the underlying mechanism, some cont

Re: [PATCH v4 2/2] mmc: sdhci-cadence: add Cadence SD4HC support

On 05/12/16 04:10, Masahiro Yamada wrote: > Add a driver for the Cadence SD4HC SD/SDIO/eMMC Controller. > > For SD, it basically relies on the SDHCI standard code. > For eMMC, this driver provides some callbacks to support the > hardware part that is specific to this IP design. > > Signed-off-by:

Re: Tearing down DMA transfer setup after DMA client has finished

On Thu, Dec 8, 2016 at 12:44 PM, Måns Rullgård wrote: > Vinod Koul writes: >> On Wed, Dec 07, 2016 at 04:45:58PM +, Måns Rullgård wrote: >>> Vinod Koul writes: >>> > On Tue, Dec 06, 2016 at 01:14:20PM +, Måns Rullgård wrote: >>> >> That's not going to work very well. Device drivers typi

Re: Tearing down DMA transfer setup after DMA client has finished

Hi Måns, On Thu, Dec 8, 2016 at 12:47 PM, Måns Rullgård wrote: > Geert Uytterhoeven writes: >> On Thu, Dec 8, 2016 at 11:54 AM, Mason wrote: >>> On 08/12/2016 11:39, Vinod Koul wrote: On Wed, Dec 07, 2016 at 04:45:58PM +, Måns Rullgård wrote: > Vinod Koul writes: >> On Tue, De

Re: [PATCH v3 4/6] mfd: dt: Add bindings for the Aspeed LPC Host Controller (LHC)

On Thu, 2016-12-08 at 12:42 +1030, Joel Stanley wrote: > > On Tue, Dec 6, 2016 at 1:23 PM, Andrew Jeffery wrote: > > The LPC bus pinmux configuration on fifth generation Aspeed SoCs depends > > on bits in both the System Control Unit and the LPC Host Controller. > > > > The Aspeed LPC Host Contro

Re: [PATCH] x86/smpboot: Make logical package management more robust

On Thu, Dec 08, 2016 at 10:04:25AM +0100, Thomas Gleixner wrote: > @@ -289,16 +293,17 @@ int topology_update_package_map(unsigned > if (test_and_set_bit(pkg, physical_package_map)) > goto found; > > - if (logical_packages_frozen) { > - physical_to_logical_pkg[p

Re: [PATCH v2] rpmsg: qcom_smd: Add support for "label" property

On 2016-12-02 2:06 PM, Bjorn Andersson wrote: Add support for the "label" property, used to give the edge a name other than the one of the DT node. This allows the implementor to provide consistently named edges when using the rpmsg character device. Signed-off-by: Bjorn Andersson --- Changes

Re: [RFC PATCH 0/3] staging: remove fbdev drivers

On Thu, Dec 8, 2016 at 11:10 AM, Daniel Vetter wrote: > On Thu, Dec 08, 2016 at 12:01:19PM +1100, Benjamin Herrenschmidt wrote: >> On Wed, 2016-11-23 at 10:03 +0200, Tomi Valkeinen wrote: >> > Since the fbdev framework is in maintenance mode and all new display >> > drivers >> > should be made wi

Re: Tearing down DMA transfer setup after DMA client has finished

On 08/12/2016 13:03, Geert Uytterhoeven wrote: > Måns Rullgård wrote: > >> Geert Uytterhoeven writes: >> >>> Can you fall back to PIO if requesting a channel fails? >> >> Why are we debating this nonsense? There is an easy fix that doesn't >> require changing the semantics of existing functions o

Re: [PATCH v5 2/5] i2c: Add STM32F4 I2C driver

Hi M'boumba, [auto build test WARNING on wsa/i2c/for-next] [also build test WARNING on v4.9-rc8 next-20161208] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/M-boumba-Cedric-Madiang

Re: Tearing down DMA transfer setup after DMA client has finished

Geert Uytterhoeven writes: > On Thu, Dec 8, 2016 at 12:44 PM, Måns Rullgård wrote: >> Vinod Koul writes: >>> On Wed, Dec 07, 2016 at 04:45:58PM +, Måns Rullgård wrote: Vinod Koul writes: > On Tue, Dec 06, 2016 at 01:14:20PM +, Måns Rullgård wrote: >> That's not going to

Re: Tearing down DMA transfer setup after DMA client has finished

Geert Uytterhoeven writes: > Hi Måns, > > On Thu, Dec 8, 2016 at 12:47 PM, Måns Rullgård wrote: >> Geert Uytterhoeven writes: >>> On Thu, Dec 8, 2016 at 11:54 AM, Mason wrote: On 08/12/2016 11:39, Vinod Koul wrote: > On Wed, Dec 07, 2016 at 04:45:58PM +, Måns Rullgård wrote: >

[PATCH v5 2/7] MFD: add STM32 General Purpose Timer driver

This hardware block could at used at same time for PWM generation and IIO timers. PWM and IIO timer configuration are mixed in the same registers so we need a multi fonction driver to be able to share those registers. version 5: - fix Lee comments about detect function - add missing dependency on

[PATCH v5 1/7] MFD: add bindings for STM32 General Purpose Timer driver

Add bindings information for STM32 General Purpose Timer version 2: - rename stm32-mfd-timer to stm32-gptimer - only keep one compatible string Signed-off-by: Benjamin Gaignard --- .../bindings/mfd/stm32-general-purpose-timer.txt | 39 ++ 1 file changed, 39 insertions(+)

[PATCH v5 0/7] Add PWM and IIO timer drivers for STM32

version 5: - fix comments done on version 4 - rebased on kernel 4.9-rc8 - change nodes names and re-order then by addresses version 4: - fix comments done on version 3 - don't use interrupts anymore in IIO timer - detect hardware capabilities at probe time to simplify binding version 3: - no chan

Re: [PATCH 1/5] staging: comedi: serial2002: Combine four kcalloc() calls into one in serial2002_setup_subdevs()

The original code was simpler. regards, dan carpenter

Re: [PATCH 02/22] m68k/mac: macints - Modernize printing of kernel messages

On Wed, Dec 7, 2016 at 11:45 PM, Finn Thain wrote: > On Wed, 7 Dec 2016, Geert Uytterhoeven wrote: > >> - Introduce helpers for printing debug messages, incl. dummies for >> validating format strings when debugging is disabled, >> - Convert from printk() to pr_*(), >> - Add missing conti

[PATCH v5 3/7] PWM: add pwm-stm32 DT bindings

Define bindings for pwm-stm32 version 2: - use parameters instead of compatible of handle the hardware configuration Signed-off-by: Benjamin Gaignard --- .../devicetree/bindings/pwm/pwm-stm32.txt | 33 ++ 1 file changed, 33 insertions(+) create mode 100644 Document

[PATCH v5 7/7] ARM: dts: stm32: add STM32 General Purpose Timer driver in DT

Add General Purpose Timers and it sub-nodes into DT for stm32f4. Define and enable pwm1 and pwm3 for stm32f469 discovery board version 5: - rename gptimer node to timers - re-order timers node par addresses version 4: - remove unwanted indexing in pwm@ and timer@ node name - use "reg" instead of

[PATCH v5 4/7] PWM: add PWM driver for STM32 plaftorm

This driver adds support for PWM driver on STM32 platform. The SoC have multiple instances of the hardware IP and each of them could have small differences: number of channels, complementary output, auto reload register size... version 4: - detect at probe time hardware capabilities - fix comments

[PATCH 2/8] x86/efi: Allow invocation of arbitrary runtime services [ver #6]

Provide the ability to perform mixed-mode runtime service calls for x86 in the same way that commit 0a637ee61247bd4bed9b2a07568ef7a1cfc76187 ("x86/efi: Allow invocation of arbitrary boot services") provides the ability to invoke arbitrary boot services. Suggested-by: Lukas Wunner Signed-off-by: D

[PATCH 1/8] efi: use typed function pointers for runtime services table [ver #6]

From: Ard Biesheuvel Instead of using void pointers, and casting them to correctly typed function pointers upon use, declare the runtime services pointers as function pointers using their respective prototypes, for which typedefs are already available. Signed-off-by: Ard Biesheuvel Signed-off-b

[PATCH v5 5/7] IIO: add bindings for STM32 timer trigger driver

Define bindings for STM32 timer trigger version 4: - remove triggers enumeration from DT - add reg parameter version 3: - change file name - add cross reference with mfd bindings version 2: - only keep one compatible - add DT parameters to set lists of the triggers: one list describe the trigg

[PATCH 3/8] arm/efi: Allow invocation of arbitrary runtime services [ver #6]

efi_call_runtime() is provided for x86 to be able abstract mixed mode support. Provide this for ARM also so that common code work in mixed mode also. Suggested-by: Lukas Wunner Signed-off-by: David Howells --- arch/arm/include/asm/efi.h |1 + arch/arm64/include/asm/efi.h |1 + 2 fil

[PATCH 0/8] efi: Pass secure boot mode to kernel [ver #6]

Here's a set of patches that can determine the secure boot state of the UEFI BIOS and pass that along to the main kernel image. This involves generalising ARM's efi_get_secureboot() function and making it mixed-mode safe. Changes: Ver 6: - Removed unnecessary variable init and trimmed comme

[PATCH 4/8] efi: Add SHIM and image security database GUID definitions [ver #6]

Add the definitions for shim and image security database, both of which are used widely in various Linux distros. Signed-off-by: Josh Boyer Signed-off-by: David Howells Reviewed-by: Ard Biesheuvel --- include/linux/efi.h |3 +++ 1 file changed, 3 insertions(+) diff --git a/include/linux/

[PATCH 8/8] efi: Add EFI_SECURE_BOOT bit [ver #6]

From: Josh Boyer UEFI machines can be booted in Secure Boot mode. Add a EFI_SECURE_BOOT bit that can be passed to efi_enabled() to find out whether secure boot is enabled. This will be used by the SysRq+x handler, registered by the x86 arch, to find out whether secure boot mode is enabled so th

[PATCH 7/8] efi: Handle secure boot from UEFI-2.6 [ver #6]

UEFI-2.6 adds a new variable, DeployedMode. If it exists, this must be 1 if we're to engage lockdown mode. Reported-by: James Bottomley Signed-off-by: David Howells --- drivers/firmware/efi/libstub/secureboot.c | 16 +++- include/linux/efi.h |4 2

[PATCH 6/8] efi: Disable secure boot if shim is in insecure mode [ver #6]

From: Josh Boyer A user can manually tell the shim boot loader to disable validation of images it loads. When a user does this, it creates a UEFI variable called MokSBState that does not have the runtime attribute set. Given that the user explicitly disabled validation, we can honor that and no

Re: [PATCH v4 2/2] mmc: sdhci-cadence: add Cadence SD4HC support

On 5 December 2016 at 03:10, Masahiro Yamada wrote: > Add a driver for the Cadence SD4HC SD/SDIO/eMMC Controller. > > For SD, it basically relies on the SDHCI standard code. > For eMMC, this driver provides some callbacks to support the > hardware part that is specific to this IP design. > > Signe

[PATCH v5 6/7] IIO: add STM32 timer trigger driver

Timers IPs can be used to generate triggers for other IPs like DAC, ADC or other timers. Each trigger may result of timer internals signals like counter enable, reset or edge, this configuration could be done through "master_mode" device attribute. A timer device could be triggered by other timers

Re: [PATCH v4 1/2] mmc: sdhci: export sdhci_execute_tuning()

On 5 December 2016 at 03:10, Masahiro Yamada wrote: > Some SDHCI-compat controllers support not only SD, but also eMMC, > but they use different commands for tuning: CMD19 for SD, CMD21 for > eMMC. > > Due to the difference of the underlying mechanism, some controllers > (at least, the Cadence IP

Re: Tearing down DMA transfer setup after DMA client has finished

On Thu, Dec 8, 2016 at 1:20 PM, Måns Rullgård wrote: > Geert Uytterhoeven writes: >> On Thu, Dec 8, 2016 at 12:44 PM, Måns Rullgård wrote: >>> Vinod Koul writes: On Wed, Dec 07, 2016 at 04:45:58PM +, Måns Rullgård wrote: > Vinod Koul writes: > > On Tue, Dec 06, 2016 at 01:14:2

Re: [Lsf-pc] LSF/MM 2017: Call for Proposals

On Thu 08-12-16 13:26:19, Michal Hocko wrote: > On Wed 07-12-16 06:57:06, James Bottomley wrote: > [...] > > Just on this point, since there seems to be a lot of confusion: lsf-pc > > is the list for contacting the programme committee, so you cannot > > subscribe to it. > > > > There is no -discus

[PATCH 5/8] efi: Get the secure boot status [ver #6]

Get the firmware's secure-boot status in the kernel boot wrapper and stash it somewhere that the main kernel image can find. The efi_get_secureboot() function is extracted from the arm stub and (a) generalised so that it can be called from x86 and (b) made to use efi_call_runtime() so that it can

Re: [PATCH 2/5] staging: comedi: usbdux: Split a condition check in usbdux_alloc_usb_buffers()

On Thu, Dec 08, 2016 at 12:34:27PM +0100, SF Markus Elfring wrote: > From: Markus Elfring > Date: Thu, 8 Dec 2016 10:01:54 +0100 > > The functions "kcalloc" and "kzalloc" were called in four cases by the > function "usbdux_alloc_usb_buffers" without checking immediately > if they succeded. > This

Re: [patch] mm, compaction: add vmstats for kcompactd work

On Thu 08-12-16 09:04:12, Vlastimil Babka wrote: > On 12/08/2016 02:50 AM, David Rientjes wrote: > > A "compact_daemon_wake" vmstat exists that represents the number of times > > kcompactd has woken up. This doesn't represent how much work it actually > > did, though. > > > > It's useful to under

Re: [PATCH v4 2/2] mmc: sdhci-cadence: add Cadence SD4HC support

Hi Ulf, 2016-12-08 21:32 GMT+09:00 Ulf Hansson : > On 5 December 2016 at 03:10, Masahiro Yamada > wrote: >> Add a driver for the Cadence SD4HC SD/SDIO/eMMC Controller. >> >> For SD, it basically relies on the SDHCI standard code. >> For eMMC, this driver provides some callbacks to support the >>

[PATCH 5/7] dell-laptop: import dell_micmute_led_set() from drivers/leds/dell-led.c

To ensure all users of dell-smbios are in drivers/platform/x86, move the dell_micmute_led_set() method from drivers/leds/dell-led.c to drivers/platform/x86/dell-laptop.c. Signed-off-by: Michał Kępień --- drivers/leds/dell-led.c| 29 - drivers/platform/x86/

[PATCH 3/7] ALSA: hda - use dell_micmute_led_set() instead of dell_app_wmi_led_set()

When the dell_app_wmi_led_set() method was introduced in db6d8cc ("dell-led: add mic mute led interface"), it was implemented as an easily extensible entry point for other modules to set the state of various LEDs. However, almost three years later it is still only used to control the mic mute LED,

[PATCH 1/7] dell-led: remove GUID check from dell_micmute_led_set()

As dell_micmute_led_set() no longer uses the dell_wmi_perform_query() method, which was removed in 0c41a08 ("dell-led: use dell_smbios_send_request() for performing SMBIOS calls"), the DELL_APP_GUID check is redundant and thus can be safely removed. Signed-off-by: Michał Kępień --- drivers/leds/

[PATCH 7/7] dell-led: move driver to drivers/platform/x86/dell-wmi-led.c

The dell-led driver handles a specific WMI GUID present on some Dell laptops and as such it belongs in the x86 platform driver subsystem. Source code is moved along with the relevant Kconfig and Makefile entries with some minor modifications: - Kconfig option is renamed from COFIG_LEDS_DELL_NETB

[PATCH 0/7] Move dell-led to drivers/platform/x86

This patch series moves the dell-led driver from the LED subsystem to the x86 platform driver subsystem. I decided to also CC the sound subsystem contacts for the whole series as sound/pci/hda/dell_wmi_helper.c is also affected. The original motivation behind this effort was to move all code usin

[PATCH 4/7] dell-led: remove dell_app_wmi_led_set()

All calls to dell_app_wmi_led_set() have been replaced with direct calls to dell_micmute_led_set(), so the former can be safely removed along with its related enum. Signed-off-by: Michał Kępień --- drivers/leds/dell-led.c | 17 - include/linux/dell-led.h | 5 - 2 files chan

[PATCH 6/7] dell-led: remove code related to mic mute LED

With dell_micmute_led_set() moved to drivers/platform/x86/dell-laptop.c, all remnants of the mic mute LED handling code can be removed from drivers/leds/dell-led.c, restoring it back to the state it was in before db6d8cc ("dell-led: add mic mute led interface"). Signed-off-by: Michał Kępień ---

Re: [PATCH 2/5] staging: comedi: usbdux: Split a condition check in usbdux_alloc_usb_buffers()

Same bug. regards, dan carpenter

[PATCH 2/7] dell-led: export dell_micmute_led_set()

When the dell_app_wmi_led_set() method was introduced in db6d8cc ("dell-led: add mic mute led interface"), it was implemented as an easily extensible entry point for other modules to set the state of various LEDs. However, almost three years later it is still only used to control the mic mute LED,

Re: LSF/MM 2017: Call for Proposals

On Wed 07-12-16 06:57:06, James Bottomley wrote: [...] > Just on this point, since there seems to be a lot of confusion: lsf-pc > is the list for contacting the programme committee, so you cannot > subscribe to it. > > There is no -discuss equivalent, like kernel summit has, because we > expect yo

Re: [PATCH 5/8] efi: Get the secure boot status [ver #5]

On Thu, Dec 08, 2016 at 08:16:21AM +, David Howells wrote: > +/* > + * Determine whether we're in secure boot mode. > + */ > +enum efi_secureboot_mode efi_get_secureboot(efi_system_table_t > *sys_table_arg) > +{ > + u8 secboot, setupmode; > + unsigned long size; > + efi_status_t st

Re: [PATCH 3/5] staging: comedi: usbdux: Move an assignment in usbdux_alloc_usb_buffers()

This one is pointless. It's just a style issue that you invented. Only Joe Perches is allowed to invent new style guidelines. regards, dan carpenter

[PATCH v2 0/2] mtd: spi-nor: add a stateless method to support memory size above 128Mib

Hi all, this series of patches is based on next-20161208 and can also be applied to the git://github.com/spi-nor/linux.git tree. It has been extracted from the SFDP series and is resent as a standalone series. This series fixes compatibility issue between Linux and many bootloaders when using

Re: Tearing down DMA transfer setup after DMA client has finished

On 08/12/2016 13:20, Måns Rullgård wrote: > The only problem we have is that nobody envisioned hardware where the > dma engine indicates completion slightly too soon. I suspect there's a > fifo or such somewhere, and the interrupt is triggered when the last > byte has been placed in the fifo rath

Re: [PATCH 01/22] m68k/atari: Modernize printing of kernel messages

On Wed, Dec 7, 2016 at 11:36 PM, Finn Thain wrote: > On Wed, 7 Dec 2016, Geert Uytterhoeven wrote: >> - Convert from printk() to pr_*(), >> - Add missing continuations, to fix user-visible breakage, >> - Drop useless WARNING prefix, >> - Move trailing spaces to start of continuations. >> >

[PATCH v2 1/2] mtd: spi-nor: rename SPINOR_OP_* macros of the 4-byte address op codes

This patch renames the SPINOR_OP_* macros of the 4-byte address instruction set so the new names all share a common pattern: the 4-byte address name is built from the 3-byte address name appending the "_4B" suffix. The patch also introduces new op codes to support other SPI protocols such as SPI 1

Re: [PATCH 2/5] staging: comedi: usbdux: Split a condition check in usbdux_alloc_usb_buffers()

On 08/12/16 11:34, SF Markus Elfring wrote: From: Markus Elfring Date: Thu, 8 Dec 2016 10:01:54 +0100 The functions "kcalloc" and "kzalloc" were called in four cases by the function "usbdux_alloc_usb_buffers" without checking immediately if they succeded. This issue was detected by using the Co

Re: Tearing down DMA transfer setup after DMA client has finished

Mason writes: > On 08/12/2016 13:20, Måns Rullgård wrote: > >> The only problem we have is that nobody envisioned hardware where the >> dma engine indicates completion slightly too soon. I suspect there's a >> fifo or such somewhere, and the interrupt is triggered when the last >> byte has been

Lockdep splat from destroy_workqueue() with RT_PREEMPT_FULL

Hi, I am seeing the following splat when stopping btattach on v4.4.30-rt41 with PREEMPT_RT_FULL with lockdep and slub_debug. The bad unlock balance seems to just be an effect of the lock having been overwritten with POISON_FREE, the real issue is that put_pwq_unlocked() is not resuming and unlock

[PATCH v2 2/2] mtd: spi-nor: add a stateless method to support memory size above 128Mib

This patch provides an alternative mean to support memory above 16MiB (128Mib) by replacing 3byte address op codes by their associated 4byte address versions. Using the dedicated 4byte address op codes doesn't change the internal state of the SPI NOR memory as opposed to using other means such as

[PATCH v5 1/2] mmc: sdhci: export sdhci_execute_tuning()

Some SDHCI-compat controllers support not only SD, but also eMMC, but they use different commands for tuning: CMD19 for SD, CMD21 for eMMC. Due to the difference of the underlying mechanism, some controllers (at least, the Cadence IP is the case) provide their own registers for the eMMC tuning. T

Re: [PATCH 4/5] staging: comedi: usbduxsigma: Split a condition check in usbduxsigma_alloc_usb_buffers()

On 08/12/16 11:37, SF Markus Elfring wrote: From: Markus Elfring Date: Thu, 8 Dec 2016 11:15:40 +0100 The functions "kcalloc" and "kzalloc" were called in four cases by the function "usbduxsigma_alloc_usb_buffers" without checking immediately if they succeded. This issue was detected by using t

Re: [PATCH] x86/smpboot: Make logical package management more robust

On Thu, 8 Dec 2016, Peter Zijlstra wrote: > On Thu, Dec 08, 2016 at 10:04:25AM +0100, Thomas Gleixner wrote: > > @@ -289,16 +293,17 @@ int topology_update_package_map(unsigned > > if (test_and_set_bit(pkg, physical_package_map)) > > goto found; > > > > - if (logical_packages_fro

[PATCH v5 2/2] mmc: sdhci-cadence: add Cadence SD4HC support

Add a driver for the Cadence SD4HC SD/SDIO/eMMC Controller. For SD, it basically relies on the SDHCI standard code. For eMMC, this driver provides some callbacks to support the hardware part that is specific to this IP design. Signed-off-by: Masahiro Yamada Acked-by: Adrian Hunter --- Changes

[PATCH v5 0/2] mmc: sdhci: export sdhci_execute_tuning(), then add Cadence SDHCI driver

1/2 exports sdhci_execute_tuning(), which I want to use for 2/2. 2/2 adds a new driver for Cadence's controller IP. Changes in v2: - Remove unnecessary "select MMC_SDHCI_IO_ACCESSORS" Masahiro Yamada (2): mmc: sdhci: export sdhci_execute_tuning() mmc: sdhci-cadence: add Cadence SD4HC sup

Re: [PATCH v4 2/2] mmc: sdhci-cadence: add Cadence SD4HC support

Hi Ulf, 2016-12-08 21:32 GMT+09:00 Ulf Hansson : > On 5 December 2016 at 03:10, Masahiro Yamada > wrote: >> Add a driver for the Cadence SD4HC SD/SDIO/eMMC Controller. >> >> For SD, it basically relies on the SDHCI standard code. >> For eMMC, this driver provides some callbacks to support the >>

Re: [PATCH 2/2] mm, oom: do not enfore OOM killer for __GFP_NOFAIL automatically

Michal Hocko wrote: > On Tue 06-12-16 19:38:38, Tetsuo Handa wrote: > > You are trying to increase possible locations of lockups by changing > > default behavior of __GFP_NOFAIL. > > I disagree. I have tried to explain that it is much more important to > have fewer silent side effects than optimiz

Re: [PATCH] gcov: support GCC 7.1

hat helps quoting them in replies. See also >> linux/Documentation/SubmittingPatches. > > Sure, thanks for info. I'm attaching new version: > > Starting from GCC 7.1, __gcov_exit is a new symbol expected > to be implemented in a profiling runtime. Update number of pro

Re: [RFC PATCH] mm: introduce kv[mz]alloc helpers

Am 08.12.2016 um 11:33 schrieb Michal Hocko: From: Michal Hocko Using kmalloc with the vmalloc fallback for larger allocations is a common pattern in the kernel code. Yet we do not have any common helper for that and so users have invented their own helpers. Some of them are really creative whe

Re: [PATCH] x86/smpboot: Make logical package management more robust

On Thu, Dec 08, 2016 at 01:49:28PM +0100, Thomas Gleixner wrote: > > > > - if (logical_packages > __max_logical_packages) { > > > - pr_warn("Detected more packages (%u), then computed by BIOS > > > data (%u).\n", > > > - logical_packages, __max_logical_packages); > > > -

[PATCH] ASoC: rsnd: don't double free kctrl

From: Colin Ian King On an error, snd_ctl_add already free's kctrl, so calling snd_ctl_free_one to free it again leads to a double free error. Fix this by removing the extraneous snd_ctl_free_one call. Issue found using static analysis with CoverityScan, CID 1372908 Signed-off-by: Colin Ian Ki

Re: [PATCH v2 0/5] kthread: make struct kthread kmalloc'ed

On Tue, Nov 29, 2016 at 06:50:37PM +0100, Oleg Nesterov wrote: > Hello, > > I think that these patches were lost in confusing discussion, let me resend. > The only change is that I added the acks from Thomas and Petr. > > More to come. Acked-by: Peter Zijlstra (Intel)

Re: [PATCH] x86/smpboot: Make logical package management more robust

On Thu, 8 Dec 2016, Peter Zijlstra wrote: > On Thu, Dec 08, 2016 at 01:49:28PM +0100, Thomas Gleixner wrote: > > > > > > - if (logical_packages > __max_logical_packages) { > > > > - pr_warn("Detected more packages (%u), then computed by > > > > BIOS data (%u).\n", > > > > -

Re: [PATCH 16/18] arm64: ptrace: handle ptrace_request differently for aarch32 and ilp32

On Wed, Dec 07, 2016 at 09:40:13PM +0100, Arnd Bergmann wrote: > On Wednesday, December 7, 2016 4:59:13 PM CET Catalin Marinas wrote: > > On Tue, Dec 06, 2016 at 11:55:08AM +0530, Yury Norov wrote: > > > On Mon, Dec 05, 2016 at 04:34:23PM +, Catalin Marinas wrote: > > > > On Fri, Oct 21, 2016 a

[PATCH] drm/edid: Don't print an error if the checksum of a CEA block is wrong

It's common to share screens within CI labs, and it's also common for KVM switches to alter the contents of the CEA block but leave the checksum outdated. So in this case, print a debug message instead of an error. References: https://bugs.freedesktop.org/show_bug.cgi?id=98228 Cc: Chris Wilson C

Re: [RFC v3 00/10] KVM PCIe/MSI passthrough on ARM/ARM64 and IOVA reserved regions

On 08/12/16 09:36, Auger Eric wrote: > Hi, > > On 15/11/2016 14:09, Eric Auger wrote: >> Following LPC discussions, we now report reserved regions through >> iommu-group sysfs reserved_regions attribute file. > > > While I am respinning this series into v4, here is a tentative summary > of techn

Re: [PATCH 08/11] ACPICA: Tables: Back port acpi_get_table_with_size() and early_acpi_os_unmap_memory() from Linux kernel

On Thu, Dec 8, 2016 at 2:11 AM, Dan Williams wrote: > On Tue, Nov 29, 2016 at 11:21 PM, Lv Zheng wrote: >> ACPICA commit cac6790954d4d752a083e610b8a22febcd07 >> >> This patch back ports Linux acpi_get_table_with_size() and >> early_acpi_os_unmap_memory() into ACPICA upstream to reduce diverge

Re: [PATCH] arm64: Work around Falkor erratum 1009

On Thu, Dec 08, 2016 at 11:45:12AM +, Mark Rutland wrote: > On Wed, Dec 07, 2016 at 03:04:31PM -0500, Christopher Covington wrote: > > + asm volatile(ALTERNATIVE( > > +"nop \n" > > +"nop \n", > > +"tlbi vmalle1is \n" > > +"dsb is

Re: [PATCH 0/5] staging-COMEDI: Fine-tuning for three functions

On Thu, Dec 08, 2016 at 12:30:20PM +0100, SF Markus Elfring wrote: > From: Markus Elfring > Date: Thu, 8 Dec 2016 11:37:37 +0100 > > Some update suggestions were taken into account > from static source code analysis. > > Markus Elfring (5): > Combine four kcalloc() calls into one in serial2002

Re: Tearing down DMA transfer setup after DMA client has finished

On 08/12/2016 13:44, Måns Rullgård wrote: > Mason writes: > >> On 08/12/2016 13:20, Måns Rullgård wrote: >> >>> The only problem we have is that nobody envisioned hardware where the >>> dma engine indicates completion slightly too soon. I suspect there's a >>> fifo or such somewhere, and the in

Re: linux-next: build failure in the powerpc allyesconfig build

On Monday, December 5, 2016 4:22:04 PM CET Stephen Rothwell wrote: > Hi all, > > After mergeing everything but Andrew's tree, today's linux-next build > (powerpc allyesconfig) failed like this: > > kallsyms failure: relative symbol value 0xc000 out of range in > relative mode > > I

Re: Lockdep splat from destroy_workqueue() with RT_PREEMPT_FULL

On 2016-12-08 12:20:28 [+], John Keeping wrote: > Hi, Hi John, > I am seeing the following splat when stopping btattach on v4.4.30-rt41 > with PREEMPT_RT_FULL with lockdep and slub_debug. > > The bad unlock balance seems to just be an effect of the lock having > been overwritten with POISON_F

<    1   2   3   4   5   6   7   8   9   >