Re: [PATCH 3/3][v4] staging: fsl-mc: move bus driver out of staging

On Fri, May 19 2017 at 02:41:43 PM, Matthias Brugger wrote: > On 19/05/17 15:13, laurentiu.tu...@nxp.com wrote: >> From: Stuart Yoder >> >> Move the source files out of staging into their final locations: >>-include files in

[PATCH v2] Use ctlr directly in rdac_failover_get()

rdac_failover_get references struct rdac_controller as ctlr->ms_sdev->handler_data->ctlr for no apparent reason. Besides being inefficient this also introduces a null-pointer dereference as send_mode_select() sets ctlr->ms_sdev to NULL before calling rdac_failover_get(): [ 18.432550]

[PATCH 2/2] libsas: Enhance libsas hotplug

Libsas complete a hotplug event notified by LLDD in several works, for example, if libsas receive a PHYE_LOSS_OF_SIGNAL, we process it in following steps: notify_phy_event[interrupt context] sas_queue_event [queue work on shost->work_q]

Re: [PATCH] regmap: add regmap_debugfs_exit as devres action

On 2017-05-19 09:46, Mark Brown wrote: > On Mon, May 15, 2017 at 01:08:27AM -0700, Stefan Agner wrote: > >> Instead of manually cleanup regmap_debugfs_exit, use devres action >> to do the cleanup. This also works for external users of >> regmap_attach_dev. > > Why? It's also not clear to me

[RFC PATCH] vmalloc: show more detail info in vmallocinfo for clarify

When ioremap a 67112960 bytes vm_area with the vmallocinfo: [..] 0xec79b000-0xec7fa000 389120 ftl_add_mtd+0x4d0/0x754 pages=94 vmalloc 0xec80-0xecbe1000 4067328 kbox_proc_mem_write+0x104/0x1c4 phys=8b52 ioremap we get result: 0xf100-0xf5001000 67112960 devm_ioremap+0x38/0x7c

[v2 1/1] usb:host:xhci support option to disable xHCI 1.0 USB2 HW LPM

XHCI specification 1.1 does not require xHCI 1.0 compliant controllers to always enable hardware USB2 LPM. However, the current xHCI driver always enable it by setting HLE=1 when seeing HLC=1. This makes certain xHCI controllers that have broken USB2 HW LPM fail to work as there is no way to

Re: [PATCH 00/24] Thunderbolt security levels and NVM firmware upgrade

On Fri, May 19, 2017 at 05:54:37PM +, mario.limoncie...@dell.com wrote: > > > > It happens occasionally when you reboot the machine when a device is > > connected but seems to be dependent on the BIOS version. Since it is the > > BIOS who is supposed to enumerated these devices, I suspect

Re: [PATCH 2/2] ARM: dts: am335x-sl50: Fix cannot claim requested pins for spi0

On Fri, May 19, 2017 at 06:51:44PM +0200, Enric Balletbo i Serra wrote: > We don't need to bitbang these pins anymore, instead we muxed these > pins as SPI, after this change, done in commit 6c69f726, we introduced > the following error: > > pinctrl-single 44e10800.pinmux: pin PIN85 already

Re: [PATCH 1/2] ARM: dts: am335x-sl50: Fix card detect pin for mmc1

On Fri, May 19, 2017 at 06:51:43PM +0200, Enric Balletbo i Serra wrote: > The second version of the hardware moved the card detect pin from gpio0_6 > to gpio1_9, as we won't support the first hardware version fix the pinmux > configuration of this pin. > > Fixes: 8584d4fc ("ARM: dts: am335x-sl50:

[PATCH 1/1] pcmcia: remove left-over %Z format

Commit 5b5e0928f742 ("lib/vsprintf.c: remove %Z support") removed some usages of format %Z but forgot "%.2Zx". This makes clang 4.0 reports a -Wformat-extra-args warning because it does not know about %Z. Replace %Z with %z. Cc: sta...@vger.kernel.org # v4.11+ Signed-off-by: Nicolas Iooss

RE: [PATCH 00/24] Thunderbolt security levels and NVM firmware upgrade

On Fri, May 19 2017, 07:35 PM, mario.limoncie...@dell.com wrote: > Here's my setup: > System: I'm using is an XPS 9350 (Has Alpine Ridge). It's got NVM 16.0. BIOS > 1.4.13 TBT Device: Dell TB16 (which has AR in the cable and in dock - both > NVM 16.0). > Is it BIOS assist or native

Re: [GIT PULL] KVM fixes for v4.12-rc2

On 20/05/17 00:21, Linus Torvalds wrote: > So I noticed that my diffstat didn't match either the KVM or the Xen pull. > > The *reason* seems to be that both Radim and Juergen have enabled the > "patience" diff, because if I add "--patience" to the diff line, I get > the same numbers you guys

