[PATCH 1/1] driver/tty: Fix a warning in check_tty_count

When there are to many open/close on a tty device in the same time, there may be a warning like: Warning: dev (ttyS0) tty->count(4) != #fd's(3) in tty_release_dev That's because tty->count and files in tty->tty_files are not synchronized in time. So I add a lock to avoid this. Signed-off-by:

Re: pull request: wireless-next 2014-07-11

From: "John W. Linville" Date: Fri, 11 Jul 2014 16:06:50 -0400 > Please pull this batch of updates intended for the 3.17 stream... > > This is primarily a Bluetooth pull. Gustavo says: > > "A lot of patches to 3.17. The bulk of changes here are for LE support. > The 6loWPAN over Bluetooth now

Re: [PATCH] ASoC: omap-dmic: Use devm_clk_get

On 07/11/2014 07:14 AM, Himangi Saraogi wrote: > This patch introduces the use of managed interfaces like devm_clk_get > and does away with the clk_puts in the probe and remove functions. A > label is also done away with. Acked-by: Peter Ujfalusi > > Signed-off-by: Himangi Saraogi > --- >

Re: [PATCHv8 2/2] mailbox: Introduce framework for mailbox

On 11 July 2014 22:56, Arnd Bergmann wrote: > On Friday 11 July 2014, Jassi Brar wrote: >> + >> + This document aims to help developers write client and controller >> +drivers for the API. But before we start, let us note that the >> +client (especially) and controller drivers are likely going to

[PATCH] cpufreq: Fix latency for cpufreq_info

This fixes the latency for the cpufreq policy to 1 million nanoseconds that calls the function pxa_cpu_init for the member of the structure called cpuinfo.transition_latency. Signed-off-by: Nicholas Krause --- drivers/cpufreq/pxa2xx-cpufreq.c | 2 +- 1 file changed, 1 insertion(+), 1

Re: [PATCHv8 2/2] mailbox: Introduce framework for mailbox

On 12 July 2014 03:39, Markus Mayer wrote: > On 11 July 2014 02:35, Jassi Brar wrote: >> Introduce common framework for client/protocol drivers and >> controller drivers of Inter-Processor-Communication (IPC). >> >> Client driver developers should have a look at >>

[PATCH V6] regulator: DA9211 : new regulator driver

This is the driver for the Dialog DA9211 Multi-phase 12A DC-DC Buck Converter regulator. It communicates via an I2C bus to the device. Signed-off-by: James Ban --- This patch is relative to linux-next repository tag next-20140710. Changes in V6: - Removed an unnecessary log. Changes in V5: -

Re: [RFC 0/7] hrtimer: drop active hrtimer checks after adding it

Hi Thomas, On 10 July 2014 07:04, Frederic Weisbecker wrote: > On Wed, Jul 09, 2014 at 11:30:41PM +0200, Thomas Gleixner wrote: >> On Wed, 9 Jul 2014, Viresh Kumar wrote: >> >> So your patch series drops active hrtimer checks after adding it, >> according to your subject line. >> >> Quite useeul

[RFC PATCH 0/3] hw_random: support for delayed init randomness requests

Hello, This series introduces a way to allow devices to contribute to initial system randomness after a certain delay. Specifically, the virtio-rng device can contribute initial randomness only after a successful probe(). A delayed workqueue item is queued in the system queue to fetch this

[RFC PATCH 1/3] hw_random: allow RNG devices to give early randomness after a delay

Some RNG devices may not be ready to give early randomness at probe() time, and hence lose out on the opportunity to contribute to system randomness at boot- or device hotplug- time. This commit schedules a delayed work item for such devices, and fetches early randomness after a delay. Currently

[RFC PATCH 3/3] Revert "virtio: rng: ensure reads happen after successful probe"

This reverts commit ceb5d72a2e27e95bc9570ce259c45b35f0e23462. This commit was added for -stable so systems with virtio-rng don't freeze at boot-time. With the addition of the previous commits that delay the request for initial randomness after probe() is successful, this is no longer needed.

[RFC PATCH 2/3] virtio: rng: only accept delayed early randomness requests

hw_random core can ask for initial randomness after a slight delay after probe() finishes, and we can contribute to system randomness at that point. Tell the hw_random core by setting the HWRNG_DELAY_READ_AT_INIT flag. CC: Kees Cook CC: Jason Cooper CC: Herbert Xu Signed-off-by: Amit Shah

Re: [PATCH v1] PCI: enable ASPM configuration in PCIE POWERSAVE mode

