Re: 4.3 regression: task_work corruption in vm86 mode?

On Fri, Oct 30, 2015 at 6:44 PM, Andy Lutomirski wrote: > Hi all- > > In 4.3-rc7, running dosemu2 (https://github.com/stsp/dosemu2/) oopses > the system very quickly, as long as CONFIG_VM86=y. It blows up > because snd_seq_delete_port walks ports_list_head, finds two valid > ports, and then

[PATCH urgent 2/2] x86/vm86: Set thread.vm86 to NULL on fork/clone

thread.vm86 points to per-task information -- the pointer should not be copied on clone. Fixes: d4ce0f26c790 ("x86/vm86: Move fields from 'struct kernel_vm86_struct' to 'struct vm86'") Signed-off-by: Andy Lutomirski --- arch/x86/kernel/process.c | 3 +++ 1 file changed, 3 insertions(+) diff

[PATCH urgent 0/2] x86: vm86 fix and test

Calling vm86 and then forking will corrupt things. Fix it. This is for x86/urgent. It fixes a 4.3 regression. Andy Lutomirski (2): selftests/x86: Add a fork() to entry_from_vm86 to catch fork bugs x86/vm86: Set thread.vm86 to NULL on fork/clone arch/x86/kernel/process.c

[PATCH urgent 1/2] selftests/x86: Add a fork() to entry_from_vm86 to catch fork bugs

Mere possession of vm86 state is strange. Make sure that nothing gets corrupted if we fork after calling vm86(). Signed-off-by: Andy Lutomirski --- tools/testing/selftests/x86/entry_from_vm86.c | 4 1 file changed, 4 insertions(+) diff --git

Re: [PATCH 11/12] usb: serial: usb_debug: add support for dbc debug device

On 10/30/2015 10:41 PM, Greg Kroah-Hartman wrote: On Fri, Oct 30, 2015 at 07:46:45PM +0800, Lu, Baolu wrote: On 10/28/2015 08:33 PM, Greg Kroah-Hartman wrote: On Wed, Oct 28, 2015 at 04:00:42PM +0800, Lu Baolu wrote: This patch add dbc debug device support in usb_debug driver.

Re: [PATCH 10/31] perf test: Enforce LLVM test for BPF test

On 2015/10/30 6:37, Arnaldo Carvalho de Melo wrote: Em Wed, Oct 14, 2015 at 12:41:21PM +, Wang Nan escreveu: This patch replaces the original toy BPF program with previous introduced bpf-script-example.c. Dynamically embedded it into 'llvm-src.c'. The newly introduced BPF program

Re: [PATCH] mm/hugetlbfs Fix bugs in fallocate hole punch of areas with holes

> > Hugh Dickins pointed out problems with the new hugetlbfs fallocate > hole punch code. These problems are in the routine remove_inode_hugepages > and mostly occur in the case where there are holes in the range of > pages to be removed. These holes could be the result of a previous hole >

Re: [PATCH v4 1/6] virtio-net: Stop doing DMA from the stack

On Fri, Oct 30, 2015 at 6:55 AM, Christian Borntraeger wrote: > Am 30.10.2015 um 02:09 schrieb Andy Lutomirski: >> From: "Michael S. Tsirkin" >> >> Once virtio starts using the DMA API, we won't be able to safely DMA >> from the stack. virtio-net does a couple of config DMA requests >> from

Re: [PATCH 2/2] dma: add Qualcomm Technologies HIDMA channel driver

On 10/30/2015 10:50 AM, Mark Rutland wrote: The documentation above didn't state this was an 8-bit quantity, and you save nothing by doing this (all values in the binary format are padded to 4-byte alignment). done. -- Sinan Kaya Qualcomm Technologies, Inc. on behalf of Qualcomm Innovation

Re: [PATCH] Revert "h8300: clocksource"

On Fri, 30 Oct 2015 20:48:52 +0900, Daniel Lezcano wrote: > > On 10/30/2015 12:19 PM, Arnd Bergmann wrote: > > On Friday 30 October 2015 11:26:08 Daniel Lezcano wrote: > >> This reverts commit 618b902d8c098f2fff188119da7b3184c4bc5483. > > [ ... ] > > > I found that Yoshinori Sato has always

Re: [RFC 1/3] mm, oom: refactor oom detection

> On Fri 30-10-15 09:36:26, Michal Hocko wrote: > > On Fri 30-10-15 12:10:15, Hillf Danton wrote: > > [...] > > > > + for_each_zone_zonelist_nodemask(zone, z, ac->zonelist, > > > > ac->high_zoneidx, ac->nodemask) { > > > > + unsigned long free = zone_page_state(zone, > > > >

[PATCH] livepatch: old_name@old_addr scheme in livepatch sysfs directory

The following directory structure will allow for cases when the same function name exists in a single object. /sys/kernel/livepatch/// An example of this issue is documented here: https://github.com/dynup/kpatch/issues/493 Signed-off-by: Chris J Arges ---

[GIT PULL] SCSI fixes for 4.3-rc4

This is three essential bug fixes for various SCSI parts. The only affected users are SCSI multi-path via device handler (basically all the enterprise) and mvsas users. The dh bugs are an async entanglement in boot resulting in a serious WARN_ON trip and a use after free on remove leading to a

[PATCH v2 09/11] mtd: drop unnecessary partition parser data

We should assign the MTD dev.of_node instead of the parser data field. This gets us the equivalent partition parser behavior with fewer special fields and parameter passing. Also convert several of these to mtd_device_register(), since we don't need the 2nd and 3rd parameters anymore.

[PATCH v2 11/11] mtd: physmap_of: assign parent for the concatenated MTD

If there is more than one map region for this device, then the concatenated MTD will not have a parent device assigned to it -- only the sub-devices (which are not actually registered with the framework) will have their parents assigned. Let's assign the concatenated device correctly.

[PATCH v2 08/11] mtd: spi-nor: drop flash_node field

We can just alias to the MTD of_node. Signed-off-by: Brian Norris --- v2: new drivers/mtd/spi-nor/spi-nor.c | 1 - include/linux/mtd/spi-nor.h | 6 ++ 2 files changed, 2 insertions(+), 5 deletions(-) diff --git a/drivers/mtd/spi-nor/spi-nor.c b/drivers/mtd/spi-nor/spi-nor.c index

[PATCH v2 10/11] mtd: ofpart: drop 'of_node' partition parser data

This field is no longer used anywhere, as it is superseded by mtd->dev.of_node. Signed-off-by: Brian Norris --- v2: use new helpers drivers/mtd/ofpart.c | 14 -- include/linux/mtd/partitions.h | 4 2 files changed, 4 insertions(+), 14 deletions(-) diff --git

[PATCH v2 02/11] mtd: ofpart: grab device tree node directly from master device node

It seems more logical to use a device node directly associated with the MTD master device (i.e., mtd->dev.of_node field) rather than requiring auxiliary partition parser information to be passed in by the driver in a separate struct. This patch supports the mtd->dev.of_node field and deprecates

[PATCH v2 00/11] mtd: migrate 'of_node' handling to core, not in mtd_part_parser_data

Hi, I noticed that, for MTD drivers that want to support DT partition parsing (essentially all recent ones), it's a bit awkward to set the tell MTD which DT node to use. I also noticed that this info is duplicated in a few places; namely, some sub-subsystems (like SPI NOR and NAND) need their own

[PATCH v2 05/11] mtd: spi-nor: convert to spi_nor_{get,set}_flash_node()

Used semantic patch with 'make coccicheck MODE=patch COCCI=script.cocci': ---8< virtual patch @@ struct spi_nor b; struct spi_nor *c; expression d; @@ ( -(b).flash_node = (d) +spi_nor_set_flash_node(, d) | -(c)->flash_node = (d) +spi_nor_set_flash_node(c, d) ) ---8< And a manual

[PATCH v2 01/11] mtd: add get/set of_node/flash_node helpers

We are going to begin using the mtd->dev.of_node field for MTD device nodes, so let's add helpers for it. Also, we'll be making some conversions on spi_nor (and nand_chip eventually) too, so get that ready with their own helpers. Signed-off-by: Brian Norris --- v2: new include/linux/mtd/mtd.h

[PATCH v2 04/11] mtd: nand: convert to nand_set_flash_node()

Used semantic patch with 'make coccicheck MODE=patch COCCI=script.cocci': ---8< virtual patch @@ struct nand_chip *c; struct device_node *d; @@ -(c)->flash_node = (d) +nand_set_flash_node(c, d) ---8< Signed-off-by: Brian Norris --- v2: new drivers/mtd/nand/brcmnand/brcmnand.c | 2 +-

[PATCH v2 03/11] mtd: {nand,spi-nor}: assign MTD of_node

We should pass along our flash DT node to the MTD layer, so it can set up ofpart for us. Signed-off-by: Brian Norris --- v2: split out of the previous patch drivers/mtd/nand/nand_base.c | 3 +++ drivers/mtd/spi-nor/spi-nor.c | 1 + 2 files changed, 4 insertions(+) diff --git

[PATCH v2 06/11] mtd: nand: drop unnecessary partition parser data

All of these drivers set up a parser data struct just to communicate DT partition data. This field has been deprecated and is instead supported by telling nand_scan_ident() about the 'flash_node'. This patch: * sets chip->flash_node for those drivers that didn't already (but used OF

[PATCH v2 07/11] mtd: spi-nor: drop unnecessary partition parser data

Now that the SPI-NOR/MTD framework pass the 'flash_node' through to the partition parsing code, we don't have to do it ourselves. Also convert to mtd_device_register(), since we don't need the 2nd and 3rd parameters anymore. Signed-off-by: Brian Norris --- v2: no change

Re: [PATCH 1/2] dma: add Qualcomm Technologies HIDMA management driver

Hi Andy, On 10/30/2015 04:15 PM, Andy Shevchenko wrote: > On Fri, Oct 30, 2015 at 10:08 PM, Al Stone wrote: >> On 10/30/2015 01:01 PM, Mark Rutland wrote: >>> On Fri, Oct 30, 2015 at 02:48:06PM -0400, Sinan Kaya wrote: > >>> The CSRT is listed under "Want", not "Never" or "Don't Care", so

Re: [PATCH v8 09/17] dt-bindings: add document for rockchip variant of analogix_dp

Hi Rob, On 10/31/2015 12:46 AM, Rob Herring wrote: On Wed, Oct 28, 2015 at 3:28 AM, Yakir Yang wrote: Rockchip DP driver is a helper driver of analogix_dp coder driver, so most of the DT property should be descriped in analogix_dp document. Reviewed-by: Heiko Stuebner Signed-off-by: Yakir

Re: [PATCH v8 11/17] dt-bindings: add document for rockchip dp phy

On 10/31/2015 12:42 AM, Rob Herring wrote: On Wed, Oct 28, 2015 at 3:31 AM, Yakir Yang wrote: Add dt binding documentation for rockchip display port PHY. Reviewed-by: Heiko Stuebner Signed-off-by: Yakir Yang Acked-by: Rob Herring Thanks, - Yakir --- Changes in v8: - Remove the

(IPVN) EuP/FRBWDC/EcB-3109/2015,

European Parliament 36 St Peter's St, London N1 8JT, United Kingdom. In consideration of the legislative resolution reached by the European Parliament in conjunctions with the European Central Bank on financial and allied matters,following eries of complaints and petitions received from the

Re: [PATCH 0/3] PM, vfs: use filesystem freezing instead of kthread freezer

On Friday, October 30, 2015 10:17:54 PM Jiri Kosina wrote: > On Fri, 30 Oct 2015, Alan Stern wrote: > > > > > > I would say instead "no I/O is allowed from now on". Maybe that's an > > > > > overstatement, but I think it comes closer to the truth. > > > > > > But that's what PM callbacks are

Re: [patch 3/3] vmstat: Create our own workqueue

Christoph Lameter wrote: > On Thu, 29 Oct 2015, Tejun Heo wrote: > > > Wait, this series doesn't include Tetsuo's change. Of course it won't > > fix the deadlock problem. What's necessary is Tetsuo's patch + > > WQ_MEM_RECLAIM. > > This series is only dealing with vmstat changes. Do I get an

Re: [RFD] Functional dependencies between devices

On Sat, Oct 31, 2015 at 03:13:09AM +0100, Rafael J. Wysocki wrote: > On Thursday, October 29, 2015 09:15:09 AM Mark Brown wrote: > > This seems like a good plan to me however I am concerned that only > > allowing links to be created at device registration time will prove > > restrictive - it

Re: [PATCH 5/6] cpufreq: governor: replace per-cpu delayed work with timers

Hi Ashwin, On 30-10-15, 16:46, Ashwin Chaugule wrote: > On 29 October 2015 at 08:27, Viresh Kumar wrote: > > This could be made lightweight by keeping per-cpu deferred timers with a > > single work item, which is scheduled by the first timer that expires. > > Single shared work item - would

[PATCH 2/3] dt-bindings: gpio: Documentation for Hi6220 gpio driver

dt-bindings: gpio: Documentation for Hi6220 gpio driver Signed-off-by: Zhong Kaihua --- .../devicetree/bindings/gpio/gpio-hi6220.txt | 23 ++ 1 file changed, 23 insertions(+) create mode 100644 Documentation/devicetree/bindings/gpio/gpio-hi6220.txt diff --git

[PATCH 3/3] arm64: dts: add Hi6220 pinctrl configuration nodes

arm64: dts: add Hi6220 pinctrl configuration nodes Signed-off-by: Zhong Kaihua --- arch/arm64/boot/dts/hisilicon/hi6220-hikey.dts | 1 + arch/arm64/boot/dts/hisilicon/hi6220.dtsi| 243 arch/arm64/boot/dts/hisilicon/hikey-gpio.dtsi| 416 ++

[PATCH 1/3] arm64: dts: Add Hi6220 gpio configuration nodes

arm64: dts: Add Hi6220 gpio configuration nodes Signed-off-by: Zhong Kaihua --- arch/arm64/boot/dts/hisilicon/hi6220-hikey.dts | 1 + arch/arm64/boot/dts/hisilicon/hi6220.dtsi | 38 + arch/arm64/boot/dts/hisilicon/hikey-gpio.dtsi | 195 + 3 files changed,

Re: [PATCH 1/3] PM / OPP: Add "opp-supported-hw" binding

On 30-10-15, 15:18, Stephen Boyd wrote: > A side-note. I wonder if it would be better style to have the > node name be: > > opp@6 { I thought the @... had a special meaning and we might end up creating some device for the node then? Perhaps I am mistaken. But then, yeah it

Re: [PATCH RESEND v2 net-next] net: hisilicon: updates HNS config and documents

On 10/31/2015 1:40 AM, huangdaode wrote: On 2015/10/30 22:20, Arnd Bergmann wrote: On Tuesday 27 October 2015 19:16:34 huangdaode wrote: mdio@803c { #address-cells = <1>; #size-cells = <0>; - compatible =

Re: [PATCH] PM / OPP: Protect updates to list_dev with mutex

On 30-10-15, 10:06, Stephen Boyd wrote: > On 10/30, Viresh Kumar wrote: > > dev_opp_list_lock is used everywhere to protect device and OPP lists, > > but dev_pm_opp_set_sharing_cpus() is missed somehow. And instead we used > > rcu-lock, which wouldn't help here as we are adding a new list_dev. > >

Re: [PATCH 1/3] PM / OPP: Add "opp-supported-hw" binding

On 30-10-15, 14:49, Stephen Boyd wrote: > I suppose if you wanted to have 64 possible combinations of some > attribute you would just extend it to two 32 bit numbers in > sequence? I don't see the limitation here, and hopefully there > isn't a limitation so that we can specify sufficiently large >

Re: [PATCH 1/3] recordmcount: fix endianness handling bug for nop_mcount

on 2015/10/30 22:35, Sergei Shtylyov wrote: > Hello. > > On 10/30/2015 11:31 AM, Li Bin wrote: > >> In nop_mcount, shdr->sh_offset and welp->r_offset should handle >> endianness properly, otherwise it will trigger Segmentation fault >> if the recordmcount main and file.o have different

Re: [PATCH v2] cpufreq: arm_big_little: fix frequency check when bL switcher is active

On Friday, October 30, 2015 10:48:18 AM Jon Medhurst wrote: > On Wed, 2015-10-21 at 15:27 +0530, Viresh Kumar wrote: > > On 21-10-15, 10:55, Jon Medhurst (Tixy) wrote: > > > The check for correct frequency being set in bL_cpufreq_set_rate is > > > broken when the big.LITTLE switcher is active, for

Re: [PATCH] ARM: dts: uniphier: add system-bus-controller nodes

On Tue, Oct 27, 2015 at 12:21:05PM +0900, Masahiro Yamada wrote: > The System Bus Controller block has two register regions, > but having only the second one in a separate node was not nice. > > Replace it with a new node with two register regions in it. > > Signed-off-by: Masahiro Yamada

Re: [PATCH] ARM: multi_v7_defconfig: enable UniPhier I2C drivers

On Tue, Oct 27, 2015 at 11:47:13AM +0900, Masahiro Yamada wrote: > These two drivers were merged into the I2C sub-system by > commit dd6fd4a32793 ("i2c: uniphier: add UniPhier FIFO-less I2C driver") > and commit 6a62974b667f ("i2c: uniphier_f: add UniPhier FIFO-builtin I2C > driver"). > > Enable

Re: [PATCH 1/2] pinctrl: uniphier: enable UniPhier SoCs pinctrl drivers by default

On Thu, Oct 29, 2015 at 02:33:34PM +0100, Linus Walleij wrote: > On Tue, Oct 27, 2015 at 3:28 AM, Masahiro Yamada > wrote: > > > Add "default y" to the Kconfig rather than adding entries into > > arch/arm/configs/multi_v7_defconfig. > > > > Signed-off-by: Masahiro Yamada > > (...) > > config

Re: timer code oops when calling mod_delayed_work

(cc'ing Lai) Hello, Jeff. On Thu, Oct 29, 2015 at 01:58:36PM -0400, Jeff Layton wrote: > crash> p cache_cleaner > cache_cleaner = $12 = { > work = { > data = { > counter = 0xfffe1 If I'm not mistaken, PENDING, flush color 14, OFFQ and POOL_NONE. > }, > entry = { >

Re: [RFD] Functional dependencies between devices

On Thursday, October 29, 2015 10:31:08 AM Alan Stern wrote: > Good grief, don't you guys ever trim unwanted material from your > emails? I had to erase more than 4 screens worth of useless stuff > before getting to the relevant portions. > > On Thu, 29 Oct 2015, Tomeu Vizoso wrote: > > > >>

Re: [PATCH v8 00/61] PCI: Resource allocation cleanup for v4.4

On Fri, Oct 30, 2015 at 2:47 PM, Khalid Aziz wrote: > > I applied patches 1-8 and 11-16 to 4.3.0-rc7 to test on sparc platforms. I > am seeing a "can't claim BAR" message on a T4: > > pci :04:00.0: can't claim BAR 6 [mem 0x840-0x840]: > address conflict with :04:00.0 [mem

Re: [PATCH 2/2] dma: add Qualcomm Technologies HIDMA channel driver

On 10/30/2015 6:28 PM, Arnd Bergmann wrote: I missed that part. If the descriptor count is a hardware feature, just make that property mandatory. OTOH, if this is an optimization setting, better drop that property entirely. I'm going to make this a module parameter instead and get rid of the

Re: [RFD] Functional dependencies between devices

On Thursday, October 29, 2015 09:15:09 AM Mark Brown wrote: > On Tue, Oct 27, 2015 at 04:24:14PM +0100, Rafael J. Wysocki wrote: > > > So, the question to everybody is whether or not this sounds reasonable or > > there > > are concerns about it and if so what they are. At this point I mostly

4.3 regression: task_work corruption in vm86 mode?

Hi all- In 4.3-rc7, running dosemu2 (https://github.com/stsp/dosemu2/) oopses the system very quickly, as long as CONFIG_VM86=y. It blows up because snd_seq_delete_port walks ports_list_head, finds two valid ports, and then starts finding obviously invalid pointers in the list. git bisect

Re: [PATCH RESEND v2 net-next] net: hisilicon: updates HNS config and documents

On 2015/10/30 22:20, Arnd Bergmann wrote: On Tuesday 27 October 2015 19:16:34 huangdaode wrote: mdio@803c { #address-cells = <1>; #size-cells = <0>; - compatible = "hisilicon,mdio","hisilicon,hns-mdio"; +

Re: [PATCH v7 2/7] dmaengine: mxs: APBH DMA supports deep sleep mode

On Tue, Oct 27, 2015 at 05:05:35PM -0500, Han Xu wrote: > > -static int __init mxs_dma_init(struct mxs_dma_engine *mxs_dma) > +static int mxs_dma_init(struct mxs_dma_engine *mxs_dma) This change seems unrelated to patch description, can you explain why? > +#ifdef CONFIG_PM_SLEEP > +static int

[PATCH v2] block: fix blk-core.c kernel-doc warning

From: Randy Dunlap Fix kernel-doc warning in blk-core.c: Warning(..//block/blk-core.c:1549): No description found for parameter 'same_queue_rq' Signed-off-by: Randy Dunlap Cc: Jeff Moyer Cc: Jens Axboe --- block/blk-core.c |3 +++ 1 file changed, 3 insertions(+) ---

[GIT PULL REQUEST] last minute bug fixes for md.

they just keep coming in :-( The following changes since commit 8bce6d35b308d73cdb2ee273c95d711a55be688c: md/raid10: fix the 'new' raid10 layout to work correctly. (2015-10-24 16:24:25 +1100) are available in the git repository at: git://neil.brown.name/md tags/md/4.3-rc7-fixes for you

Re: [PATCH] ahci: Add Marvell 88se91a2 device id

On Tue, Oct 27, 2015 at 11:48:14AM +0100, Johannes Thumshirn wrote: > On Tue, 2015-10-20 at 09:31 +0200, Johannes Thumshirn wrote: > > Add device id for Marvell 88se91a2 > > Tejun, ping? Oops, missed this one somehow. Applied to libata/for-4.4. Thanks. -- tejun -- To unsubscribe from this

Re: [patch 3/3] vmstat: Create our own workqueue

On Thu, Oct 29, 2015 at 08:01:12PM -0500, Christoph Lameter wrote: > On Thu, 29 Oct 2015, Tejun Heo wrote: > > > Wait, this series doesn't include Tetsuo's change. Of course it won't > > fix the deadlock problem. What's necessary is Tetsuo's patch + > > WQ_MEM_RECLAIM. > > This series is only

Re: [PATCH 1/3] ahci: qoriq: Rename LS2085A SoC support code to LS2080A

On Thu, Oct 29, 2015 at 02:22:15PM +0800, Tang Yuantian wrote: > Freescale is renaming the LS2085A SoC to LS2080A. > This patch addresses the same. > > Signed-off-by: Tang Yuantian Applied 1-3 to libata/for-4.4 with cosmetic updates. Thanks. -- tejun -- To unsubscribe from this list: send

[PATCH 3/4] Input: tsc2004 - Add support for tsc2004

Adds support for the i2c based tsc2004. Signed-off-by: Michael Welling --- drivers/input/touchscreen/Kconfig | 13 ++ drivers/input/touchscreen/Makefile | 1 + drivers/input/touchscreen/tsc2004.c | 86 + 3 files changed, 100 insertions(+) create mode

[PATCH 1/4] Input: tsc2005 - Separate SPI and core functions

This patch separates the SPI functionality from core functionality that overlaps with the tsc2004. Prepares kernel for new tsc2004 driver without much redundant code. Signed-off-by: Michael Welling --- drivers/input/touchscreen/Kconfig | 4 +

[PATCH 4/4] Input: tsc2004 - Document ts2004 dt bindings

Adds documentation for the devicetree bindings of the new tsc2004 driver. Signed-off-by: Michael Welling --- .../bindings/input/touchscreen/tsc2005.txt | 39 ++ 1 file changed, 39 insertions(+) diff --git

[PATCH 2/4] Input: tsc200x-core - Rename functions and variables

The functions, variables, and defines of the new tsc200x-core.c are renamed to tsc200x instead of tsc2005 avoid possible confusion. Signed-off-by: Michael Welling --- drivers/input/touchscreen/tsc2005.c | 2 +- drivers/input/touchscreen/tsc200x-core.c | 200

[PATCH v4 0/4] tsc2005 - Add support for tsc2004

Adds support for the i2c based tsc2004. Due to the overlapping functionality of the tsc2004 and tsc2005 the common code was moved to a core driver (tsc200x-core). v4: Break patch into series. Isolates the I2C and SPI commands to respective drivers. v3: Splits the tsc2004 and tsc2005 into

[PATCH 1/3] drm/dsi: Add support for Turn on/Shutdown peripheral packets

From: Werner Johansson The MIPI_DSI_TURN_ON_PERIPHERAL and MIPI_DSI_SHUTDOWN_PERIPHERAL packets are required for some panels, one example being the Panasonic VVX10F034N00 panel. Signed-off-by: Werner Johansson Signed-off-by: Bjorn Andersson --- drivers/gpu/drm/drm_mipi_dsi.c | 47

[PATCH 2/3] panel/panasonic-vvx10f034n00: Add DT bindings

From: Werner Johansson This patch adds bindings for the Panasonic VVX10F034N00 WUXGA panel. Signed-off-by: Werner Johansson Signed-off-by: Bjorn Andersson --- .../bindings/panel/panasonic,vvx10f034n00.txt| 20 1 file changed, 20 insertions(+) create mode 100644

[PATCH 3/3] drm/panel: Add Panasonic VVX10F034N00 MIPI DSI panel

From: Werner Johansson This adds support for the Panasonic panel found in some Xperia Z2 tablets. Signed-off-by: Werner Johansson Signed-off-by: Bjorn Andersson --- drivers/gpu/drm/panel/Kconfig | 10 + drivers/gpu/drm/panel/Makefile | 1 +

Re: [PATCH] mtd: blkdevs: fix potential deadlock + lockdep warnings

On Mon, Oct 26, 2015 at 07:38:49PM -0700, Brian Norris wrote: > Commit 073db4a51ee4 ("mtd: fix: avoid race condition when accessing > mtd->usecount") fixed a race condition but due to poor ordering of the > mutex acquisition, introduced a potential deadlock. [...] > > Fixes: 073db4a51ee4 ("mtd:

Re: [git pull] drm fixes (updated)

On 31 October 2015 at 10:08, Dave Airlie wrote: > > Hi Linus, > > This is an updated pull, you can ignore the last one. > > Two drm atomic core fixes. > > The two radeon patches needed to fix a backlight > regression on some older hardware. I needed one more stable tag on the top of that, so the

Re: [PATCH v2 1/4] clocksource: rockchip: Make the driver more compatible

Hi Daniel, Am Freitag, 30. Oktober 2015, 11:42:29 schrieb Daniel Lezcano: > On 10/30/2015 04:43 AM, Caesar Wang wrote: > > Hi Daniel, > > > > 在 2015年10月01日 03:14, Heiko Stübner 写道: > >> Hi Daniel, > >> > >> Am Dienstag, 29. September 2015, 06:18:03 schrieb Daniel Lezcano: > >>> On 09/25/2015

Re: [PATCH v3 1/4] lib/string_helpers: change blk_size to u32 for string_get_size() interface

On Fri, 2015-10-30 at 11:46 +0100, Vitaly Kuznetsov wrote: > James Bottomley writes: > > > On Thu, 2015-10-29 at 17:30 +0100, Vitaly Kuznetsov wrote: > >> string_get_size() can't really handle huge block sizes, especially > >> blk_size > U32_MAX but string_get_size() interface states the

Re: [PATCH v3 5/5] mtd: ofpart: move ofpart partitions to a dedicated dt node

On Tue, Aug 18, 2015 at 03:34:09PM -, Michal Suchanek wrote: > Parsing direct subnodes of a mtd device as partitions is unreliable > since the mtd device is also part of its bus subsystem and can contain > bus data in subnodes. > > Move ofpart data to a subnode of its own so it is clear which

Re: [PATCH] block: genhd: Add disk/partition specific uevent callbacks for partition info

On Thu, Oct 22, 2015 at 10:27 AM, John Stultz wrote: > From: San Mehat > > This patch has been carried in the Android tree for quite some > time and is one of the few patches required to get a mainline > kernel up and running with an exsiting Android userspace. So I > wanted to submit it for

[git pull] drm fixes (updated)

Hi Linus, This is an updated pull, you can ignore the last one. Two drm atomic core fixes. The two radeon patches needed to fix a backlight regression on some older hardware. Dave. The following changes since commit 8a28d67457b613258aa0578ccece206d166f2b9f: Merge tag 'powerpc-4.3-6' of

Re: [PATCH v3 2/4] lib/string_helpers.c: protect string_get_size() against blk_size=0

On Fri, 2015-10-30 at 11:41 +0100, Vitaly Kuznetsov wrote: > James Bottomley writes: > > > On Fri, 2015-10-30 at 01:32 +0200, Andy Shevchenko wrote: > >> On Fri, Oct 30, 2015 at 1:00 AM, James Bottomley > >> wrote: > >> > On Thu, 2015-10-29 at 17:30 +0100, Vitaly Kuznetsov wrote: > >> >>

Re: [PATCH] bpf: convert hashtab lock to raw lock

On Fri, Oct 30, 2015 at 03:16:26PM -0700, Yang Shi wrote: > When running bpf samples on rt kernel, it reports the below warning: > > BUG: sleeping function called from invalid context at > kernel/locking/rtmutex.c:917 > in_atomic(): 1, irqs_disabled(): 128, pid: 477, name: ping > Preemption

Re: [REPOST PATCH 0/3] dwc2 patches to allow wakeup on Rockchip rk3288

John, On Mon, Oct 26, 2015 at 7:05 PM, John Youn wrote: > On 10/21/2015 9:23 AM, Doug Anderson wrote: >> John, >> >> On Mon, Jul 6, 2015 at 11:27 AM, Douglas Anderson >> wrote: >>> This series of patches, together with >>> from Chris Zhong and a

Re: [BUG] IB/hfi1: might sleep under spinlock in hfi1_ioctl()

On Sat, Oct 31, 2015 at 12:32:29AM +0300, Alexey Khoroshilov wrote: > Hello, > > hfi1_ioctl() contains many calls to might sleep functions with > dd->hfi1_snoop.snoop_lock spinlock held (for example, access_ok, > copy_from_user, kzalloc(GFP_KERNEL), etc.). > > Should dd->hfi1_snoop.snoop_lock be

[PATCH] sg: Fix double-free when drives detach during SG_IO

In sg_common_write(), we free the block request and return -ENODEV if the device is detached in the middle of the SG_IO ioctl(). Unfortunately, sg_finish_rem_req() also tries to free srp->rq, so we end up freeing rq->cmd in the already free rq object, and then free the object itself out from

[PATCH v3 2/3] iio: light: lm3533-als: Print error message on invalid resistance

Print an error message to indicate that invalid configuration data was provided in the platform_data, rather than just aborting initialization. Signed-off-by: Bjorn Andersson --- This patch can be picked independently of the other 2, but included in the series for "completeness". No changes

[PATCH v3 3/3] mfd: lm3533: Support initialization from Device Tree

Implement Device Tree parsing functions to support initialization of the lm3533 drivers. Signed-off-by: Bjorn Andersson --- Changes since v2: - Included and changed unit in various dt properties - Fix compilation issue with !CONFIG_OF Changes since v1: - Added units to bost-freq and als

Re: [PATCH v2 0/4] x86: sigcontext fixes, again

On Tue, Oct 27, 2015 at 7:05 AM, Stas Sergeev wrote: > 27.10.2015 03:52, Andy Lutomirski пишет: >> On Mon, Oct 26, 2015 at 4:45 AM, Stas Sergeev wrote: >>> 26.10.2015 04:25, Andy Lutomirski пишет: This is take 2 at fixing x86 64-bit signals wrt SS. After a lot of thought, this is not

[PATCH v3 1/3] devicetree: mfd: Add binding for the TI LM3533

Add the binding for the Texas Instruments LM3533 lighting power solution. Signed-off-by: Bjorn Andersson --- Changes since v2: - Drop vendor prefix of vendor properties - Specify unit of various properties - Fix reference paths Changes since v1: - Added unit to boost-freq and als-resistance

Re: [PATCH v2] fs/block_dev.c: Remove WARN_ON() when inode writeback fails

On 10/30/2015 09:34 AM, Jeff Moyer wrote: From: Vivek Goyal If a block device is hot removed and later last reference to device is put, we try to writeback the dirty inode. But device is gone and that writeback fails. Currently we do a WARN_ON() which does not seem to be the right thing.

[PATCH v2 net-next] net: dsa: mv88e6xxx: lookup switch name

All the mv88e6xxx drivers use the exact same code in their probe function to lookup the switch name given its ID. Thus introduce a mv88e6xxx_switch_id structure and a mv88e6xxx_lookup_name function in the common mv88e6xxx code. In the meantime make __mv88e6xxx_reg_{read,write} static since we do

Re: [Y2038] [RESEND PATCH v3] scsi: stex: Remove use of struct timeval

On Friday 30 October 2015 01:54:10 Tina Ruchandani wrote: > > > > Thanks for the conversion. Can you please check if other (scsi) drivers > > have the same y2038 issues? A quick "git grep do_gettimeofday > > drivers/scsi/ | wc -l" reveals 30 occurrences (of cause not all are > > problematic). In

Re: [PATCH 2/2] sound: soc: Add Cygnus audio driver

Hi Arnd, On 10/30/2015 4:28 PM, Arnd Bergmann wrote: On Saturday 31 October 2015 07:20:17 kbuild test robot wrote: > 785 dev_dbg(rtd->cpu_dai->dev, "%s: size 0x%x @ 0x%p\n", 786 __func__, size, buf->area); Both reports are for the same bug:

[PATCH] mm/hugetlbfs Fix bugs in fallocate hole punch of areas with holes

Hugh Dickins pointed out problems with the new hugetlbfs fallocate hole punch code. These problems are in the routine remove_inode_hugepages and mostly occur in the case where there are holes in the range of pages to be removed. These holes could be the result of a previous hole punch or simply

Re: [PATCH 2/2] sound: soc: Add Cygnus audio driver

On Saturday 31 October 2015 07:20:17 kbuild test robot wrote: > > 785 dev_dbg(rtd->cpu_dai->dev, "%s: size 0x%x @ 0x%p\n", >786 __func__, size, buf->area); > Both reports are for the same bug: the "0x%x" should be "0x%zx". There is another bug in

[PATCH tip/locking/core v9 1/6] locking/qspinlock: Use _acquire/_release versions of cmpxchg & xchg

This patch replaces the cmpxchg() and xchg() calls in the native qspinlock code with the more relaxed _acquire or _release versions of those calls to enable other architectures to adopt queued spinlocks with less memory barrier performance overhead. Signed-off-by: Waiman Long ---

[PATCH tip/locking/core v9 2/6] locking/qspinlock: prefetch next node cacheline

A queue head CPU, after acquiring the lock, will have to notify the next CPU in the wait queue that it has became the new queue head. This involves loading a new cacheline from the MCS node of the next CPU. That operation can be expensive and add to the latency of locking operation. This patch

[PATCH tip/locking/core v9 5/6] locking/pvqspinlock: Allow 1 lock stealing attempt

This patch allows one attempt for the lock waiter to steal the lock when entering the PV slowpath. To prevent lock starvation, the pending bit will be set by the queue head vCPU when it is in the active lock spinning loop to disable any lock stealing attempt. This helps to reduce the performance

[PATCH tip/locking/core v9 0/6] locking/qspinlock: Enhance pvqspinlock

v8->v9: - Added a new patch 2 which tried to prefetch the cacheline of the next MCS node in order to reduce the MCS unlock latency when it was time to do the unlock. - Changed the slowpath statistics counters implementation in patch 4 from atomic_t to per-cpu variables to reduce

[PATCH tip/locking/core v9 6/6] locking/pvqspinlock: Queue node adaptive spinning

In an overcommitted guest where some vCPUs have to be halted to make forward progress in other areas, it is highly likely that a vCPU later in the spinlock queue will be spinning while the ones earlier in the queue would have been halted. The spinning in the later vCPUs is then just a waste of

[PATCH tip/locking/core v9 3/6] locking/pvqspinlock, x86: Optimize PV unlock code path

The unlock function in queued spinlocks was optimized for better performance on bare metal systems at the expense of virtualized guests. For x86-64 systems, the unlock call needs to go through a PV_CALLEE_SAVE_REGS_THUNK() which saves and restores 8 64-bit registers before calling the real

[PATCH tip/locking/core v9 4/6] locking/pvqspinlock: Collect slowpath lock statistics

This patch enables the accumulation of kicking and waiting related PV qspinlock statistics when the new QUEUED_LOCK_STAT configuration option is selected. It also enables the collection of data which enable us to calculate the kicking and wakeup latencies which have a heavy dependency on the CPUs

Re: [PATCH 2/2] sound: soc: Add Cygnus audio driver

Hi Simran, [auto build test WARNING on asoc/for-next -- if it's inappropriate base, please suggest rules for selecting the more suitable base] url: https://github.com/0day-ci/linux/commits/Simran-Rai/Add-audio-support-for-Broadcom-Cygnus-SoC/20151031-025721 config: tile-allmodconfig

Re: [RFC PATCH 1/3] PCI: iproc: generate proper configuration access cycles

On Tuesday 27 October 2015 10:18:20 Jisheng Zhang wrote: > On Mon, 26 Oct 2015 10:18:14 -0700 Ray Jui wrote: > > > Hi Jisheng, > > > > On 10/26/2015 4:02 AM, Jisheng Zhang wrote: > > > Inspired by Russell King's patch[1], I found current iproc also has the > > > same issue of "reading 32-bits

[PATCH 1/1] drm/i915/dma: enforce pr_ consistency

One branch of the if clause uses pr_info, the other pr_err; change the 'false' branch to also use pr_info. This minor oversight has gone unfixed since the initial vga_switcheroo implementation in 6a9ee8af. Signed-off-by: Ioan-Adrian Ratiu --- drivers/gpu/drm/i915/i915_dma.c | 2 +- 1 file

Re: [PATCH v3 net] i40e: Look up MAC address in Open Firmware or IDPROM

On (10/30/15 22:03), Nelson, Shannon wrote: > The more common idiom in our driver would be > > err = i40e_get_platform_mac_addr(..); > if (err) { Ok. > Have you tested this beyond a compile? > Do you have a DT model to try this against? yes. > In looking at a couple other drivers,

[PATCH v2 net-next] net: dsa: mv88e6xxx: assert SMI lock

It's easy to forget to lock the smi_mutex before calling the low-level _mv88e6xxx_reg_{read,write}, so add a assert_smi_lock function in them. Signed-off-by: Vivien Didelot --- drivers/net/dsa/mv88e6xxx.c | 25 ++--- 1 file changed, 14 insertions(+), 11 deletions(-) diff

  1   2   3   4   5   6   7   8   9   10   >