[PATCHv2 0/3] Enable no_cache flag to driver_data

From: Yi Li Changes in v2: - Rebase to Luis R. Rodriguez's 20170501-driver-data-try2 branch - Expose DRIVER_DATA_REQ_NO_CACHE flag to public driver_data_req_params structure, so upper drivers can ask driver_data driver to bypass the internal caching

[PATCHv2 1/3] firmware_class: move NO_CACHE from private to driver_data_req_params

From: Yi Li This adds DRIVER_DATA_REQ_NO_CACHE flag with .req flag under struct driver_data_req_params. When this flag is set, the driver_data driver will bypass the internal caching mechanism, its used by streaming case and other drivers which implement their own cache

[PATCHv2 1/2] firmware: Enable pre-allocated buffer support in driver_data

From: Yi Li This enables the equivalent feature of the legacy request_firmware_into_buf to driver_data, so caller can allocate and manage the firmware buffer instead of by driver_data class internally. The caller need to setup alloc_buf and alloc_buf_size in the

[PATCHv2 3/3] test: add no_cache to driver_data load tester

From: Yi Li This adds a no_cache flag to simple sync and async test. Signed-off-by: Yi Li --- lib/test_driver_data.c | 43 +++-- tools/testing/selftests/firmware/driver_data.sh | 36

[PATCHv2 0/2] Enable pre-allocated buffer support for driver_data

From: Yi Li This series enables the equivalent pre-allocated buffer feature in request_firmware_into_buf to driver_data API, so caller can allocate firmware data buffer and pass to driver_data. This will be used for streaming support of driver_data, which allow caller to

[PATCHv2 2/3] iwlwifi: use DRIVER_DATA_REQ_NO_CACHE for driver_data

From: Yi Li Set DRIVER_DATA_REQ_NO_CACHE flag to disable driver_data driver caching mechanism, iwlwifi has its own firmware cache management. Signed-off-by: Yi Li --- drivers/net/wireless/intel/iwlwifi/iwl-drv.c | 2 ++ 1 file changed, 2

Re: [PATCH v2] printk: Use the main logbuf in NMI when logbuf_lock is available

