Re: [ 3.14.0-12041-g75ff24f ] regression: drm warning

2014-04-09 12:08 GMT+02:00 Jörg Otte : > Kernel 3.14.0-12041-g75ff24f from 9.4.2014 introduces the following > on the console (driver is i915): > > [drm:ivb_err_int_handler] *ERROR* Pipe B FIFO underrun > [drm:cpt_serr_int_handler] *ERROR* PCH transcoder A FIFO underrun >

Re: [PATCH] netfilter: conntrack: initialize net.ct.generation

On Sat, Apr 12, 2014 at 04:58:18PM -0400, David Miller wrote: > From: Andrey Vagin > Date: Fri, 11 Apr 2014 21:34:20 +0400 > > > [ 251.920788] INFO: trying to register non-static key. > > I'll let Pablo integrate this. Applied, thanks. -- To unsubscribe from this list: send the line

Re: [PATCH 02/12] drm/nouveau/timer: skip calibration on GK20A

On Fri, Apr 11, 2014 at 5:34 PM, Alexandre Courbot wrote: > On 04/11/2014 04:31 PM, Ben Skeggs wrote: >> >> On Fri, Apr 11, 2014 at 12:46 PM, Alexandre Courbot >> wrote: >>> >>> On Wed, Mar 26, 2014 at 1:19 PM, Ben Skeggs wrote: On Tue, Mar 25, 2014 at 7:54 AM, Thierry Reding

[PATCH v2 RESEND 03/23] bfa: Cleanup bfad_setup_intr() function

Signed-off-by: Alexander Gordeev Cc: Anil Gurumurthy Cc: Vijaya Mohan Guvva Cc: linux-s...@vger.kernel.org Cc: linux-...@vger.kernel.org Acked-by: Anil Gurumurthy --- drivers/scsi/bfa/bfad.c | 18 -- 1 files changed, 8 insertions(+), 10 deletions(-) diff --git

[PATCH v2 RESEND 00/23] scsi: Use pci_enable_msix_range() instead of pci_enable_msix()

Hello, This series is against 3.15-rc1. As result of deprecation of MSI-X/MSI enablement functions pci_enable_msix() and pci_enable_msi_block() all drivers using these two interfaces need to be updated to use the new pci_enable_msi_range() or pci_enable_msi_exact() and pci_enable_msix_range()

[PATCH 3/7] blk-mq: make ->flush_rq fully transparent to drivers

Drivers shouldn't have to care about the block layer setting aside a request to implement the flush state machine. We already override the mq context and tag to make it more transparent, but so far haven't deal with the driver private data in the request. Make sure to override this as well, and

[PATCH 2/7] blk-mq: do not initialize req->special

Drivers can reach their private data easily using the blk_mq_rq_to_pdu helper and don't need req->special. By not initializing it code can be simplified nicely, and we also shave off a few more instructions from the I/O path. Signed-off-by: Christoph Hellwig --- block/blk-flush.c |

[PATCH 1/7] blk-mq: initialize resid_len

Signed-off-by: Christoph Hellwig --- block/blk-mq.c |2 ++ 1 file changed, 2 insertions(+) diff --git a/block/blk-mq.c b/block/blk-mq.c index 1d2a9bd..c1f4736 100644 --- a/block/blk-mq.c +++ b/block/blk-mq.c @@ -350,6 +350,8 @@ static void blk_mq_start_request(struct request *rq, bool

[PATCH 4/7] blk-mq: add ->init_request and ->exit_request methods

The current blk_mq_init_commands/blk_mq_free_commands interface has a two problems: 1) Because only the constructor is passed to blk_mq_init_commands there is no easy way to clean up when a comman initialization failed. The current code simply leaks the allocations done in the

[PATCH 5/7] blk-mq: initialize request on allocation

If we want to share tag and request allocation between queues we cannot initialize the request at init/free time, but need to initialize it at allocation time as it might get used for different queues over its lifetime. Signed-off-by: Christoph Hellwig --- block/blk-mq.c |4 +--- 1 file

[PATCH 7/7] block: all blk-mq requests are tagged

Instead of setting the REQ_QUEUED flag on each of them just take it into account in the only macro checking it. Signed-off-by: Christoph Hellwig --- include/linux/blkdev.h |3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/include/linux/blkdev.h b/include/linux/blkdev.h

[PATCH 6/7] blk-mq: split out tag initialization, support shared tags

Add a new blk_mq_tag_set structure that gets set up before we initialize the queue. A single blk_mq_tag_set structure can be shared by multiple queues. Signed-off-by: Christoph Hellwig --- block/blk-mq-cpumap.c |6 +- block/blk-mq-tag.c | 14 --- block/blk-mq-tag.h |

[no subject]

This is the majority of the blk-mq work still required for switching over SCSI. There are a few more bits for I/O completion and requeueing pending, but they will need further work. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to

Re: [PATCH] efi: Clarify Kconfig help for EFI_MIXED