On Sat, Jul 12, 2014 at 4:14 AM, Bjorn Helgaas wrote: > [updated Naga's email address] > > On Wed, Jul 09, 2014 at 11:50:01PM +0530, vidya sagar wrote: >> On Tue, Jul 8, 2014 at 2:42 AM, Bjorn Helgaas wrote: >> > On Mon, Jul 7, 2014 at 12:00 PM, Vidya Sagar wrote: >> >>> -Original

[PATCH] ftrace: Do not copy old hash when resetting.

If we are going to reset hash, we don't need to duplicate old hash and remove every entries right after allocation. Signed-off-by: Wang Nan Cc: Steven Rostedt Cc: Ingo Molnar --- kernel/trace/ftrace.c | 8 +--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git

Re: [PATCHv8 2/2] mailbox: Introduce framework for mailbox

On 11 July 2014 17:16, Ashwin Chaugule wrote: > Hi Jassi, > > Other than a few nits, this looks good to me. > Thanks for the nits. I will club them together with other feedback on the patchset. > > Hopefully you've run this through checkpatch as well? Also, were you > able to sort out the

Re: [PATCH] Cpufreq: ARM IMX6Q: Select PM_OPP

On 14 July 2014 03:29, Nicolas Del Piano wrote: > PM_OPP is a library used by several of the existing cpufreq drivers. > ARM IMX6Q cpufreq driver uses this library for its functionality. > Thus, it should be selected in Kconfig. > > Reported-by: Ezequiel Garcia > Signed-off-by: Nicolas Del Piano

RE: [PATCH v6 2/6] ARM: EXYNOS: Move cpufreq and cpuidle device registration to init_machine

Hi Kukjin, On Thursday, July 10, 2014 7:04 PM, Kukjin wrote: > Pankaj Dubey wrote: > > > > Hi Kukjin, > > > Hi, > > > > > > > On 07/07/14 12:50, Pankaj Dubey wrote: > > > > As exynos_cpuidle_init and exynos_cpufreq_init function have just > > > > one lines of code for registering platform

[PATCH 1/1 V2] workqueue: unfold start_worker() into create_worker()

Simply unfold the code of start_worker() into create_worker() and remove the original start_worker() and create_and_start_worker(). The only trade-off is the introduced overhead that the pool->lock is released and re-grabbed after the newly worker is started. The overhead is acceptable since the

[PATCH 0/1 V2] workqueue: manager cleanup

Hi, TJ, I dropped the patch1 & patch2 of the V1, only the patch3 is kept and re-based. The new patch depends on the patch of last night: "workqueue: remove the del_timer_sync()s in maybe_create_worker()". Thanks, Lai Lai Jiangshan (1): workqueue: unfold start_worker() into create_worker()

[RESPIN PATCH v6] ARM: EXYNOS: Move cpufreq and cpuidle device registration to init_machine

As exynos_cpuidle_init and exynos_cpufreq_init function have just one lines of code for registering platform devices. We can move these lines to exynos_dt_machine_init and delete exynos_cpuidle_init and exynos_cpufreq_init function. This will help in reducing lines of code in exynos.c, making it

[PATCH v2] sched/deadline: overrun could happen in start_hrtick_dl

It could be wrong for the precision of runtime and deadline when the precision is within microsecond level. For example: Task runtime deadline period P1 200us 500us 500us This case need enbale HRTICK feature by the next command PC#echo "HRTICK" > /sys/kernel/debug/sched_features

Fix mes in arch/cris/arch-v32/kernel/kgdb.c

In the file arch/cris/arch-v32/kernel/kgdb.c , I am hitting a few fix mes that need to be fixed for kgdb support of this subsystem architecture of cris. Below this message are the lines of code and their respective Fix Me messages. When you around to it I would like to known how you would like

[PATCH net] mlx4: mark napi id for gro_skb

Napi id was not marked for gro_skb, this will lead rx busy loop won't work correctly since they stack never try to call low latency receive method because of a zero socket napi id. Fix this by marking napi id for gro_skb. The transaction rate of 1 byte netperf tcp_rr gets about 50% increased

Re: [RFC PATCH 0/2] irqchip: GIC: check and clear GIC interupt active status

On 2014/7/11 20:35, Will Deacon wrote: > [adding Marc] > > On Fri, Jul 11, 2014 at 07:46:15AM +0100, Liu Hua wrote: >> For this version of GIC codes, kernel assumes that all the interrupt >> status of GIC is inactive. So the kernel does not check this when >> booting. >> >> This is no problem on

RE: [PATCH 4/8] Drivers: scsi: storvsc: Filter WRITE_SAME_16

> -Original Message- > From: driverdev-devel-boun...@linuxdriverproject.org [mailto:driverdev- > devel-boun...@linuxdriverproject.org] On Behalf Of KY Srinivasan > Sent: Sunday, July 13, 2014 7:38 PM > To: Martin K. Petersen > Cc: linux-s...@vger.kernel.org; jasow...@redhat.com; linux- >

Re: [PATCH 2/2] staging: comedi: addi_apci_1564: use addi_watchdog module to init watchdog subdevice

On Sun, Jul 13, 2014 at 2:17 PM, Hartley Sweeten wrote: > On Saturday, July 12, 2014 3:44 PM, Chase Southwood wrote: >> Use the addi_watchdog module to provide support for the watchdog >> subdevice. >> >> Also, rearrange the subdevice init blocks so that the order makes sense. >> Digital

[PATCH] ARM: at91: at91sam9x5: correct typo error for ohci clock

Correct the typo error for the second "uhphs_clk". Signed-off-by: Bo Shen --- arch/arm/boot/dts/at91sam9x5.dtsi | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/arch/arm/boot/dts/at91sam9x5.dtsi b/arch/arm/boot/dts/at91sam9x5.dtsi index 2ebc421..727d3a4 100644 ---

[PATCH] xillybus: place 'else' on same line as '}'

Place 'else' on same line as closing brace '}' as per Documentation/CodingStyle. Fixes 1 error found by checkpatch.pl. Signed-off-by: Jeremiah Mahler --- drivers/staging/xillybus/xillybus_core.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git

RE: [PATCH 4/8] Drivers: scsi: storvsc: Filter WRITE_SAME_16

> -Original Message- > From: KY Srinivasan > Sent: Sunday, July 13, 2014 11:50 AM > To: 'Martin K. Petersen' > Cc: h...@infradead.org; James Bottomley; linux-kernel@vger.kernel.org; > de...@linuxdriverproject.org; a...@canonical.com; sta...@vger.kernel.org; > linux-s...@vger.kernel.org;

Re: [RFC][PATCH 1/3] ftrace/x86: Add dynamic allocated trampoline for ftrace_ops

(2014/07/04 5:07), Steven Rostedt wrote: > From: "Steven Rostedt (Red Hat)" > > The current method of handling multiple function callbacks is to register > a list function callback that calls all the other callbacks based on > their hash tables and compare it to the function that the callback

Re: [PATCH 1/3] workqueue: remove the first check and the return value of maybe_create_worker()

On 07/11/2014 11:03 PM, Tejun Heo wrote: > On Fri, Jul 11, 2014 at 12:01:03AM +0800, Lai Jiangshan wrote: >> @@ -1887,17 +1887,11 @@ static void pool_mayday_timeout(unsigned long __pool) >> * spin_lock_irq(pool->lock) which may be released and regrabbed >> * multiple times. Does GFP_KERNEL

Re: Re: [PATCH V8 2/2] serial/uart/8250: Add tunable RX interrupt trigger I/F of FIFO buffers

(2014/07/13 6:22), Greg KH wrote: On Thu, Jul 10, 2014 at 04:16:37PM -0700, Greg Kroah-Hartman wrote: On Thu, Jul 10, 2014 at 03:31:57PM +0100, One Thousand Gnomes wrote: I really don't like the way that the tty core has been changed to handle multiple attribute groups, as I feel tty drivers

Re: [PATCH] drivers/base: redundant return value settings in try_to_bring_up_master()

On 07/12/2014 08:58 AM, Greg KH wrote: On Tue, Jun 17, 2014 at 04:25:31PM +0800, Liu Ying wrote: Remove redundant return value settings 'ret = 0;' in the function try_to_bring_up_master(), since it has already been set to zero. Signed-off-by: Liu Ying --- drivers/base/component.c |2 --

Re: [PATCH 4/5] cgroup: distinguish the default and legacy hierarchies when handling cftypes

> @@ -3085,8 +3091,37 @@ static int cgroup_add_cftypes(struct cgroup_subsys > *ss, struct cftype *cfts) > return ret; > } > > +/** > + * cgroup_add_dfl_cftypes - add an array of cftypes for default hierarchy > + * @ss: target cgroup subsystem > + * @cfts: zero-length name terminated

Re: [PATCH 0/3] drm/gk20a: support for reclocking

On Fri, Jul 11, 2014 at 7:54 PM, Peter De Schrijver wrote: > On Fri, Jul 11, 2014 at 03:49:06AM +0200, Alex Courbot wrote: >> On 07/10/2014 06:43 PM, Peter De Schrijver wrote: >> > On Thu, Jul 10, 2014 at 09:34:34AM +0200, Alexandre Courbot wrote: >> >> This series adds support for reclocking on

Re: [PATCH 2/2] PCI/MSI: Remove arch_msi_check_device()

> /** > - * pci_msi_check_device - check whether MSI may be enabled on a device > + * msi_check_device - check whether MSI may be enabled on a device > * @dev: pointer to the pci_dev data structure of MSI device function > * @nvec: how many MSIs have been requested ? > - * @type: are we

Re: [Nouveau] [PATCH 0/3] drm/gk20a: support for reclocking

On Fri, Jul 11, 2014 at 10:38 AM, Alexandre Courbot wrote: > Hi Ben, > > > On 07/11/2014 10:07 AM, Ben Skeggs wrote: >> >> On Thu, Jul 10, 2014 at 5:34 PM, Alexandre Courbot >> wrote: >>> >>> This series adds support for reclocking on GK20A. The first two patches >>> touch >>> the clock

[tip:x86/apic] x86, vsmp: Remove is_vsmp_box() from apic_is_clustered_box()

Commit-ID: 411cf9ee2946492c0ac7eca48422fcf94a723ce5 Gitweb: http://git.kernel.org/tip/411cf9ee2946492c0ac7eca48422fcf94a723ce5 Author: Oren Twaig AuthorDate: Sun, 29 Jun 2014 13:01:08 +0300 Committer: H. Peter Anvin CommitDate: Sun, 13 Jul 2014 17:48:03 -0700 x86, vsmp: Remove

Re: [PATCH 10/11] perf, tools, test: Add test case for alias and JSON parsing

On Sun, Jul 13, 2014 at 10:09:45PM +0200, Jiri Olsa wrote: > On Sun, Jul 13, 2014 at 01:49:59AM +0200, Andi Kleen wrote: > > > missing the tests/aliases.o file > > > > > > AR libperf.a > > > ar: tests/aliases.o: No such file or directory > > > > Fixed here (and in git) > > got it, would

Re: [RFC][PATCH 0/3] ftrace: Add dynamically allocated trampolines

(2014/07/11 23:29), Josh Poimboeuf wrote: [...] > >>From 951d2aec17885a62905df6b910dc705d99c63993 Mon Sep 17 00:00:00 2001 > From: Josh Poimboeuf > Date: Fri, 11 Jul 2014 08:58:33 -0500 > Subject: [PATCH] x86/dumpstack: fix stack traces for generated code > > If a function in the stack trace is

Re: [PATCH] sched: select 'idle' cfs_rq per task-group to prevent tg-internal imbalance

On 07/12/2014 12:11 AM, Rik van Riel wrote: > -BEGIN PGP SIGNED MESSAGE- [snip] >> >> That's full wake balance.. if that was cheap, >> select_idle_sibling() would not exist. > > Full wake balance iterates over all the groups in the system, > select_idle_sibling only over one LLC domain.

[PATCH] add quirks for 0x04d9:0xa096 hid keyborad device

From: microcai I am using a USB keyborad that give me "usb_submit_urb(ctrl) failed: -1" error when I plugin it. and I need to wait for 10s for this device to be ready. by adding this quirks, the usb keyborad is usable right after plugin Signed-off-by: Wangzhao Cai --- drivers/hid/hid-ids.h

linux-next: manual merge of the mvebu tree with Linus' tree

Hi all, Today's linux-next merge of the mvebu tree got a conflict in arch/arm/Kconfig between commit 19682f72f5db ("ARM: Remove ARCH_HAS_CPUFREQ config option") from Linus' tree and commit ba364fc752da ("ARM: Kirkwood: Remove mach-kirkwood") from the mvebu tree. I fixed it up (The latter just

Re: [PATCH 4/6 v2] autofs4: factor should_expire() out of autofs4_expire_indirect.

Here is a revised version of this one patch. This one fixes a problem with refcounts on dentry and adds a comment to clarify the behaviour of should_expire(). thanks, NeilBrown From: NeilBrown Date: Tue, 8 Jul 2014 17:14:53 +1000 Subject: [PATCH] autofs4: factor should_expire() out of

Re: [PATCH v3] add quirks for 0x04d9:0xa096 hid keyborad device

I am using a USB keyboard that give me "usb_submit_urb(ctrl) failed: -1" error when I plugin it. and I need to wait for 10s for this device to be ready. by adding this quirks, the usb keyboard is usable right after plugin --- drivers/hid/hid-ids.h | 1 + drivers/hid/usbhid/hid-quirks.c

Fwd: PLEASE READ THE ATTACHED

Please kindly read the attached and get back to me Dear Friend.docx Description: MS-Word 2007 document

Re: [PATCH v3] staging: android: Clean up else statement from binder_send_failed_reply

Ok. I will do it. 4th could be the right one =p. Thanks for your time Cheers -- Lucas Tanure +55 (19) 988176559 On Sun, Jul 13, 2014 at 9:13 PM, Greg Kroah-Hartman wrote: > On Sun, Jul 13, 2014 at 08:25:13PM -0300, Lucas Tanure wrote: >> Kernel coding style. Remove useless else statement

[PATCH v4] staging: android: Clean up else statement from binder_send_failed_reply

Kernel coding style. Remove useless else statement after return. Changes from v1 and v2: Fix warning for mixed declarations and code. Declaration of "struct binder_transaction *next" made outside of while. Changes from v3: Removed initialization to NULL for next variable. Signed-off-by: Lucas

Re: [PATCH 2/6] samples: refactor Makefile

Hi Sam, On Sun, 13 Jul 2014 21:52:36 +0200 Sam Ravnborg wrote: > > On Sun, Jul 13, 2014 at 12:25:33PM -0700, Randy Dunlap wrote: > > On 07/13/14 11:42, Sam Ravnborg wrote: > > > Use one line per module/program in Makefile. > > > This style is easier to read/extend. > > > > > > Introduce inverse

Re: [PATCH v3] staging: android: Clean up else statement from binder_send_failed_reply

On Sun, Jul 13, 2014 at 08:25:13PM -0300, Lucas Tanure wrote: > Kernel coding style. Remove useless else statement after return. > Changes from v1 and v2: Fix warning for mixed declarations and code. > Declaration of "struct binder_transaction *next" made outside of while, > and initialized with

Re: [PATCH] thermal: samsung: Add TMU support for Exynos3250 SoC

Dear Eduardo, Could you please review or pick this patch? Best Regards, Chanwoo Choi On 07/10/2014 12:36 PM, Amit Kachhap wrote: > On Wed, Jul 9, 2014 at 8:30 AM, Chanwoo Choi wrote: >> On 07/01/2014 09:33 AM, Chanwoo Choi wrote: >>> This patch add registers, bit fields and compatible strings

Re: [PATCH] thermal: samsung: Add TMU support for Exynos3250 SoC

On 07/10/2014 12:36 PM, Amit Kachhap wrote: > On Wed, Jul 9, 2014 at 8:30 AM, Chanwoo Choi wrote: >> On 07/01/2014 09:33 AM, Chanwoo Choi wrote: >>> This patch add registers, bit fields and compatible strings for Exynos3250 >>> TMU >>> (Thermal Management Unit). Exynos3250 uses the Cortex-A7

Re: sched, timers: use after free in __lock_task_sighand when exiting a process

On 07/13/2014 05:51 PM, Sasha Levin wrote: > Hi all, > > While fuzzing with trinity inside a KVM tools guest running the latest -next > kernel with the KASAN patchset, I've stumbled on the following spew: Alrighty, I don't think it has anything to do with timers: [ 876.319044]

[PATCH v3] staging: android: Clean up else statement from binder_send_failed_reply

Kernel coding style. Remove useless else statement after return. Changes from v1 and v2: Fix warning for mixed declarations and code. Declaration of "struct binder_transaction *next" made outside of while, and initialized with NULL. Signed-off-by: Lucas Tanure ---

Re: [PATCH] drivers: staging: lustre: Use 'force_die' instead of 'die' to avoid compiling issue

On 07/14/2014 06:50 AM, Greg Kroah-Hartman wrote: > On Mon, Jul 14, 2014 at 06:38:24AM +0800, Chen Gang wrote: >> On 07/14/2014 06:31 AM, Chen Gang wrote: >>> On 07/14/2014 05:41 AM, Chen Gang wrote: On 07/14/2014 03:05 AM, Greg Kroah-Hartman wrote: > On Sun, Jul 13, 2014 at 10:50:55PM

Re: Additional performance data on Pavel's smb3 multi credit patch series

Impressive! On Sun, Jul 13, 2014 at 12:23 PM, Steve French wrote: > Performance of Pavel's multicredit i/o SMB3 patches continues to look > good. Additional informal performance results below comparing cifs > mounts with smb3 mounts (vers=3.0) with and without Pavel's patch set. > I plan to do

Re: [PATCH][RESEND] KVM: nVMX: Fix vmptrld fail and vmwrite error when L1 goes down

Hi Marcelo, On Fri, Jul 11, 2014 at 05:03:34PM -0300, Marcelo Tosatti wrote: >On Fri, Jul 11, 2014 at 12:22:17PM +0800, Wanpeng Li wrote: >> This bug can be trigger by L1 goes down directly w/ enable_shadow_vmcs. >> >> [ 6413.158950] kvm: vmptrld (null)/7800 failed >> [

Re: Additional performance data on Pavel's smb3 multi credit patch series

Repeating these large file copy tests with SMB3 mounts with Pavel's patches and trying larger wsize and rsize of 4MB (and later 5MB) did not seem to help performance much (over his default with the new patchset, 1MB). I want to repeat these with real network adapters (rather than in vmware or

Re: [PATCH 0/4 V3] irqchip: gic: Introduce ARM GICv2m MSI(-X) support

Suravee, On Wed, Jul 09, 2014 at 06:05:00PM -0500, suravee.suthikulpa...@amd.com wrote: > From: Suravee Suthikulpanit > > This patch set introduces support for MSI(-X) in GICv2m specification, > which is implemented in some variation of GIC400. > > This depends on and has been tested with the

Re: [PATCH 4/4 V3] irqchip: gicv2m: Add support for multiple MSI for ARM64 GICv2m

Suravee, If you need to respin this series, please change the subject line to "irqchip: gic-v2m: ..." If there are no other changes needed, It can be fixed up when applied. thx, Jason. On Wed, Jul 09, 2014 at 06:05:04PM -0500, suravee.suthikulpa...@amd.com wrote: > From: Suravee Suthikulpanit

Re: [PATCH 3/4 V3] irqchip: gic: Add supports for ARM GICv2m MSI(-X)

Suravee, On Wed, Jul 09, 2014 at 06:05:03PM -0500, suravee.suthikulpa...@amd.com wrote: > From: Suravee Suthikulpanit > > ARM GICv2m specification extends GICv2 to support MSI(-X) with > a new set of register frames. This patch introduces support for > the non-secure GICv2m register frame. > >

Re: [PATCH v2 02/15] ARM: pass IRQ domain to the core IRQ handler

Marc, On Tue, Jul 08, 2014 at 02:45:40PM +0100, Marc Zyngier wrote: > Calling irq_find_mapping from outside a irq_{enter,exit} section is > unsafe and produces ugly messages if CONFIG_PROVE_RCU is enabled: > If coming from the idle state, the rcu_read_lock call in irq_find_mapping > will generate

Re: [PATCH] drivers: staging: lustre: Use 'force_die' instead of 'die' to avoid compiling issue

On Mon, Jul 14, 2014 at 06:38:24AM +0800, Chen Gang wrote: > On 07/14/2014 06:31 AM, Chen Gang wrote: > > On 07/14/2014 05:41 AM, Chen Gang wrote: > >> On 07/14/2014 03:05 AM, Greg Kroah-Hartman wrote: > >>> On Sun, Jul 13, 2014 at 10:50:55PM +0800, Chen Gang wrote: > Some of architectures

Re: [PATCH] Staging: rtl8821ae: fix coding style issues in cam.c Fix all coding style error and warnings in cam.c reported by checkpatch.pl

On Sun, Jul 13, 2014 at 11:47:57PM +0200, Joerg C. Meyer wrote: > Signed-off-by: Joerg C. Meyer Your changelog body ended up in the Subject: line (that happens if you don't put a blank line after the first line in your git commit. Also, you don't say _what_ issues you fixed here, please be

Re: [PATCH v2 3.16] x86,kprobes: Don't try to resolve kprobe faults from userspace

(2014/07/12 2:27), Andy Lutomirski wrote: > This commit: > > commit 6f6343f53d133bae516caf3d254bce37d8774625 > Author: Masami Hiramatsu > Date: Thu Apr 17 17:17:33 2014 +0900 > > kprobes/x86: Call exception handlers directly from do_int3/do_debug > > appears to have

Re: [PATCH] drivers: staging: lustre: Use 'force_die' instead of 'die' to avoid compiling issue

On 07/14/2014 06:31 AM, Chen Gang wrote: > On 07/14/2014 05:41 AM, Chen Gang wrote: >> On 07/14/2014 03:05 AM, Greg Kroah-Hartman wrote: >>> On Sun, Jul 13, 2014 at 10:50:55PM +0800, Chen Gang wrote: Some of architectures have already defined 'die' as macro, so can not use this common

Re: [PATCH] drivers: staging: lustre: Use 'force_die' instead of 'die' to avoid compiling issue

On 07/14/2014 05:41 AM, Chen Gang wrote: > On 07/14/2014 03:05 AM, Greg Kroah-Hartman wrote: >> On Sun, Jul 13, 2014 at 10:50:55PM +0800, Chen Gang wrote: >>> Some of architectures have already defined 'die' as macro, so can not use >>> this common name as declaration in other modules, or will

Re: bit fields && data tearing

On Sun, 2014-07-13 at 09:15 -0400, Peter Hurley wrote: > > I'm not sure I understand your point here, Ben. > > Suppose that two different spinlocks are used independently to > protect r-m-w access to adjacent data. In Oleg's example, > suppose spinlock 1 is used for access to the bitfield and >

[PATCH] Cpufreq: ARM IMX6Q: Select PM_OPP

PM_OPP is a library used by several of the existing cpufreq drivers. ARM IMX6Q cpufreq driver uses this library for its functionality. Thus, it should be selected in Kconfig. Reported-by: Ezequiel Garcia Signed-off-by: Nicolas Del Piano --- drivers/cpufreq/Kconfig.arm |1 + 1 file changed,

[PATCH] Staging: rtl8821ae: fix coding style issues in cam.c Fix all coding style error and warnings in cam.c reported by checkpatch.pl

Signed-off-by: Joerg C. Meyer --- drivers/staging/rtl8821ae/cam.c | 57 +++-- 1 file changed, 27 insertions(+), 30 deletions(-) diff --git a/drivers/staging/rtl8821ae/cam.c b/drivers/staging/rtl8821ae/cam.c index 3bc6b3d..835bc3b 100644 ---

net: socket: NULL ptr deref in sendmsg

Hi all, While fuzzing with trinity inside a KVM tools guest running the latest -next kernel with the KASAN patchset, I've stumbled on the following spew: [ 4448.949424] == [ 4448.951737] AddressSanitizer: user-memory-access on

sched, timers: use after free in __lock_task_sighand when exiting a process

Hi all, While fuzzing with trinity inside a KVM tools guest running the latest -next kernel with the KASAN patchset, I've stumbled on the following spew: [ 4838.503887] == [ 4838.510906] AddressSanitizer: use after free in

Re: + shmem-fix-faulting-into-a-hole-while-its-punched-take-2.patch added to -mm tree

On 07/11/2014 11:59 AM, Peter Zijlstra wrote: >>> I agree with you that "The call trace is very clear on it that its not", but >>> > > when you have 500 call traces you really want something better than >>> > > going >>> > > through it one call trace at a time. >> > >> > Points well made, and I

Re: [PATCH] drivers: staging: lustre: Use 'force_die' instead of 'die' to avoid compiling issue

On 07/14/2014 03:05 AM, Greg Kroah-Hartman wrote: > On Sun, Jul 13, 2014 at 10:50:55PM +0800, Chen Gang wrote: >> Some of architectures have already defined 'die' as macro, so can not use >> this common name as declaration in other modules, or will cause compiling >> issue. So use more precise

Linux 3.16-rc5

Things are looking normal, and as usual, I _wish_ there was a bit less churn going on since it's getting fairly late in the rc cycle, but honestly, it's not like there is anything that really raises any eyebrows here. The bulk of this is drivers - with acpi and gpu sticking out, if only by a

[PATCH] :kernel :acct :fix coding style warnings and errors

Fixed coding style warnings and errors. Signed-off-by: Ionut Alexa --- kernel/acct.c | 30 +- 1 file changed, 17 insertions(+), 13 deletions(-) diff --git a/kernel/acct.c b/kernel/acct.c index 808a86f..1bfdda0 100644 --- a/kernel/acct.c +++ b/kernel/acct.c @@

Re: [PATCHv1 2/2] Documentation/kbuild/headers_install.txt: update documentation

On Sun, Jul 13, 2014 at 12:15:30PM +0200, Yann Droneaud wrote: > Documentation in kbuild/headers_install.txt is not > up to date regarding: > - way to list the various architectures; > - path where the headers are installed. > > This patch try to fix these issues. > > Cc: Kirill A. Shutemov >

Re: [PATCHv1 1/2] Documentation: headers_install.txt is part of kbuild

On Sun, Jul 13, 2014 at 12:15:29PM +0200, Yann Droneaud wrote: > 'headers_install.txt' from Documentation/make/ is related to Kbuild > so it must be moved in Documentation/kbuild/ directory. > > As Documentation/make/ directory has only one file, it will be removed > as a consequence of moving

Re: [PATCH v6 0/6] ima: extending secure boot certificate chain of trust

Dmitry Kasatkin wrote: > If patches from integrity/next-trusted-keys goes via your tree, then I > suggest that you re-base your patches on the top of our > patchset, because it is unclear how long review of PE, PKCS7 patches > will take and if they will be pulled... I'd rather not do that since

Fix Me in file gpmc-onenand.c

Hey Kevin, I am using cscope to find fix mes in the latest git kernels that still need cleanup. Furthermore I seem to hitting one in a that file that you maintain. Due to this I am wondering should I remove this code or does it still need to be in the mainline kernel and what mach-omap2 cpus does

Re: drm: i915: "plane B assertion failure, should be off on pipe B but is still active"

Paul Bolle schreef op wo 02-07-2014 om 10:53 [+0200]: > On Tue, 2014-07-01 at 12:17 +0300, Jani Nikula wrote: > > This does not ring any bells to me (but that doesn't prove anything). A > > bisect result would be awesome. The bisect (which took me quite some time) points at commit 98ec77397a5c

[PATCH] mtd: phram: Fix whitespace issues

>From ae6ea29f112475aa1e2da20caabe36e318fd51c4 Mon Sep 17 00:00:00 2001 From: Rob Ward Date: Sun, 13 Jul 2014 20:39:01 +0100 Subject: [PATCH] mtd: phram: Fix whitespace issues Fix various whitespace issues. No functional changes. Signed-off-by: Rob Ward --- drivers/mtd/devices/phram.c | 3

Re: [PATCH] drivers: Let several drivers depends on HAS_IOMEM for 'devm_ioremap_resource'

On Sun, Jul 13, 2014 at 09:33:38PM +0200, Richard Weinberger wrote: > Am 13.07.2014 21:22, schrieb Greg Kroah-Hartman: > > On Sun, Jul 13, 2014 at 04:25:06PM +0200, Lars-Peter Clausen wrote: > >> On 07/13/2014 04:03 PM, Richard Weinberger wrote: > >>> Am 13.07.2014 15:56, schrieb Lars-Peter

Re: [PATCH 2/6] samples: refactor Makefile

On 07/13/14 12:52, Sam Ravnborg wrote: > Hi Randy - thanks for the feedback. > > On Sun, Jul 13, 2014 at 12:25:33PM -0700, Randy Dunlap wrote: >> On 07/13/14 11:42, Sam Ravnborg wrote: >>> Use one line per module/program in Makefile. >>> This style is easier to read/extend. >>> >>> Introduce

Re: [PATCH 10/11] perf, tools, test: Add test case for alias and JSON parsing

On Sun, Jul 13, 2014 at 01:49:59AM +0200, Andi Kleen wrote: > > missing the tests/aliases.o file > > > > AR libperf.a > > ar: tests/aliases.o: No such file or directory > > Fixed here (and in git) got it, would you be ok with following change? using pr_* instead of fprintf calls..

[GIT PULL] ext4 bug fixes for 3.16

The following changes since commit 16874b2cb867d3eb63ed838f2847143e11556708: Merge tag 'ext4_for_linus_stable' of git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4 (2014-06-29 19:20:43 -0700) are available in the git repository at:

[PATCH v3] arm64,ia64,ppc,s390,sh,tile,um,x86,mm: Remove default gate area

The core mm code will provide a default gate area based on FIXADDR_USER_START and FIXADDR_USER_END if !defined(__HAVE_ARCH_GATE_AREA) && defined(AT_SYSINFO_EHDR). This default is only useful for ia64. arm64, ppc, s390, sh, tile, 64-bit UML, and x86_32 have their own code just to disable it.

Re: task's thread_info print in kernel oops

On 07/14, Vaibhav Shinde wrote: > > During the kernel oops i observed the below debug message which shows the > address of task's thread_info struct > > task: 880468e61a80 ti: 88026bc86000 task.ti: 88026bc86000 > > ti: > task.ti > As per my understanding, both the function calls will

Re: [PATCH 1/6] kbuild: add support for building userspace api programs

Hi Randy. Thanks, I will include all corrections in v3. Sam -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at

Re: [PATCH 2/6] samples: refactor Makefile

Hi Randy - thanks for the feedback. On Sun, Jul 13, 2014 at 12:25:33PM -0700, Randy Dunlap wrote: > On 07/13/14 11:42, Sam Ravnborg wrote: > > Use one line per module/program in Makefile. > > This style is easier to read/extend. > > > > Introduce inverse xmas style sorting. > > google search

Re: [RESEND PATCH] staging: android: Clean up binder_send_failed_reply

Sorry, I didn't know. I will fix. Thanks -- Lucas Tanure +55 (19) 988176559 On Sun, Jul 13, 2014 at 4:07 PM, Greg Kroah-Hartman wrote: > On Sun, Jul 13, 2014 at 11:49:29AM -0300, Lucas Tanure wrote: >> Kernel coding style. Remove useless else statement after return. >> >> Signed-off-by: Lucas

Re: [PATCH] drivers: Let several drivers depends on HAS_IOMEM for 'devm_ioremap_resource'

Am 13.07.2014 21:22, schrieb Greg Kroah-Hartman: > On Sun, Jul 13, 2014 at 04:25:06PM +0200, Lars-Peter Clausen wrote: >> On 07/13/2014 04:03 PM, Richard Weinberger wrote: >>> Am 13.07.2014 15:56, schrieb Lars-Peter Clausen: On 07/13/2014 03:40 PM, Richard Weinberger wrote: > Am

Re: [PATCH V2 1/4] staging: vt6556: Cleanup coding style issues

On Sun, Jul 13, 2014 at 09:11:18PM +0200, Peter Senna Tschudin wrote: > This patch cleanup coding style issues reported by checkpatch. > > Tested by compilation only. > > Signed-off-by: Peter Senna Tschudin > --- > Cahnges from V1: > - Sent all patches in a series Why did you forget the other

Re: [PATCH 2/6] samples: refactor Makefile

On 07/13/14 11:42, Sam Ravnborg wrote: > Use one line per module/program in Makefile. > This style is easier to read/extend. > > Introduce inverse xmas style sorting. google search couldn't tell me what that means and I cannot deduce it from the new Makefile ordering (if there is some ordering).

Additional performance data on Pavel's smb3 multi credit patch series

Performance of Pavel's multicredit i/o SMB3 patches continues to look good. Additional informal performance results below comparing cifs mounts with smb3 mounts (vers=3.0) with and without Pavel's patch set. I plan to do additional testing with large rsize/wsize (default with Pavel's code is

Re: [PATCH 1/6] kbuild: add support for building userspace api programs

Hi Sam, On 07/13/14 11:42, Sam Ravnborg wrote: > > diff --git a/Documentation/kbuild/makefiles.txt > b/Documentation/kbuild/makefiles.txt > index c600e2f..713ea10 100644 > --- a/Documentation/kbuild/makefiles.txt > +++ b/Documentation/kbuild/makefiles.txt > @@ -761,7 +763,43 @@ Both

RE: [PATCH 2/2] staging: comedi: addi_apci_1564: use addi_watchdog module to init watchdog subdevice

On Saturday, July 12, 2014 3:44 PM, Chase Southwood wrote: > Use the addi_watchdog module to provide support for the watchdog > subdevice. > > Also, rearrange the subdevice init blocks so that the order makes sense. > Digital input/output subdevices and subdevices for DI/DO interrupt > support,

Re: [PATCH] drivers: Let several drivers depends on HAS_IOMEM for 'devm_ioremap_resource'

On Sun, Jul 13, 2014 at 04:25:06PM +0200, Lars-Peter Clausen wrote: > On 07/13/2014 04:03 PM, Richard Weinberger wrote: > >Am 13.07.2014 15:56, schrieb Lars-Peter Clausen: > >>On 07/13/2014 03:40 PM, Richard Weinberger wrote: > >>>Am 13.07.2014 15:26, schrieb Lars-Peter Clausen: > On

[PATCH V2 2/4] staging: vt6556: Cleanup coding style issues

This patch cleanup coding style issues reported by checkpatch. Tested by compilation only. Signed-off-by: Peter Senna Tschudin --- Cahnges from V1: - Sent all patches in a series Made against latest staging-next. drivers/staging/vt6656/main_usb.c | 118 +-

[PATCH V2 1/4] staging: vt6556: Cleanup coding style issues

This patch cleanup coding style issues reported by checkpatch. Tested by compilation only. Signed-off-by: Peter Senna Tschudin --- Cahnges from V1: - Sent all patches in a series Made against latest staging-next. drivers/staging/vt6656/baseband.c | 28 1 file

  1   2   3   4   5   6   >