On (05/19/17 15:02), Petr Mladek wrote: > > [..] > > > > > the problem is that > > > > > > `PRINTK_NMI_CONTEXT_MASK || PRINTK_NMI_DEFERRED_CONTEXT_MASK' is 0x01 > > > > d'oh... forgot to copy-paste this... > > Grrr, thanks a lot for chasing this down and I am sorry for the troubles. no

Re: [4.12 regression] Thinkpad X250 Touchpad and Trackpoint not recognized anymore; commit e839ffa: "Input: synaptics - add support for Intertouch devices"

Hi, On May 20 2017 or thereabouts, Pascal Wichmann wrote: > > Looks like you running your patched kernel? > That's right. > > > >>> CONFIG_RMI4_CORE=m > >>> CONFIG_RMI4_I2C=m > >>> CONFIG_RMI4_SPI=m > >>> # CONFIG_RMI4_SMB is not set > > > > This is your issue I believe. > > Indeed, enabling

[PATCH 2/2] pcmcia: nsp_cs: add __printf attribute to logging functions

Adding __printf attributes helps to detect errors in printf format strings at build time. Signed-off-by: Nicolas Iooss --- drivers/scsi/pcmcia/nsp_cs.c | 6 -- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/drivers/scsi/pcmcia/nsp_cs.c

[PATCH 1/2] scsi: nsp32: add __printf attribute to logging functions

nsp32_message() and nsp32_dmessage() use printf format strings in order to format a message. Adding __printf attributes helps to detect errors in such format strings at build time, like: drivers/scsi/nsp32.c:3314:23: error: format '%ld' expects argument of type 'long int', but argument 6

RE: work queue of scsi fc transports should be serialized

On Fri, 2017-05-19 at 09:36 +, Dashi DS1 Cao wrote: > It seems there is a race of multiple "fc_starget_delete" of the same > rport, thus of the same SCSI host. The race leads to the race of > scsi_remove_target and it cannot be prevented by the code snippet > alone, even of the most recent

Re: [PATCH] firmware: google: memconsole: Prevent overrun attack on coreboot console

On Fri, May 19, 2017 at 02:44:38PM -0700, Julius Werner wrote: > The recent coreboot memory console update (firmware: google: memconsole: > Adapt to new coreboot ring buffer format) introduced a small security > issue in the driver: The new driver implementation parses the memory > console

RE: [PATCH] PCI: Make SR-IOV capable GPU working on the SR-IOV incapable platform

>-Original Message- >From: Cheng, Collins >Sent: Saturday, May 20, 2017 12:53 AM >To: Alexander Duyck; Alex Williamson >Cc: Bjorn Helgaas; linux-...@vger.kernel.org; linux-kernel@vger.kernel.org; >Deucher, Alexander; Zytaruk, Kelly; Yinghai Lu >Subject: RE: [PATCH] PCI: Make SR-IOV

Re: [PATCH] lpfc: nvmet_fc: fix format string

On Fri, 2017-05-19 at 10:04 +0200, Arnd Bergmann wrote: > The lpfc_nvmeio_data() tracing helper always takes a format string and > three additional arguments. No it doesn't. It takes a format and arguments. I don't disagree with the patch, just the characterization of the lpfc_mvmeio_data call

Re: [PATCH] net: sched: fix a use-after-free error on chain on the error exit path

Fri, May 19, 2017 at 07:17:59PM CEST, xiyou.wangc...@gmail.com wrote: >On Thu, May 18, 2017 at 7:07 AM, Colin King wrote: >> diff --git a/net/sched/cls_api.c b/net/sched/cls_api.c >> index 4020b8d932a1..82ebdc3fcb2e 100644 >> --- a/net/sched/cls_api.c >> +++

[PATCH] modpost: abort if a module name is too long

From: Wanlong Gao Module name has a limited length, but currently the build system allows the build finishing even if the module name is too long. CC /root/kprobe_example/abcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyz.mod.o

[PATCH 1/1] genksyms: add printf format attribute to error_with_pos()

When compiling with -Wsuggest-attribute=format in HOSTCFLAGS, gcc complains that error_with_pos() may be declared with a printf format attribute: scripts/genksyms/genksyms.c:726:3: warning: function might be possible candidate for ‘gnu_printf’ format attribute

[PATCHv2 2/2] test: add pre-allocated buffer to driver_data tester

From: Yi Li This adds pre-allocated buffer test cases to the simple sync and async test. Signed-off-by: Yi Li --- lib/test_driver_data.c | 68 - tools/testing/selftests/firmware/driver_data.sh |

[PATCHv2 2/3] test: add streaming test to driver_data tester

From: Yi Li This adds streaming test case, which pre-allocate the buffer and ask driver_data_request_sync API to read 4KB each. Since the dummy firmware image is very small, the test only stream couple bytes. A manual test method: echo -n 'bigfile' >

[PATCHv2 0/3] Add streaming support to driver_data API

From: Yi Li This series enables the streaming support on driver_data sync API and add self test and FPGA mgr to test/use stream firmware in 4KB trucks. Changes in v2: - Rebase to Luis R. Rodriguez's 20170501-driver-data-try2 branch - Expended

[PATCHv2 1/3] firmware: Add streaming support for driver_data_request_sync API

From: Yi Li By setting the driver_data_req_params req flag of DRIVER_DATA_REQ_STREAMING and DRIVER_DATA_REQ_NO_CACHE, caller can streaming firmware image to the pre-allocated buffer in small trunks. Caller also need to setup the img_offset pointer and firmware image

[PATCHv2 3/3] fpga_mgr: Add streaming support through the new driver_data API

From: Yi Li Since the FPGA image are getting bigger in size, this add an new API fpga_mgr_firmware_stream in FPGA manager, which will stream FPGA image in 4KB trunks. Signed-off-by: Yi Li --- drivers/fpga/fpga-mgr.c | 111

Re: [patch 2/2] MM: allow per-cpu vmstat_threshold and vmstat_worker configuration

On Fri, May 19, 2017 at 12:13:26PM -0500, Christoph Lameter wrote: > On Fri, 19 May 2017, Marcelo Tosatti wrote: > > > Use-case: realtime application on an isolated core which for some reason > > updates vmstatistics. > > Ok that is already only happening every 2 seconds by default and that >

Re: [kernel-hardening] [PATCH 1/1] Sealable memory support

On Fri, May 19, 2017 at 01:38:11PM +0300, Igor Stoppa wrote: > Dynamically allocated variables can be made read only, > after they have been initialized, provided that they reside in memory > pages devoid of any RW data. > > The implementation supplies means to create independent pools of memory,

[PATCH 0/2] Enhance libsas hotplug feature

Now the libsas hotplug has some issues, Dan Williams report a similar bug here before https://www.mail-archive.com/linux-scsi@vger.kernel.org/msg39187.html The issues we have found 1. if LLDD burst reports lots of phy-up/phy-down sas events, some events may lost because a same sas events is

[PATCH 1/2] libsas: Don't process sas events in static works

Now libsas hotplug work is static, LLDD driver queue the hotplug work into shost->work_q. If LLDD driver burst post lots hotplug events to libsas, the hotplug events may pending in the workqueue like shost->work_q new work[PORTE_BYTES_DMAED] --> |[PHYE_LOSS_OF_SIGNAL][PORTE_BYTES_DMAED] ->

Re: [PATCH BUGFIX] block, bfq: access and cache blkg data only when safe

> Il giorno 19 mag 2017, alle ore 16:54, Tejun Heo ha scritto: > > Hello, Paolo. > > On Fri, May 19, 2017 at 10:39:08AM +0200, Paolo Valente wrote: >> Operations on blkg objects in blk-cgroup are protected with the >> request_queue lock, which is no more the lock that protects

Re: [PATCH] mm: clarify why we want kmalloc before falling backto vmallock

On Fri 19-05-17 17:46:58, John Hubbard wrote: > On 05/17/2017 01:09 AM, Michal Hocko wrote: > >From: Michal Hocko > > > >While converting drm_[cm]alloc* helpers to kvmalloc* variants Chris > >Wilson has wondered why we want to try kmalloc before vmalloc fallback > >even for

Re: Widespread crashes in -next, bisected to 'mm: drop HASH_ADAPT'

On Fri 19-05-17 09:46:23, Guenter Roeck wrote: > Hi, > > my qemu tests of next-20170519 show the following results: > total: 122 pass: 30 fail: 92 > > I won't bother listing all of the failures; they are available at > http://kerneltests.org/builders. I bisected one (openrisc, because > it

[PATCH 1/1] printk: add __printf attributes to internal functions

When compiling with -Wsuggest-attribute=format, gcc complains that some functions in kernel/printk/printk_safe.c transmit their argument to printf-like functions without having a printf attribute. Silence these warnings by adding relevant __printf attributes. Signed-off-by: Nicolas Iooss

RE: [PATCH] PCI: Make SR-IOV capable GPU working on the SR-IOV incapable platform

Hi Kelly, This issue also happens in "not SR-IOV capable" SBIOS. It seems some "not SR-IOV capable" SBIOS will directly report error in system BIOS boot stage and doesn't boot to OS. But other "not SR-IOV capable" SBIOS would not report error and boot to Linux. -Collins Cheng -Original

[PATCH] slub/memcg: Cure the brainless abuse of sysfs attributes

memcg_propagate_slab_attrs() abuses the sysfs attribute file functions to propagate settings from the root kmem_cache to a newly created kmem_cache. It does that with: attr->show(root, buf); attr->store(new, buf, strlen(bug); Aside of being a lazy and absurd hackery this is broken

Linux 3.18.54

I'm announcing the release of the 3.18.54 kernel. All users of the 3.18 kernel series must upgrade. The updated 3.18.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-3.18.y and can be browsed at the normal kernel.org git web

Re: Linux 3.18.54

diff --git a/Makefile b/Makefile index 274ec43fc6ba..f44ed53ab175 100644 --- a/Makefile +++ b/Makefile @@ -1,6 +1,6 @@ VERSION = 3 PATCHLEVEL = 18 -SUBLEVEL = 53 +SUBLEVEL = 54 EXTRAVERSION = NAME = Diseased Newt diff --git a/arch/arm64/kernel/perf_event.c b/arch/arm64/kernel/perf_event.c

[PATCH v2 1/5] crypto : stm32 - Add STM32F4 CRC32 support

This patch adds CRC (CRC32 Crypto) support for STM32F4 series. As an hardware limitation polynomial and key setting are not supported. They are fixed as 0x4C11DB7 (poly) and 0x (key). CRC32C Castagnoli algorithm is not used. Signed-off-by: Cosar Dindar ---

[PATCH v2 2/5] dt-bindings : Document the STM32F4 CRC32 binding

Add device tree binding for STM32F4. Signed-off-by: Cosar Dindar --- Documentation/devicetree/bindings/crypto/st,stm32-crc.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Documentation/devicetree/bindings/crypto/st,stm32-crc.txt

[PATCH v2 0/5] Add support for the STM32F4 CRC32

This patch series add hardware CRC32 ("Ethernet") calculation support for STMicroelectronics STM32F429. Polynomial and key setting are not supported, key is fixed as 0x4C11DB7 and poly is 0x. Module is tested on STM32F429-disco board with crypto testmgr using cases within the key

[GIT PULL REQUEST] watchdog - v4.12-rc1 Fixes

Hi Linus, Please pull from 'master' branch of git://www.linux-watchdog.org/linux-watchdog.git It will fix: * orion_wdt compile-test dependencies * sama5d4_wdt: WDDIS handling and a race confition * pcwd_usb: fix NULL-deref at probe * cadence_wdt: fix timeout setting * wdt_pci: fix build

[GIT PULL] Char/Misc driver fixes for 4.12-rc2

The following changes since commit 2ea659a9ef488125eb46da6eb571de5eae5c43f6: Linux 4.12-rc1 (2017-05-13 13:19:49 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git/ tags/char-misc-4.12-rc2 for you to fetch changes up to

[PATCH] pinctrl: single: use of_device_get_match_data() to get soc data

Use of_device_get_match_data() instead of of_match_device(). It allows us to remove the forward declaration of pcs_of_match. Signed-off-by: Masahiro Yamada --- drivers/pinctrl/pinctrl-single.c | 8 ++-- 1 file changed, 2 insertions(+), 6 deletions(-) diff

Re: [PATCH 4/4] iio: hi8435: cleanup reset gpio

On 19/05/17 15:48, Nikita Yushchenko wrote: Reset GPIO is active low. Currently driver uses gpiod_set_value(1) to clean reset, which depends on device tree to contain GPIO_ACTIVE_HIGH - that does not match reality. This fixes driver to use _raw version of gpiod_set_value() to enforce

Re: Widespread crashes in -next, bisected to 'mm: drop HASH_ADAPT'

The problem is due to 32-bit integer overflow in: ADAPT_SCALE_BASE and adapt In dcache_init_early() that is causing the problem. It was not enabled before 'mm: drop HASH_ADAPT' but is enabled now, and it should follow right after: "PID hash table entries: 1024 (order: 0, 4096 bytes)" main()

[PATCH kernel.org] 4.10 is now end-of-life

Properly mark 4.10 as being EOL on the website. Signed-off-by: Greg Kroah-Hartman diff --git a/pelicanconf.py b/pelicanconf.py index d0ec28210bc9..dbfe46b637bb 100644 --- a/pelicanconf.py +++ b/pelicanconf.py @@ -26,7 +26,7 @@ sys.path.append('./') from plugins

Re: [PATCH v2 00/18] ARM64: meson: DT cleanups

Am 15.05.2017 um 22:24 schrieb Martin Blumenstingl: > On Mon, May 15, 2017 at 9:10 PM, Andreas Färber wrote: >> Hi Neil, >> >> Am 15.05.2017 um 10:16 schrieb Neil Armstrong: >>> Hi Andreas, >>> >>> On 05/13/2017 04:33 PM, Andreas Färber wrote: Hello Kevin, This

CHIPPro NAND issue with 4.12 rc1

Hi All, I'm trying to boot a CHIPPro with the stock 4.12 rc1 kernel. If I make no modifications to the sun5i-gr8-chip-pro.dtb the kernel boots but can't find the root partition. So I added the partitions to the dts file diff --git a/arch/arm/boot/dts/sun5i-gr8-chip-pro.dts

Re: [PATCH v2 00/18] ARM64: meson: DT cleanups

Hi Kevin, Am 17.05.2017 um 23:46 schrieb Kevin Hilman: > Andreas Färber writes: >> This series fixes several cosmetic issues, on top of your for-next branch. >> >> Patches 3-6 rename a node, the rest should all be non-functional changes. >> >> PLEASE STOP merging random new

Re: [PATCH 3/4] iio: hi8435: make in_voltage_sensing_mode_available visible

On 19/05/17 15:48, Nikita Yushchenko wrote: Possible values of sensing_mode are encoded with strings and actual atrings used are not obvious. strings Provide a hint by enabling in_voltage_sensing_mode_available attribute. Signed-off-by: Nikita Yushchenko

Re: [PATCH 2/4] iio: hi8435: avoid garbage event at first enable

On 19/05/17 15:48, Nikita Yushchenko wrote: Currently, driver generates events for channels if new reading differs from previous one. This "previous value" is initialized to zero, which results into event if value is constant-one. Fix that by initializing "previous value" by reading at event

Re: [PATCH-RFT 2/2] pinctrl: samsung: Split Exynos drivers per ARMv7 and ARMv8

On Tue, May 16, 2017 at 10:06 PM, Krzysztof Kozlowski wrote: > Exynos pinctrl drivers contain pretty big per-SoC data structures. The > pinctrl-exynos object file contained code and data for both ARMv7 and > ARMv8 SoCs thus it grew big. There will not be a shared image between

Re: [PATCH] drm/stm: add COMPILE_TEST to Kconfig (fwd)

Hi Philippe, 2017-05-19 21:17 GMT+09:00 Philippe CORNU : > > > On 05/19/2017 09:49 AM, Julia Lawall wrote: >> On line 466, the preceeding comment suggests that the second constant >> should start with VS rather than HS again. >> >> julia >> >> -- Forwarded message

Re: [PATCH v4 2/2] tpm: vtpm_proxy: Implement request_locality function.

On Mon, May 15, 2017 at 11:56:51AM -0400, Stefan Berger wrote: > On 05/15/2017 08:41 AM, Jarkko Sakkinen wrote: > > On Wed, May 10, 2017 at 07:54:22PM -0400, Stefan Berger wrote: > > > Implement the request_locality function. To set the locality on the > > > backend we define vendor-specific TPM

Re: [PATCH v2 1/5] tpm: introduce tpm_pcr_algorithms()

On Mon, May 15, 2017 at 03:18:41PM +0200, Roberto Sassu wrote: > > > On 5/15/2017 12:36 PM, Jarkko Sakkinen wrote: > > On Fri, May 05, 2017 at 04:21:48PM +0200, Roberto Sassu wrote: > > > This function allows TPM users to know which algorithms the TPM supports. > > > It stores the algorithms in

Re: Linux 4.9.29

diff --git a/Makefile b/Makefile index 9460a63087b8..c12e501a18b8 100644 --- a/Makefile +++ b/Makefile @@ -1,6 +1,6 @@ VERSION = 4 PATCHLEVEL = 9 -SUBLEVEL = 28 +SUBLEVEL = 29 EXTRAVERSION = NAME = Roaring Lionus diff --git a/arch/arm/kvm/psci.c b/arch/arm/kvm/psci.c index

Re: Linux 4.10.17

diff --git a/Makefile b/Makefile index e3e60e71fa78..2e8b04bd180e 100644 --- a/Makefile +++ b/Makefile @@ -1,6 +1,6 @@ VERSION = 4 PATCHLEVEL = 10 -SUBLEVEL = 16 +SUBLEVEL = 17 EXTRAVERSION = NAME = Fearless Coyote diff --git a/arch/arm/kvm/psci.c b/arch/arm/kvm/psci.c index

[PATCH] input: move gpio mouse to managed api

Signed-off-by: Bram Vlerick --- drivers/input/mouse/gpio_mouse.c | 8 ++-- 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/drivers/input/mouse/gpio_mouse.c b/drivers/input/mouse/gpio_mouse.c index ced07391304b..2fc8ddaf0175 100644 ---

Linux 4.11.2

I'm announcing the release of the 4.11.2 kernel. All users of the 4.11 kernel series must upgrade. The updated 4.11.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.11.y and can be browsed at the normal kernel.org git web browser:

Re: [PATCH] slub/memcg: Cure the brainless abuse of sysfs attributes

On Sat, 20 May 2017 06:16:45 -0700 Christoph Hellwig wrote: > On Sat, May 20, 2017 at 12:52:03PM +0200, Thomas Gleixner wrote: > > This should be rewritten proper by adding a propagate() callback to those > > slub_attributes which must be propagated and avoid that insane

Re: [PATCH 1/1] xilinx ps uart: Adding a kernel parameter for the number of xilinx ps uarts

On Fri, 19 May 2017 20:21:54 -0600 Sam Povilus wrote: > The number of xilinx ps uart should be set by a kernel parameter instead of > using a #define. This allows the user to set the number of xilinx ps uart > using only kconfig and not modifying kernel source. > >

Re: [PATCH 7/7] DWARF: add the config option

On Fri, May 19, 2017 at 10:23:53PM -0700, Andy Lutomirski wrote: > On Fri, May 19, 2017 at 2:35 PM, Josh Poimboeuf wrote: > > On Fri, May 19, 2017 at 04:29:13PM -0500, Josh Poimboeuf wrote: > >> > How are you handling control flow? > >> > >> Control flow of what? > >> > >> >

Re: [4.12 regression] Thinkpad X250 Touchpad and Trackpoint not recognized anymore; commit e839ffa: "Input: synaptics - add support for Intertouch devices"

On Sat, May 20, 2017 at 11:59:50AM +0200, Benjamin Tissoires wrote: > Hi, > > On May 20 2017 or thereabouts, Pascal Wichmann wrote: > > > Looks like you running your patched kernel? > > That's right. > > > > > > >>> CONFIG_RMI4_CORE=m > > >>> CONFIG_RMI4_I2C=m > > >>> CONFIG_RMI4_SPI=m > > >>>

[PATCH] usb: remove NULL pointer check for clk_disable_unprepare

After long term efforts of fixing non-common clock implementations, clk_disable() is a no-op for a NULL pointer input, and this is now tree-wide consistent. All clock consumers can safely call clk_disable(_unprepare) without NULL pointer check. Signed-off-by: Masahiro Yamada

Re: [PATCH v3] staging: iio: light: Replace symbolic permissions as per coding style

On 19/05/17 10:37, surenderpols...@gmail.com wrote: From: Surender Polsani Fixed the following checkpatch.pl warnings: octal permissions are more preferable than symbolic permissions Replaced DEVICE_ATTR family macros with DEVICE_ATTR_RW family as suggested by Greg

RE: [PATCH] PCI: Make SR-IOV capable GPU working on the SR-IOV incapable platform

Collins, Okay, good to know. Is there a common solution that can handle all cases? Thanks, Kelly >-Original Message- >From: Cheng, Collins >Sent: Saturday, May 20, 2017 6:38 AM >To: Zytaruk, Kelly; Alexander Duyck; Alex Williamson >Cc: Bjorn Helgaas; linux-...@vger.kernel.org;

[PATCH 0/2] vhost/scsi: Adjustments for five function implementations

From: Markus Elfring Date: Sat, 20 May 2017 16:25:04 +0200 A few update suggestions were taken into account from static source code analysis. Markus Elfring (2): Improve a size determination in four functions Delete error messages for failed memory allocations

[PATCH 1/2] vhost/scsi: Improve a size determination in four functions

From: Markus Elfring Date: Sat, 20 May 2017 13:48:44 +0200 Replace the specification of four data structures by pointer dereferences as the parameter for the operator "sizeof" to make the corresponding size determination a bit safer according to the Linux coding

Re: linux-next: stats (Was: Linux 4.12-rc1)

Hi Stephen, On Tue, May 16, 2017 at 07:32:09AM +1000, Stephen Rothwell wrote: > On Mon, 15 May 2017 16:51:08 +0200 Sebastian Reichel wrote: > > On Mon, May 15, 2017 at 11:15:50PM +1000, Stephen Rothwell wrote: > > > There are also 288 commits in next-20170502 that didn't make it

Re: [PATCH 1/4] iio: hi8435: add raw access

On 19/05/17 15:47, Nikita Yushchenko wrote: With current event-only driver, it is not possible for user space application to know current senses if they don't change since application starts. Address that by adding raw access to channels. Signed-off-by: Nikita Yushchenko

Re: [PATCHv2] watchdog: core: add option to avoid early handling of watchdog

Hi, On Tue, May 16, 2017 at 12:08:32AM +0200, Rasmus Villemoes wrote: > On Sun, May 14 2017, Guenter Roeck wrote: > > > On 05/12/2017 05:05 AM, Sebastian Reichel wrote: > >> On some systems its desirable to have watchdog reboot the system > >> when it does not come up fast enough. This adds a

[PATCH RFC] perf/callchain: fixup charset file header

Non-UTF-8 characters are a problem for some terminals and also make greping harder than necessary - this only switches the copyright sign to the common (C). Reported-by: Markus Kreidl Signed-off-by: Nicholas Mc Guire --- Found by checkpatch --strict:

[PATCH] staging: vt6655: add spaces around '%' operator

Fix checkpatch issue by adding spaces around the '%' operator Signed-off-by: Marko Stankovic --- drivers/staging/vt6655/card.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/vt6655/card.c b/drivers/staging/vt6655/card.c index

Re: [REGRESSION] Failed network caused by: xhci: switch to pci_alloc_irq_vectors

On Fri, May 19, 2017 at 5:46 AM, Christoph Hellwig wrote: > > diff --git a/include/linux/pci.h b/include/linux/pci.h > index 33c2b0b77429..5a7fd3b6a7b9 100644 > --- a/include/linux/pci.h > +++ b/include/linux/pci.h > @@ -1342,7 +1342,7 @@ pci_alloc_irq_vectors_affinity(struct pci_dev

[PATCH v2] PCI/msi: fix the pci_alloc_irq_vectors_affinity stub

We need to return an error for any call that asks for MSI / MSI-X vectors only, so that non-trivial fallback logic can work properly. Also valid dev->irq and use the "correct" errno value based on feedback from Linus. Signed-off-by: Christoph Hellwig Reported-by: Steven Rostedt

[PATCH] ASoC: remove NULL pointer check for clk_disable_unprepare

After long term efforts of fixing non-common clock implementations, clk_disable() is a no-op for a NULL pointer input, and this is now tree-wide consistent. All clock consumers can safely call clk_disable(_unprepare) without NULL pointer check. Signed-off-by: Masahiro Yamada

[PATCH] serial: of_serial: remove NULL pointer check for clk_disable_unprepare

After long term efforts of fixing non-common clock implementations, clk_disable() is a no-op for a NULL pointer input, and this is now tree-wide consistent. All clock consumers can safely call clk_disable(_unprepare) without NULL pointer check. Signed-off-by: Masahiro Yamada

Re: [PATCH] ASoC: remove NULL pointer check for clk_disable_unprepare

On Sun, May 21, 2017 at 02:42:38AM +0900, Masahiro Yamada wrote: > After long term efforts of fixing non-common clock implementations, > clk_disable() is a no-op for a NULL pointer input, and this is now > tree-wide consistent. > > All clock consumers can safely call clk_disable(_unprepare)

Re: [PATCH 1/2] scsi: nsp32: add __printf attribute to logging functions

On Sat, 2017-05-20 at 13:16 +0200, Nicolas Iooss wrote: > nsp32_message() and nsp32_dmessage() use printf format strings in order > to format a message. Adding __printf attributes helps to detect errors > in such format strings at build time, like: > > drivers/scsi/nsp32.c:3314:23: error:

Re: [PATCH v2 1/5] tpm: introduce tpm_pcr_algorithms()

On Wed, May 17, 2017 at 10:42:35AM +0200, Roberto Sassu wrote: > On 5/15/2017 3:18 PM, Roberto Sassu wrote: > > > > > > On 5/15/2017 12:36 PM, Jarkko Sakkinen wrote: > > > On Fri, May 05, 2017 at 04:21:48PM +0200, Roberto Sassu wrote: > > > > This function allows TPM users to know which

Re: Widespread crashes in -next, bisected to 'mm: drop HASH_ADAPT'

On 05/20/2017 12:26 AM, Michal Hocko wrote: On Fri 19-05-17 09:46:23, Guenter Roeck wrote: Hi, my qemu tests of next-20170519 show the following results: total: 122 pass: 30 fail: 92 I won't bother listing all of the failures; they are available at http://kerneltests.org/builders. I

Re: [PATCH-RFT 2/2] pinctrl: samsung: Split Exynos drivers per ARMv7 and ARMv8

On Sat, May 20, 2017 at 07:12:13PM +0200, Linus Walleij wrote: > On Tue, May 16, 2017 at 10:06 PM, Krzysztof Kozlowski wrote: > > > Exynos pinctrl drivers contain pretty big per-SoC data structures. The > > pinctrl-exynos object file contained code and data for both ARMv7 and >

Re: [PATCH 5/5] iio: adc: stm32: add support for STM32H7

On 19/05/17 13:45, Fabrice Gasnier wrote: Add support for STM32H7 Analog to Digital Converter. It has up to 20 external channels, resolution ranges from 8 to 16bits. Either bus or asynchronous adc clock may be used. Add registers & bitfields definition. Also add new configuration options to

[PATCH] drm: remove NULL pointer check for clk_disable_unprepare

After long term efforts of fixing non-common clock implementations, clk_disable() is a no-op for a NULL pointer input, and this is now tree-wide consistent. All clock consumers can safely call clk_disable(_unprepare) without NULL pointer check. Signed-off-by: Masahiro Yamada

[PATCH 5/5] Staging: rtl8712: ieee80211: fixed camelcase coding style issue

Fixed coding style issue Renamed cap_ShortPremble to cap_short_premble Signed-off-by: Jaya Durga --- drivers/staging/rtl8712/ieee80211.c | 2 +- drivers/staging/rtl8712/wifi.h | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git

Re: Linux 4.4.69

diff --git a/Makefile b/Makefile index e6c7990497e7..dc5df61ea4be 100644 --- a/Makefile +++ b/Makefile @@ -1,6 +1,6 @@ VERSION = 4 PATCHLEVEL = 4 -SUBLEVEL = 68 +SUBLEVEL = 69 EXTRAVERSION = NAME = Blurry Fish Butt diff --git a/arch/arm/kvm/psci.c b/arch/arm/kvm/psci.c index

Linux 4.10.17

-- Note, this is the LAST 4.10.y kernel to be released, it is now end-of-life. You must move to the 4.11.y kernel series now. -- I'm announcing the release of the 4.10.17 kernel. All users of the 4.10 kernel series must upgrade. The updated 4.10.y git tree can

Linux 4.9.29

I'm announcing the release of the 4.9.29 kernel. All users of the 4.9 kernel series must upgrade. The updated 4.9.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.9.y and can be browsed at the normal kernel.org git web browser:

Linux 4.4.69

I'm announcing the release of the 4.4.69 kernel. All users of the 4.4 kernel series must upgrade. The updated 4.4.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.4.y and can be browsed at the normal kernel.org git web browser:

[PATCH 2/2] vhost/scsi: Delete error messages for failed memory allocations in five functions

From: Markus Elfring Date: Sat, 20 May 2017 15:50:30 +0200 Omit seven extra messages for memory allocation failures in these functions. This issue was detected by using the Coccinelle software. Link:

Re: [PATCH v2 0/3] Cleanup evergreen/si IRQ handling code

Am 20.05.2017 um 01:48 schrieb Lyude: This is the first part of me going through and cleaning up the IRQ handling code for radeon, since after taking a look at it the other day while trying to debug something I realized basically all of the code was copy pasted everywhere, and quite difficult to

  1   2   3   4   5   >