Am 14.04.2014 09:15, schrieb Ingo Molnar: >>> Right, it is really that it is not possible to boot a mixed-mode kernel >>> on its non-native firmware using the stub, since the stub itself can >>> only be one way or the other. >> >> Yeah, my help text was a bit... unhelpful. >> >> CONFIG_EFI_MIXED

[PATCH v2 RESEND 02/23] bfa: Do not call pci_enable_msix() after it failed once

Function pci_enable_msix() should not be called in case it threw a negative errno from a previous call. Signed-off-by: Alexander Gordeev Cc: Anil Gurumurthy Cc: Vijaya Mohan Guvva Cc: linux-s...@vger.kernel.org Cc: linux-...@vger.kernel.org Acked-by: Anil Gurumurthy ---

[PATCH v2 RESEND 06/23] csiostor: Use pci_enable_msix_range() instead of pci_enable_msix()

As result of deprecation of MSI-X/MSI enablement functions pci_enable_msix() and pci_enable_msi_block() all drivers using these two interfaces need to be updated to use the new pci_enable_msi_range() or pci_enable_msi_exact() and pci_enable_msix_range() or pci_enable_msix_exact() interfaces.

[PATCH v2 RESEND 01/23] be2iscsi: Use pci_enable_msix_exact() instead of pci_enable_msix()

As result of deprecation of MSI-X/MSI enablement functions pci_enable_msix() and pci_enable_msi_block() all drivers using these two interfaces need to be updated to use the new pci_enable_msi_range() or pci_enable_msi_exact() and pci_enable_msix_range() or pci_enable_msix_exact() interfaces.

[PATCH v2 RESEND 04/23] bfa: Use pci_enable_msix_exact() instead of pci_enable_msix()

As result of deprecation of MSI-X/MSI enablement functions pci_enable_msix() and pci_enable_msi_block() all drivers using these two interfaces need to be updated to use the new pci_enable_msi_range() or pci_enable_msi_exact() and pci_enable_msix_range() or pci_enable_msix_exact() interfaces.

[PATCH v2 RESEND 05/23] csiostor: Remove superfluous call to pci_disable_msix()

There is no need to call pci_disable_msix() in case the previous call to pci_enable_msix() failed Signed-off-by: Alexander Gordeev Cc: Naresh Kumar Inna Cc: Arvind Bhushan Cc: linux-s...@vger.kernel.org Cc: linux-...@vger.kernel.org --- drivers/scsi/csiostor/csio_isr.c |4 +--- 1 files

[PATCH v2 RESEND 07/23] fnic: Use pci_enable_msix_exact() instead of pci_enable_msix()

As result of deprecation of MSI-X/MSI enablement functions pci_enable_msix() and pci_enable_msi_block() all drivers using these two interfaces need to be updated to use the new pci_enable_msi_range() or pci_enable_msi_exact() and pci_enable_msix_range() or pci_enable_msix_exact() interfaces.

[PATCH v2 RESEND 12/23] lpfc: Use pci_enable_msix_range() instead of pci_enable_msix()

As result of deprecation of MSI-X/MSI enablement functions pci_enable_msix() and pci_enable_msi_block() all drivers using these two interfaces need to be updated to use the new pci_enable_msi_range() or pci_enable_msi_exact() and pci_enable_msix_range() or pci_enable_msix_exact() interfaces.

[PATCH v2 RESEND 11/23] lpfc: Remove superfluous call to pci_disable_msix()

There is no need to call pci_disable_msix() in case the previous call to pci_enable_msix() failed Signed-off-by: Alexander Gordeev Cc: James Smart Cc: linux-s...@vger.kernel.org Cc: linux-...@vger.kernel.org Acked-by: James Smart --- drivers/scsi/lpfc/lpfc_init.c |9 ++--- 1 files

[PATCH v2 RESEND 08/23] isci: Use pci_enable_msix_exact() instead of pci_enable_msix()

As result of deprecation of MSI-X/MSI enablement functions pci_enable_msix() and pci_enable_msi_block() all drivers using these two interfaces need to be updated to use the new pci_enable_msi_range() or pci_enable_msi_exact() and pci_enable_msix_range() or pci_enable_msix_exact() interfaces.

Re: [PATCH 5/9] crypto: qce: Adds sha and hmac transforms

Hi Stephen, On 04/11/2014 11:12 PM, Stephen Boyd wrote: > On 04/10, Stanimir Varbanov wrote: >> On 04/09/2014 03:09 AM, Stephen Boyd wrote: >>> On 04/03, Stanimir Varbanov wrote: >>> + + return 0; +} + +static int qce_ahash_import(struct ahash_request *req, const void

[PATCH v2 RESEND 13/23] megaraid: Fail resume if MSI-X re-initialization failed

Currently the driver fails to analize MSI-X re-enablement status on resuming and always assumes the success. This update checks the MSI-X initialization result and fails to resume if MSI-Xs re-enablement failed. Signed-off-by: Alexander Gordeev --- drivers/scsi/megaraid/megaraid_sas_base.c |

[PATCH v4 1/2] Documentation: Add GPIO reset binding to reset binding documentation

This patch adds documentation clarifying the reset GPIO bindings most commonly in use (reset-gpios and -reset-gpios properties). Signed-off-by: Philipp Zabel --- Documentation/devicetree/bindings/reset/reset.txt | 26 +-- 1 file changed, 24 insertions(+), 2 deletions(-)

[PATCH v4 2/2] reset: Add GPIO support to reset controller framework

This adds support for GPIO controlled reset pins on peripheral ICs to the reset controller framework. Currently there is no support for specifying a delay between assertion and de-assertion of the reset signal, so this has to be handled by the drivers. Signed-off-by: Philipp Zabel --- Changes

[PATCH v2 RESEND 15/23] mpt2sas: Use pci_enable_msix_exact() instead of pci_enable_msix()

As result of deprecation of MSI-X/MSI enablement functions pci_enable_msix() and pci_enable_msi_block() all drivers using these two interfaces need to be updated to use the new pci_enable_msi_range() or pci_enable_msi_exact() and pci_enable_msix_range() or pci_enable_msix_exact() interfaces.

Re: [PATCH 2/3] sched,numa: retry placement more frequently when misplaced

* Rik van Riel wrote: > On 04/11/2014 01:46 PM, Joe Perches wrote: > > On Fri, 2014-04-11 at 13:00 -0400, r...@redhat.com wrote: > >> This patch reduces the interval at which migration is retried, > >> when the task's numa_scan_period is small. > > > > More style trivia and a question. [...]

clovertrail (z2760) defconfig?

hi i'm unsuccessfully trying to boot a linux kernel on an intel atom z2760 right now but somehow the boot up process appears to be crashing the cpu right at the beginning of the load process. not even the uefi early_printk's appear to be reached, so it must be the setup.S or something like this.

Re: [PATCH 1/9] crypto: qce: Add core driver implementation

Hi Courtney, On 04/09/2014 01:00 AM, Courtney Cavin wrote: > On Tue, Apr 08, 2014 at 06:26:44PM +0200, Stanimir Varbanov wrote: >> On 04/04/2014 02:38 AM, Courtney Cavin wrote: >>> On Thu, Apr 03, 2014 at 06:17:58PM +0200, Stanimir Varbanov wrote: This adds core driver files. The core part

Pull request ?

Hi Jonathan, I realise you didn't send any pull request for 3.15 yet, do you intend to send it soon. As you know, I have a patch set depending on a few patches and I'd like to rebase and resend it soon. Regards, -- Alexandre Belloni, Free Electrons Embedded Linux, Kernel and Android

[PATCH 0/4] ARM: at91: move sam9n12 SoC and boards to the CCF

Hello, This series moves the at91sam9n12 SoC and the at91sam9n12-ek board to the Common Clock Framework. It depends on this series [1], which introduces new slow clock and main clock implementation (and DT bindings) for at91 SoCs. Best Regards, Boris [1]

[PATCH 4/4] ARM: at91: move sam9n12 SoC to the CCF

This patch removes the selection of AT91_USE_OLD_CLK when selecting sam9n12 SoC support. This will automatically enable COMMON_CLK_AT91 option and add support for at91 common clk implementation. Signed-off-by: Boris BREZILLON --- arch/arm/mach-at91/Kconfig | 1 - 1 file changed, 1 deletion(-)

[PATCH 3/4] ARM: at91/dt: define sam9n12ek crystal frequencies

Define sam9n12ek's main and slow crystal frequencies. Signed-off-by: Boris BREZILLON --- arch/arm/boot/dts/at91sam9n12ek.dts | 8 1 file changed, 8 insertions(+) diff --git a/arch/arm/boot/dts/at91sam9n12ek.dts b/arch/arm/boot/dts/at91sam9n12ek.dts index 924a6a6..6132769 100644 ---

[PATCH 2/4] ARM: at91/dt: define sam9n12 clocks

Define sam9n12 clocks and make use of them in peripheral definitions. Signed-off-by: Boris BREZILLON --- arch/arm/boot/dts/at91sam9n12.dtsi | 350 - 1 file changed, 348 insertions(+), 2 deletions(-) diff --git a/arch/arm/boot/dts/at91sam9n12.dtsi

[PATCH 1/4] ARM: at91: prepare common clk transition for sam9n12 SoC

This patch encloses sam9n12 old clk registration in "#if defined(CONFIG_OLD_CLK_AT91) #endif" sections. Signed-off-by: Boris BREZILLON --- arch/arm/mach-at91/at91sam9n12.c | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/arch/arm/mach-at91/at91sam9n12.c

[PATCH v2 RESEND 14/23] megaraid: Use pci_enable_msix_range() instead of pci_enable_msix()

As result of deprecation of MSI-X/MSI enablement functions pci_enable_msix() and pci_enable_msi_block() all drivers using these two interfaces need to be updated to use the new pci_enable_msi_range() or pci_enable_msi_exact() and pci_enable_msix_range() or pci_enable_msix_exact() interfaces.

Re: [PATCH V2 1/1] X86: Probe for PIC and set legacy_pic appropriately

>>> On 12.04.14 at 07:56, wrote: > --- a/arch/x86/kernel/i8259.c > +++ b/arch/x86/kernel/i8259.c > @@ -299,11 +299,30 @@ static void unmask_8259A(void) > static void init_8259A(int auto_eoi) > { > unsigned long flags; > + unsigned char probe_val = ~(1 << PIC_CASCADE_IR); > +

[PATCH v2 RESEND 20/23] pmcraid: Use pci_enable_msix_range() instead of pci_enable_msix()

As result of deprecation of MSI-X/MSI enablement functions pci_enable_msix() and pci_enable_msi_block() all drivers using these two interfaces need to be updated to use the new pci_enable_msi_range() or pci_enable_msi_exact() and pci_enable_msix_range() or pci_enable_msix_exact() interfaces.

[PATCH v2 RESEND 16/23] mpt3sas: Use pci_enable_msix_exact() instead of pci_enable_msix()

As result of deprecation of MSI-X/MSI enablement functions pci_enable_msix() and pci_enable_msi_block() all drivers using these two interfaces need to be updated to use the new pci_enable_msi_range() or pci_enable_msi_exact() and pci_enable_msix_range() or pci_enable_msix_exact() interfaces.

[PATCH v2 RESEND 21/23] qla2xxx: Use pci_enable_msix_range() instead of pci_enable_msix()

As result of deprecation of MSI-X/MSI enablement functions pci_enable_msix() and pci_enable_msi_block() all drivers using these two interfaces need to be updated to use the new pci_enable_msi_range() or pci_enable_msi_exact() and pci_enable_msix_range() or pci_enable_msix_exact() interfaces. Log

[PATCH 1/4] regulator: s2mps11: Move DTS parsing code to separate function

Refactor code for parsing DTS to increase a little code readability. The behaviour should not change. Signed-off-by: Krzysztof Kozlowski --- drivers/regulator/s2mps11.c | 35 +++ 1 file changed, 23 insertions(+), 12 deletions(-) diff --git

[PATCH v2 RESEND 19/23] pmcraid: Get rid of a redundant assignment

Signed-off-by: Alexander Gordeev Cc: Anil Ravindranath Cc: linux-s...@vger.kernel.org Cc: linux-...@vger.kernel.org --- drivers/scsi/pmcraid.c |1 - 1 files changed, 0 insertions(+), 1 deletions(-) diff --git a/drivers/scsi/pmcraid.c b/drivers/scsi/pmcraid.c index be8ce54..c06af7f 100644

Re: [PATCH] phy: exynos5-usbdrd: Add facility to toggle vbus gpio on/off

Hi Felipe, On Sat, Apr 12, 2014 at 9:07 AM, Felipe Balbi wrote: > On Wed, Apr 09, 2014 at 05:24:45PM +0530, Vivek Gautam wrote: >> Adding support to enable/disable VBUS hooked to a gpio >> to enable vbus supply on the port. >> >> Signed-off-by: Vivek Gautam >> --- >> >> Based on

[PATCH v2 RESEND 23/23] vmw_pvscsi: Use pci_enable_msix_exact() instead of pci_enable_msix()

As result of deprecation of MSI-X/MSI enablement functions pci_enable_msix() and pci_enable_msi_block() all drivers using these two interfaces need to be updated to use the new pci_enable_msi_range() or pci_enable_msi_exact() and pci_enable_msix_range() or pci_enable_msix_exact() interfaces.

[PATCH 3/4] Documentation: regulator: s2mps11: Document external GPIO control

Add documentation for new property for controlling (enable/disable) some of the S2MPS14 regulators by GPIO. Signed-off-by: Krzysztof Kozlowski Cc: Tomasz Figa Cc: devicet...@vger.kernel.org Cc: Rob Herring Cc: Pawel Moll Cc: Mark Rutland Cc: Ian Campbell Cc: Kumar Gala ---

Re: Kernel scanning/freeing to relieve cgroup memory pressure

Johannes/Michal What are your thoughts on this matter? Do you see this as a valid requirement? Regards, Glyn On 02/04/2014 19:00, Tejun Heo wrote: (cc'ing memcg maintainers and cgroup ML) On Wed, Apr 02, 2014 at 02:08:04PM +0100, Glyn Normington wrote: Currently, a memory cgroup can hit

[PATCH 0/4] regulator: s2mps11: Add external GPIO control for S2MPS14

Hi, This patchset adds external GPIO control to s2mps11 regulator driver for some of the S2MPS14 regulators. Additionally (patch 4/4) it changes the bindings in s5m8767 regulator driver for external control to match these used here: "samsung,ext-control-gpios" Best regards, Krzysztof

Re: [PATCH] pwm_lpss: Add support for PCI devices

On Sat, Apr 12, 2014 at 09:58:51PM +0800, Chew Chiau Ee wrote: > From: Alan Cox > > Not all systems enumerate the PWM devices via ACPI. They can also be exposed > via the PCI interface. > > Signed-off-by: Alan Cox > Signed-off-by: Chew, Chiau Ee > --- > drivers/pwm/pwm-lpss.c | 160

[PATCH 2/4] regulator: s2mps11: Add external GPIO control for S2MPS14

Add support for external control over GPIO for LDO10, LDO11 and LDO12 S2MPS14 regulators. External control can be turned on by writing 0x0 to control register which in case of other regulators is used for disabling them. These LDO10-LDO12 regulators can be disabled only by I2C GPIO or PWREN pin so

[PATCH 4/4] regulator: s5m8767: Use same binding for external control as in s2mps11

Change the binding for regulators external control to the same used in s2mps11 driver to be consistent. Signed-off-by: Krzysztof Kozlowski Cc: Tomasz Figa Cc: devicet...@vger.kernel.org Cc: Rob Herring Cc: Pawel Moll Cc: Mark Rutland Cc: Ian Campbell Cc: Kumar Gala ---

[PATCH v2 RESEND 18/23] pm8001: Use pci_enable_msix_exact() instead of pci_enable_msix()

As result of deprecation of MSI-X/MSI enablement functions pci_enable_msix() and pci_enable_msi_block() all drivers using these two interfaces need to be updated to use the new pci_enable_msi_range() or pci_enable_msi_exact() and pci_enable_msix_range() or pci_enable_msix_exact() interfaces.

[PATCH] arm64:kconfig: make default for CONFIG_COMPAT

'make savedefconfig' doesn't generate defconfig properly due to missing COMPAT default. So Add default and set to yes. Signed-off-by: Chanho Min --- arch/arm64/Kconfig |1 + 1 file changed, 1 insertion(+) diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig index 4907b85..93b7531 100644

[PATCH v2 RESEND 17/23] pm8001: Fix invalid return when request_irq() failed

When a call to request_irq() failed pm8001_setup_msix() still returns the success. This udate fixes the described misbehaviour. Signed-off-by: Alexander Gordeev Cc: xjtu...@gmail.com Cc: lindar_...@usish.com Cc: linux-s...@vger.kernel.org Cc: linux-...@vger.kernel.org Acked-by: Jack Wang ---

[PATCH v2 RESEND 10/23] hpsa: Use pci_enable_msix_range() instead of pci_enable_msix()

As result of deprecation of MSI-X/MSI enablement functions pci_enable_msix() and pci_enable_msi_block() all drivers using these two interfaces need to be updated to use the new pci_enable_msi_range() or pci_enable_msi_exact() and pci_enable_msix_range() or pci_enable_msix_exact() interfaces.

linus-next stats (Re: Linux 3.15-rc1 out, merge window closed)

As usual, the executive friendly graph is at http://neuling.org/linux-next-size.html :-) (No merge commits counted, next-20140331 was the last linux-next before v3.14. I neglected to publish the stats for v3.14-rc1, but they are mentioned below.) Commits in v3.15-rc1 (relative to v3.14): 12034

[PATCH v2 RESEND 09/23] hpsa: Fallback to MSI rather than to INTx if MSI-X failed

Currently the driver falls back to INTx mode when MSI-X initialization failed. This is a suboptimal behaviour for chips that also support MSI. This update changes that behaviour and falls back to MSI mode in case MSI-X mode initialization failed. Signed-off-by: Alexander Gordeev Cc: "Stephen M.

Re: [tip:x86/urgent] x86-64, modify_ldt: Ban 16-bit segments on 64-bit kernels

Linus Torvalds writes: > On Fri, Apr 11, 2014 at 11:45 AM, Brian Gerst wrote: >> >> I haven't tested it recently but I do know it has worked on 64-bit >> kernels. There is no reason for it not to, the only thing not >> supported in long mode is vm86. 16-bit protected mode is unchanged. > >

[PATCH v2 RESEND 22/23] qla4xxx: Use pci_enable_msix_exact() instead of pci_enable_msix()

As result of deprecation of MSI-X/MSI enablement functions pci_enable_msix() and pci_enable_msi_block() all drivers using these two interfaces need to be updated to use the new pci_enable_msi_range() or pci_enable_msi_exact() and pci_enable_msix_range() or pci_enable_msix_exact() interfaces.

Aw: Re: new module to check constant memory for corruption

Hi Andi, I would like to ask for your help. Is there a central kernel function that enables/disables write-protection for kernel memory? I only know the place, where its write protected at booting for x86/x64. If there is one place, it would be much easier, as to hook into many places (e.g.

[PATCH 0/6] input: cyapa: integrated with gen5 trackpad supported in one driver.

This patch set is made based on kernel 3.14.0. It's aimed to re-architecture the cyapa driver to support the old gen3 trackpad device and new gen5 trackpad device in one cyapa driver for easily products support based on customers' requirements, and add sysfs functions and interfaces supported that

[PATCH 3/6] input: cyapa: add power mode sleep and runtime power mode supported.

In order to save power when the trackpad device is not used, the sleep power mode and runtime power mode must be supported. And the enter sleep time can be configured in the sysfs system. TEST=test on Chomebooks. Signed-off-by: Du, Dudley --- diff --git a/drivers/input/mouse/cyapa.c

[PATCH 4/6] input: cyapa: enable/disable trackpad device based on LID state

Rely on EV_SW and SW_LID bits to identify a LID device, and hook up our filter to listen for SW_LID events to enable/disable touchpad when LID is open/closed. TEST=test on Chomebooks. Signed-off-by: Du, Dudley --- diff --git a/drivers/input/mouse/cyapa.c b/drivers/input/mouse/cyapa.c index

Re: [PATCH] workqueue: fix double unlock bug

2014-04-14 15:50 GMT+09:00 Lai Jiangshan : > On 04/14/2014 08:58 AM, Daeseok Youn wrote: >> >> mutex_unlock() and put_pwq_unlocked() do not need to be called >> when alloc_unbound_pwq() is failed. >> >> Signed-off-by: Daeseok Youn >> --- >> kernel/workqueue.c |2 +- >> 1 files changed, 1

[PATCH v3 resend] clk: s2mps11: Add support for S2MPS14 clocks

This patch adds support for S2MPS14 PMIC clocks (BT and AP) to the s2mps11 clock driver. Signed-off-by: Krzysztof Kozlowski Cc: Kyungmin Park Reviewed-by: Yadwinder Singh Brar Reviewed-by: Tomasz Figa --- drivers/clk/Kconfig | 8 +++ drivers/clk/clk-s2mps11.c | 61

[PATCH v3 resend] clk: s2mps11: Add support for S2MPS14 clocks

Hi, This is a resend of third version of patchset adding support for the S2MPS14 device to the s2mps11 clock driver. Previous discusson can be found here: http://thread.gmane.org/gmane.linux.kernel.samsung-soc/28039 Changes since v2: = 1. Patch 2/3: Remove MFD cells

Re: [Patch v3 2/6] IIO: core: Introduce read_raw_multi

On April 14, 2014 2:51:22 AM GMT+01:00, Srinivas Pandruvada wrote: > >On 04/12/2014 09:52 AM, Jonathan Cameron wrote: >> On 09/04/14 01:56, Srinivas Pandruvada wrote: >>> This callback is introduced to overcome some limitations of existing >>> read_raw callback. The functionality of both

[PATCH V2] tty: fix memleak in alloc_pid

There is memleak in alloc_pid: -- unreferenced object 0xd3453a80 (size 64): comm "adbd", pid 1730, jiffies 66363 (age 6586.950s) hex dump (first 32 bytes): 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 40 c2 f6 d5 00 d3 25 c1

[RFC PATCH v3] Use kernfs_break_active_protection() for device online store callbacks

I noticed following lockdep warning when trying acpi hot-remove cpus: [84154.204080] == [84154.204080] [ INFO: possible circular locking dependency detected ] [84154.204080] 3.14.0-next-20140408+ #24 Tainted: GW [84154.204080]

[PATCH 0/8] Support 4 levels of translation tables for ARM64

Hi All, This patchset supports 4 levels of tranlsation tables for ARM64. Firstly, the patchset decouples page size from level of translation tables as taking account into the comment from Catalin Marinas: http://www.spinics.net/linux/lists/arm-kernel/msg319552.html Then, it implements 4 levels

[PATCH 3/8] arm64: Decouple page size from level of translation

This patch separates page size from level of translation tables in configuration. It facilitates introduction of different options, such as 4KB + 4 levels, 16KB + 4 levels and 64KB + 3 levels, easily. Signed-off-by: Jungseok Lee Reviewed-by: Sungjinn Chung --- arch/arm64/Kconfig

Re: [PATCH 2/2] [RFC v2 with seqcount] reservation: add suppport for read-only access using rcu

On 04/14/2014 09:42 AM, Maarten Lankhorst wrote: > op 11-04-14 21:35, Thomas Hellstrom schreef: >> On 04/11/2014 08:09 PM, Maarten Lankhorst wrote: >>> op 11-04-14 12:11, Thomas Hellstrom schreef: On 04/11/2014 11:24 AM, Maarten Lankhorst wrote: > op 11-04-14 10:38, Thomas Hellstrom

[PATCH 5/8] arm64: Add a description on 48-bit address space with 4KB pages

This patch adds memory layout and translation lookup information about 48-bit address space with 4K pages. The description is based on 4 levels of translation tables. Signed-off-by: Jungseok Lee Reviewed-by: Sungjinn Chung --- Documentation/arm64/memory.txt | 59

[PATCH resend] mfd/rtc: s5m: Do not allocate RTC I2C dummy and regmap for unsupported chipsets

The rtc-s5m driver does not support all of S2M and S5M chipsets supported by main MFD sec-core driver. For such chipsets unsupported by rtc-s5m, the MFD sec-core driver initialized regmap with default config. This config in such cases wouldn't work at all. The main MFD sec-core driver shouldn't

[PATCH 7/8] arm64: mm: Implement 4 levels of translation tables

This patch implements 4 levels of translation tables since 3 levels of page tables with 4KB pages cannot support 40-bit physical address space described in [1] due to the following issue. It is a restriction that kernel logical memory map with 4KB + 3 levels

[PATCH 6/8] arm64: Add 4 levels of page tables definition with 4KB pages

This patch adds hardware definition and types for 4 levels of translation tables with 4KB pages. Signed-off-by: Jungseok Lee Reviewed-by: Sungjinn Chung --- arch/arm64/include/asm/pgtable-4level-hwdef.h | 50 + arch/arm64/include/asm/pgtable-4level-types.h | 71

[PATCH 4/4] vfs: Block intuitively in the case of BSD accounting files

Have the mntput that started the BSD accounting files closing block until the superblock has been succesfully freed. This is what used to happen until fput started calling mntput assynchronously, and is arguably the right thing to do in the case of umount. Signed-off-by: "Eric W. Biederman"

Re: [PATCH 2/2] [RFC v2 with seqcount] reservation: add suppport for read-only access using rcu

op 11-04-14 21:35, Thomas Hellstrom schreef: On 04/11/2014 08:09 PM, Maarten Lankhorst wrote: op 11-04-14 12:11, Thomas Hellstrom schreef: On 04/11/2014 11:24 AM, Maarten Lankhorst wrote: op 11-04-14 10:38, Thomas Hellstrom schreef: Hi, Maarten. Here I believe we encounter a lot of locking

[PATCH 8/8] arm64: KVM: Implement 4 levels of translation tables for HYP and stage2

This patch adds 4 levels of translation tables implementation for both HYP and stage2. A combination of 4KB + 4 levels host and 4KB + 4 levels guest can run on ARMv8 architecture as introducing this feature. Signed-off-by: Jungseok Lee Reviewed-by: Sungjinn Chung --- arch/arm/kvm/mmu.c

[PATCH 3/4] vfs: In mntput run deactivate_super on a shallow stack.

mntput as part of path_put is called from all over the vfs sometimes as in the case of symlink chasing from some rather deep call chains. During lazy filesystem unmount with the right set of races those innocuous little mntput calls (that take very little stack space) can call deactivate_super

[PATCH 2/4] vfs: Move autoclose of BSD accounting into a work queue

The autoclose of BSD accounting writes a record to the BSD accounting file. When mntput is called from moderaly deep within the stack the (3KiB or so) generating I/O can be problemenatic as some I/O paths require nearly 5KiB of stack on their own. Avoid the possibility of stack overflow by

Re: [PATCH v3 1/1] pinctrl: add Intel BayTrail GPIO/pinctrl support

On 04/12/2014 01:54 AM, Timur Tabi wrote: On Tue, Jun 18, 2013 at 6:33 AM, Mathias Nyman wrote: Pins may be muxed to alternate function instead of gpio by firmware. This driver does not touch the pin muxing and expect firmare to set pin muxing and pullup/down properties properly.

[PATCH 1/4] vfs: Remove useless loop in mntput_no_expire

Remove the extra reference added to mnt_count by the mnt_pinned code, and stop jumping to the top of mntput_no_expire. When fput synchronously called mntput that extra reference count and the loop ensured that after acct_auto_close_mnt closed all of the pinned references mntput_no_expire would

[PATCH 1/8] arm64: Use pr_* instead of printk

This patch fixed the following checkpatch complaint as using pr_* instead of printk. WARNING: printk() should include KERN_ facility level Signed-off-by: Jungseok Lee Reviewed-by: Sungjinn Chung --- arch/arm64/kernel/traps.c | 14 +++--- 1 file changed, 7 insertions(+), 7

[PATCH 2/8] arm/arm64: KVM: Fix line length exceeding 80 characters

This patch deals with checkpatch complaint as fixing line length exceeding 80 characters. WARNING: line over 80 characters Signed-off-by: Jungseok Lee Reviewed-by: Sungjinn Chung --- arch/arm/kvm/mmu.c |4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git

[PATCH 4/8] arm64: Introduce a kernel configuration option for VA_BITS

This patch adds a kernel configuration for VA_BITS. It helps to prevent unnecessary #ifdef statements insertions for VA_BITS when implementing different page sizes and level of translation tables. Signed-off-by: Jungseok Lee Reviewed-by: Sungjinn Chung --- arch/arm64/Kconfig |

[RFC][PATCH 0/4] No I/O from mntput

There are a lot of ways we could approach this, and I sat down and wrote the simplest variant I could think of, so hopefully there are not silly bugs that get overlooked. The code move all cleanup from mntput that would do filesystem I/O into work queues. The code waits in mntput for that I/O

[PATCH] arm64:init: Move of_clk_init to time_init

Clock providers should be initialized before clocksource_of_init. If not, Clock source initialization can be fail to get the clock. Signed-off-by: Chanho Min --- arch/arm64/kernel/setup.c |1 - arch/arm64/kernel/time.c |3 ++- 2 files changed, 2 insertions(+), 2 deletions(-) diff

[PATCH V2] fs/jfs/jfs_inode.c: atomically set inode->i_flags

According to commit 5f16f3225b0624 ext4: atomically set inode->i_flags in ext4_set_inode_flags() Inspired-by: "Theodore Ts'o" Cc: Dave Kleikamp Cc: "Theodore Ts'o" Signed-off-by: Fabian Frederick --- fs/jfs/jfs_inode.c | 16 1 file changed, 8 insertions(+), 8 deletions(-)

Re: [PATCH v3 0/5] hugetlb: add support gigantic page allocation at runtime

Clear explanation and implementation! Reviewed-by: Zhang Yanfei On 04/11/2014 01:58 AM, Luiz Capitulino wrote: > [Full introduction right after the changelog] > > Changelog > - > > v3 > > - Dropped unnecessary WARN_ON() call [Kirill] > - Always check if the pfn range lies within a

Re: [PATCH v4 0/5] rework sched_domain topology description

On 12 April 2014 14:56, Dietmar Eggemann wrote: > On 11/04/14 10:44, Vincent Guittot wrote: >> >> This patchset was previously part of the larger tasks packing patchset >> [1]. >> I have splitted the latter in 3 different patchsets (at least) to make the >> thing easier. >> -configuration of

Re: [tip:x86/urgent] x86-64, modify_ldt: Ban 16-bit segments on 64-bit kernels

* H. Peter Anvin wrote: > On 04/11/2014 11:41 AM, Linus Torvalds wrote: > > > > Ok, so you actually do this on x86-64, and it currently works? For > > some reason I thought that 16-bit windows apps already didn't work. > > > > Some will work, because not all 16-bit software care about the

[tip:core/urgent] locking/mutex: Fix debug_mutexes

Commit-ID: a227960fe0cafcc229a8d6bb8b454a3a0b33719d Gitweb: http://git.kernel.org/tip/a227960fe0cafcc229a8d6bb8b454a3a0b33719d Author: Peter Zijlstra AuthorDate: Thu, 10 Apr 2014 16:15:59 +0200 Committer: Ingo Molnar CommitDate: Fri, 11 Apr 2014 10:40:35 +0200 locking/mutex: Fix

[tip:x86/urgent] x86/gpu: Fix sign extension issue in Intel graphics stolen memory quirks

Commit-ID: 86e587623a0ca8426267dad8d3eaebd6fc2d00f1 Gitweb: http://git.kernel.org/tip/86e587623a0ca8426267dad8d3eaebd6fc2d00f1 Author: Ville Syrjälä AuthorDate: Sun, 13 Apr 2014 12:45:03 +0300 Committer: Ingo Molnar CommitDate: Mon, 14 Apr 2014 08:50:56 +0200 x86/gpu: Fix sign

[tip:x86/urgent] x86/platform: Fix "make O=dir kvmconfig"

Commit-ID: f96364041ccda63ff4bed96fd06b267d8d841dc0 Gitweb: http://git.kernel.org/tip/f96364041ccda63ff4bed96fd06b267d8d841dc0 Author: Antonio Borneo AuthorDate: Sun, 13 Apr 2014 16:26:08 +0800 Committer: Ingo Molnar CommitDate: Mon, 14 Apr 2014 08:50:36 +0200 x86/platform: Fix "make

Re: [PATCH 1/1] FS: Add generic data flush to fsync

On Fri, Apr 11, 2014 at 11:05:30PM +0200, Fabian Frederick wrote: > Ok, that would mean 'older' filesystems -without barrier flag- > to call generic_file_fsync would result in a flush but ext4 without journal > also calls it ; maybe with nobarrier and I'm not sure it's the only case. > How can I

[PATCH] [PATCH V2] tty: memleak in alloc_pid

There is memleak in alloc_pid: -- unreferenced object 0xd3453a80 (size 64): comm "adbd", pid 1730, jiffies 66363 (age 6586.950s) hex dump (first 32 bytes): 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 40 c2 f6 d5 00 d3 25 c1

Re: [PATCH 1/1] ARM: dts: omap5: Add clocks to USB3 PHY node

Hi Tony, On 04/01/2014 05:13 PM, Felipe Balbi wrote: > On Tue, Apr 01, 2014 at 01:37:27PM +0300, Roger Quadros wrote: >> The USB3 PHY driver (ti-pipe3) was updated so that the relevant >> clock phandles are expected in the DT node. >> Provide the necessary clocks. >> >> Reported-by: Kishon Vijay

[tip:sched/urgent] sched/numa: Fix task_numa_free() lockdep splat

Commit-ID: 60e69eed85bb7b5198ef70643b5895c26ad76ef7 Gitweb: http://git.kernel.org/tip/60e69eed85bb7b5198ef70643b5895c26ad76ef7 Author: Mike Galbraith AuthorDate: Mon, 7 Apr 2014 10:55:15 +0200 Committer: Ingo Molnar CommitDate: Fri, 11 Apr 2014 10:39:15 +0200 sched/numa: Fix

<    5   6   7   8   9   10   11   12   13   14   >