Re: [PATCH] cpufreq, store_scaling_governor requires policy->rwsem to be held for duration of changing governors [v2]

On 5 August 2014 11:59, wrote: > Looks like Srivatsa has gone off the grid too. I'm hoping at least one of > you can do a review of my series. Come on guys, not everyone has to work > on the same patch/issue. :-( Srivatsa is currently going through some personal stuff. He is joining MIT for his

Re: [PATCHv2 5/6] base: platform: name the device already during allocation

On Mon, Jul 14, 2014 at 07:55:43AM -0700, Greg Kroah-Hartman wrote: > > > diff --git a/drivers/base/platform.c b/drivers/base/platform.c > > > index 9e9227e..e856bc4 100644 > > > --- a/drivers/base/platform.c > > > +++ b/drivers/base/platform.c > > > @@ -177,11 +177,45 @@ struct platform_object { >

Re: [PATCH] cpufreq, store_scaling_governor requires policy->rwsem to be held for duration of changing governors [v2]

Viresh Kumar wrote: > On 5 August 2014 01:46, Saravana Kannan wrote: >> The problem is when between one thread trying to cat a governor's file >> (say, >> sampling_rate) vs the governor getting a POLICY_EXIT. > > I don't see two threads racing against each other here. Simply changing > the govern

linux-next: manual merge of the char-misc tree with the slave-dma tree

Hi all, Today's linux-next merge of the char-misc tree got a conflict in drivers/dma/Makefile between commit b45b262cefd5 ("dmaengine: add a driver for AMBA AXI NBPF DMAC IP cores") from the slave-dma tree and commit 95b4ecbf759a ("dma: MIC X100 DMA Driver") from the char-misc tree. I fixed it up

Re: [PATCH 1/2] dma: imx-sdma: use module_platform_driver for SDMA driver

On Monday 04 August 2014 02:08 PM, Vinod Koul wrote: > On Mon, Aug 04, 2014 at 02:11:01PM +0530, Vignesh Raman wrote: >> On Thursday 31 July 2014 05:30 PM, Vinod Koul wrote: >>> On Wed, Jul 30, 2014 at 06:41:14PM +0530, Vignesh Raman wrote: Currently there is no module_exit declared in SDMA dr

[PATCH] drm/gma500: mdfld: Reuse video/mipi_display.h

From: Thierry Reding The GMA500 driver redefines many constants already found in the generic header. Replace uses of the custom defines by the standard ones and get rid of the duplicate defininitions. Signed-off-by: Thierry Reding --- drivers/gpu/drm/gma500/mdfld_dsi_pkg_sender.c | 75

Re: [PATCH] cpufreq_opp.c: Fixed the __might_sleep by changing GFP_KERNEL to GFP_ATOMIC.

On 5 August 2014 01:44, Anand Moon wrote: > Note: Generally, you should use GFP_ATOMIC in interrupt context > or in process context where it is not allowed to sleep, and GFP_KERNEL > elsewhere. > > This changes fixes bellow bug on ARM imx6 > > Signed-off-by: Anand Moon This should have come aft

Re: [PATCH] cpufreq, store_scaling_governor requires policy->rwsem to be held for duration of changing governors [v2]

On 5 August 2014 01:46, Saravana Kannan wrote: > The problem is when between one thread trying to cat a governor's file (say, > sampling_rate) vs the governor getting a POLICY_EXIT. I don't see two threads racing against each other here. Simply changing the governor from conservative->ondemand cr

Re: [PATCH 05/33] perf record: Allow the user to disable time stamps

* Arnaldo Carvalho de Melo wrote: > From: Andi Kleen > This patch looks dangerous and misleading to me. > Time stamps are always implicitely enabled for record currently. The > old --time/-T option is a nop. > > Allow the user to disable timestamps by using --no-time > > This can cause so

Re: [PATCH v1] phy: extend APIs of the generic phy framework

Hi, On Tuesday 05 August 2014 12:03 AM, yga...@codeaurora.org wrote: >> Hi, >> >> On Thursday 31 July 2014 06:07 PM, Yaniv Gardi wrote: >>> This change adds a few more APIs to the phy_ops structure: >>> advertise_quirks - API for setting the phy quirks >> >> What are these phy quirks? An explanati

Re: linux-next: build failures after merge of the drm tree

Hi Stephen and Dave, On 08/05/2014 12:09 PM, Stephen Rothwell wrote: Hi Dave, After merging the drm tree, today's linux-next build (x86_64 allmodconfig) failed like this: ERROR: "drm_sysfs_connector_remove" [drivers/gpu/drm/i2c/tda998x.ko] undefined! ERROR: "drm_sysfs_connector_add" [drivers/g

Re: [PATCH net-next 2/3] netlink: Convert netlink_lookup() to use RCU protected hash table

From: Eric Dumazet Date: Tue, 05 Aug 2014 07:50:07 +0200 > [PATCH net-next] netlink: fix lockdep splats > > With netlink_lookup() conversion to RCU, we need to use appropriate > rcu dereference in netlink_seq_socket_idx() & netlink_seq_next() > > Reported-by: Sasha Levin > Signed-off-by: Eric

Re: pull request: wireless-next 2014-08-01

From: Marcel Holtmann Date: Mon, 4 Aug 2014 22:39:47 -0700 > Hi Dave, > > Please pull this last(?) batch of wireless change intended for the > 3.17 stream... When I pull this I get tons of conflicts for: CONFLICT (content): Merge conflict in net/6lowpan/iphc.c

Re: [PATCH] xhci: Merge and Update debugging for patches from 3.6 kernel tree

On Tue, Aug 5, 2014 at 1:45 AM, Greg KH wrote: > On Tue, Aug 05, 2014 at 12:56:57AM -0400, Nicholas Krause wrote: >> I am adding the fixes to the tree send for adding debugging to the kernel >> tree from a patch sent in 2013 on the the 3.6 release. The patch adds >> debugging over xhci capable deb

Re: [PATCH net-next 2/3] netlink: Convert netlink_lookup() to use RCU protected hash table

On Mon, 2014-08-04 at 19:58 -0700, David Miller wrote: > From: Sasha Levin > Date: Mon, 04 Aug 2014 22:10:19 -0400 > > > On 08/02/2014 05:47 AM, Thomas Graf wrote: > >> static void *netlink_seq_start(struct seq_file *seq, loff_t *pos) > >> - __acquires(nl_table_lock) > >> { > >> - read_lock(&

Re: [PATCH] xhci: Merge and Update debugging for patches from 3.6 kernel tree

On Tue, Aug 05, 2014 at 12:56:57AM -0400, Nicholas Krause wrote: > I am adding the fixes to the tree send for adding debugging to the kernel > tree from a patch sent in 2013 on the the 3.6 release. The patch adds > debugging over xhci capable debugging usb ports and needed to be updated > into the

Re: [PATCH] sched: Reduce contention in update_cfs_rq_blocked_load

On Tue, Aug 05, 2014 at 03:15:26AM +0800, Yuyang Du wrote: > Hi Jason, > > I am not sure whether you noticed my latest work: rewriting per entity load > average > > http://article.gmane.org/gmane.linux.kernel/1760754 > http://article.gmane.org/gmane.linux.kernel/1760755 > http://article.gmane.or

[PATCH] kbuild: trivial - fix the help doc of CONFIG_CC_OPTIMIZE_FOR_SIZE

Other than GCC, we have another choice, Clang for building the kernel these days. It seems better to say "compiler" rather than "gcc". Signed-off-by: Masahiro Yamada --- init/Kconfig | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/init/Kconfig b/init/Kconfig index 41066e

Re: [PATCH] brcmfmac: prevent watchdog from interfering with scanning and connecting

On 2014/8/5 4:12, Arend van Spriel wrote: > On 08/04/14 18:52, Russell King - ARM Linux wrote: >> On Tue, Aug 05, 2014 at 12:36:49AM +0800, Fu, Zhonghui wrote: >>> Hi, Arend >>> >>> I investigated this issue, and its root cause is still that sdio >>> controller can't receive interrupts from WiFi c

Re: [PATCH 4/7] locking/rwsem: threshold limited spinning for active readers

On Mon, 2014-08-04 at 22:30 -0700, Davidlohr Bueso wrote: > On Mon, 2014-08-04 at 21:54 -0700, Davidlohr Bueso wrote: > > > #ifdef CONFIG_RWSEM_SPIN_ON_OWNER > > > +/* > > > + * The owner field is set to RWSEM_READ_OWNED if the last owner(s) are > > > + * readers. It is not reset until a writer ta

Re: pull request: wireless-next 2014-08-01

Hi Dave, Please pull this last(?) batch of wireless change intended for the 3.17 stream... >>> >>> When I pull this I get tons of conflicts for: >>> >>> CONFLICT (content): Merge conflict in net/6lowpan/iphc.c >>> >>> I don't feel comfortable fixing these up, where are they coming >>>

[PATCH v1] MIPS: perf: Mark pmu interupt IRQF_NO_THREAD

From: Yang Wei In RT kernel, I ran into the following calltrace, so PMU interrupts cannot be threaded in_atomic(): 1, irqs_disabled(): 1, pid: 0, name: swapper/0 INFO: lockdep is turned off. Call Trace: [] dump_stack+0x1c/0x50 [] __might_sleep+0x13c/0x148 [] rt_spin_lock+0x3c/0xb0 [] __wake_up+0

Re: [PATCH] brcmfmac: prevent watchdog from interfering with scanning and connecting

On 2014/8/5 0:52, Russell King - ARM Linux wrote: > On Tue, Aug 05, 2014 at 12:36:49AM +0800, Fu, Zhonghui wrote: >> Hi, Arend >> >> I investigated this issue, and its root cause is still that sdio >> controller can't receive interrupts from WiFi chip on sdio bus when >> sdio controller is in runt

Re: Kernel Debugging Support

On Mon, Aug 4, 2014 at 11:18 PM, Nick Krause wrote: > On Mon, Aug 4, 2014 at 9:33 PM, Nick Krause wrote: >> On Mon, Aug 4, 2014 at 8:12 PM, Sarah Sharp >> wrote: >>> On Mon, Aug 04, 2014 at 07:11:07PM -0400, Nick Krause wrote: On Mon, Aug 4, 2014 at 7:03 PM, Paul Zimmerman wrote:

Re: [PATCH 4/7] locking/rwsem: threshold limited spinning for active readers

On Mon, 2014-08-04 at 21:54 -0700, Davidlohr Bueso wrote: > > #ifdef CONFIG_RWSEM_SPIN_ON_OWNER > > +/* > > + * The owner field is set to RWSEM_READ_OWNED if the last owner(s) are > > + * readers. It is not reset until a writer takes over and set it to its > > + * task structure pointer or NULL wh

Re: Is lockref_get_not_zero() really correct in dget_parent()

On Mon, Aug 04, 2014 at 09:07:32PM -0700, Linus Torvalds wrote: > So renaming it to "lockref_get_active()", and changing the "not zero" > test to check for "positive" and change the rtype of "count" to be > signed, all sound like good things to me. Fine by me. I can do that, unless somebody else

Re: One bug of SDHCI driver

Hi, Jaehoon According to your comments, I created a new patch for this issue as follows: Thanks, Zhonghui >From 6cee984e1d76ba0a3320430f8cf4318ab65fcf06 Mon Sep 17 00:00:00 2001 From: Fu Zhonghui Date: Tue, 5 Aug 2014 12:44:38 +0800 Subject: [PATCH] mmc: core: sdio: Fix unconditional wake_up_

Re: Is lockref_get_not_zero() really correct in dget_parent()

On Mon, Aug 4, 2014 at 9:54 PM, Steven Noonan wrote: > On Mon, Aug 04, 2014 at 09:07:32PM -0700, Linus Torvalds wrote: >> On Mon, Aug 4, 2014 at 8:17 PM, NeilBrown wrote: >> > >> > I've been looking at last year's change to dentry refcounting which sets >> > the >> > refcount to -128 (mark_dea

Re: [PATCH 4/7] locking/rwsem: threshold limited spinning for active readers

On Sun, 2014-08-03 at 22:36 -0400, Waiman Long wrote: > Even thought only the writers can perform optimistic spinning, there > is still a chance that readers may take the lock before a spinning > writer can get it. In that case, the owner field will be NULL and the > spinning writer can spin indefi

Re: Is lockref_get_not_zero() really correct in dget_parent()

On Mon, Aug 04, 2014 at 09:07:32PM -0700, Linus Torvalds wrote: > On Mon, Aug 4, 2014 at 8:17 PM, NeilBrown wrote: > > > > I've been looking at last year's change to dentry refcounting which sets > > the > > refcount to -128 (mark_dead()) when the dentry is gone. > > > > As this is an "unsigne

Re: [PATCH 1/2] KVM: nVMX: Fix nested vmexit ack intr before load vmcs01

Hi Davidlohr, On Mon, Aug 04, 2014 at 12:56:36PM -0700, Davidlohr Bueso wrote: >On Fri, 2014-08-01 at 16:12 +0800, Wanpeng Li wrote: >> External interrupt will cause L1 vmexit w/ reason external interrupt when L2 >> is >> running. Then L1 will pick up the interrupt through vmcs12 if L1 set the ac

[PATCH v2 2/2] KVM: nVMX: fix acknowledge interrupt on exit when APICv is in use

After commit 77b0f5d (KVM: nVMX: Ack and write vector info to intr_info if L1 asks us to), "Acknowledge interrupt on exit" behavior can be emulated. To do so, KVM will ask the APIC for the interrupt vector if during a nested vmexit if VM_EXIT_ACK_INTR_ON_EXIT is set. With APICv, kvm_get_apic_inter

[PATCH v2 1/2] KVM: nVMX: Fix nested vmexit ack intr before load vmcs01

External interrupt will cause L1 vmexit w/ reason external interrupt when L2 is running. Then L1 will pick up the interrupt through vmcs12 if L1 set the ack interrupt bit. Commit 77b0f5d (KVM: nVMX: Ack and write vector info to intr_info if L1 asks us to) get intr that belongs to L1 before load v

Re: [PATCH? v2] x86: reimplement ___preempt_schedule*() using THUNK helpers

On Mon, 2014-08-04 at 19:36 +0200, Oleg Nesterov wrote: > Seems to work at least on x86_64, but I do not know how to test, lets see > what HPA thinks. Seeing the words "preempt" and "test", blindly feeding it to -rt seemed like a reasonable thing to do over morning java (la la la;)... it hasn't s

[GIT PULL] bcache changes for 3.17

Hey Jens, here's the pull request for 3.17 - typically late, but lots of tasty fixes in this one :) The following changes since commit 4c834452aad01531db949414f94f817a86348d59: Linux 3.16-rc3 (2014-06-29 14:11:36 -0700) are available in the git repository at: http://evilpiepirate.org/git/li

Re: [GIT PULL] Staging driver patches for 3.17-rc1

On Tue, Aug 05, 2014 at 06:13:25AM +0200, Andreas Mohr wrote: > > Lots of things in here, over 2000 patches, but the best part is this: > > 1480 files changed, 39070 insertions(+), 254659 deletions(-) > > > > Thanks to the great work of Kristina Martšenko, 14 different staging > > drivers have bee

Re: [PATCH] drivers/isdn/hisax/Kconfig: Let HISAX_NETJET skip microblaze architecture

On 08/05/2014 03:44 AM, Geert Uytterhoeven wrote: > On Mon, Aug 4, 2014 at 9:23 PM, Jean Delvare wrote: >>> --- a/drivers/isdn/hisax/Kconfig >>> +++ b/drivers/isdn/hisax/Kconfig >>> @@ -237,7 +237,7 @@ config HISAX_MIC >>> >>> config HISAX_NETJET >>> bool "NETjet card" >>> - depends o

Re: linux-next: build failures after merge of the drm tree

> Hi Dave, > > After merging the drm tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > ERROR: "drm_sysfs_connector_remove" [drivers/gpu/drm/i2c/tda998x.ko] > undefined! > ERROR: "drm_sysfs_connector_add" [drivers/gpu/drm/i2c/tda998x.ko] undefined! > I've fixed this,

Re: [GIT PULL] Staging driver patches for 3.17-rc1

> Lots of things in here, over 2000 patches, but the best part is this: > 1480 files changed, 39070 insertions(+), 254659 deletions(-) > > Thanks to the great work of Kristina Martšenko, 14 different staging > drivers have been removed from the tree as they were obsolete and no > one > was willing

Re: [PATCH 0/3] FS-Cache: Bug fixes for bugs that happen under vma pressure

David, I was away for a few days I'll take a look at your comments and respond appropriately within the next two days. - M On Tue, Jul 29, 2014 at 12:03 PM, David Howells wrote: > Did you mean to add Signed-off-by lines? > > David -- Milosz Tanski CTO 16 East 34th Street, 15th floor New York

[PATCH] perf/x86: fix load latency/precise store data source issues

This patch fixes some issues introduced by Andi's 'Revamp PEBS' event selection patch (which is under review right now). Most of the issues were related to the encoding of the data source, for PEBS events in general and load/store events on Haswell. This patchd does: - the default of 0 in perf_

Re: Is lockref_get_not_zero() really correct in dget_parent()

On Mon, Aug 4, 2014 at 8:17 PM, NeilBrown wrote: > > I've been looking at last year's change to dentry refcounting which sets the > refcount to -128 (mark_dead()) when the dentry is gone. > > As this is an "unsigned long" and there are several places where > d_lockref.count is compared e.g. ">

Re: [PATCH 8/8] msm: scm: Move the scm driver to drivers/soc/qcom

On Mon, 4 Aug 2014, Stephen Boyd wrote: > Architectural changes in the ARM Linux kernel tree mandate > the eventual removal of the mach-* directories. Move the > scm driver to drivers/soc/qcom and the scm header to > include/soc/qcom to support that removal. > > Signed-off-by: Stephen Boyd > ---

linux-next: is the kgdb tree still relevant?

Hi Jason, I have noticed that the kgdb tree contains 10 commits the last of which was committed on March 3, 2013. Should I drop this tree form linux-next? -- Cheers, Stephen Rothwells...@canb.auug.org.au signature.asc Description: PGP signature

Re: [PATCH] KVM: MMU: Use hashtable for MMU page hash

On 08/05/2014 04:54 AM, Sasha Levin wrote: > Use the kernel hashtable interface instead of the hlist interface. > This allows us to eliminate some unneeded code and make the code > simpler. The side effect is that the hash function is changed, the current way is: gfn & ((1 << KVM_MMU_HASH_

Re: [PATCH v3 2/2] usb: dwc2: add 'mode' which based on Kconfig select or dts setting

Kever, On Mon, Aug 4, 2014 at 6:45 PM, Kever Yang wrote: > Doug, > > > On 08/05/2014 12:34 AM, Doug Anderson wrote: >> >> Kever, >> >> On Mon, Aug 4, 2014 at 6:45 AM, Kever Yang >> wrote: >>> >>> According to the "dr_mode", the otg controller can work as >>> device role during firmware period, a

Re: [PATCH, RESEND] procfs: silence lockdep warning about read vs. exec seq_file

"Kirill A. Shutemov" writes: > From: "Kirill A. Shutemov" > > Testcase: > > cat /proc/self/maps >/dev/null > chmod +x /proc/self/net/packet > exec /proc/self/net/packet > > It triggers lockdep warning: > I don't know why we allow "chmod +x" on some proc files, notably net-related. > Is it

Re: [PATCH] sched: Reduce contention in update_cfs_rq_blocked_load

Hi Jason, I am not sure whether you noticed my latest work: rewriting per entity load average http://article.gmane.org/gmane.linux.kernel/1760754 http://article.gmane.org/gmane.linux.kernel/1760755 http://article.gmane.org/gmane.linux.kernel/1760757 http://article.gmane.org/gmane.linux.kernel/17

Is lockref_get_not_zero() really correct in dget_parent()

Hi, I've been looking at last year's change to dentry refcounting which sets the refcount to -128 (mark_dead()) when the dentry is gone. As this is an "unsigned long" and there are several places where d_lockref.count is compared e.g. "> 1", I start feeling uncomfortable, as "-128" is greate

Re: Kernel Debugging Support

On Mon, Aug 4, 2014 at 9:33 PM, Nick Krause wrote: > On Mon, Aug 4, 2014 at 8:12 PM, Sarah Sharp > wrote: >> On Mon, Aug 04, 2014 at 07:11:07PM -0400, Nick Krause wrote: >>> On Mon, Aug 4, 2014 at 7:03 PM, Paul Zimmerman >>> wrote: >>> >> From: Nick Krause [mailto:xerofo...@gmail.com] >> >> [sni

Re: Random panic in load_balance() with 3.16-rc

On Fri, 25 Jul 2014 11:29:06 -0700 Linus Torvalds wrote: > On Fri, Jul 25, 2014 at 7:02 AM, Steven Rostedt wrote: > > > > But wouldn't it be rather trivial to run a static analyzer on the final > > vmlinux to make sure there are no red zones? I mean, you would only need > > to read each function

Re: [GIT PULL] hwmon updates for 3.17

On 08/04/2014 08:14 PM, Stephen Rothwell wrote: Hi Guenter, On Mon, 4 Aug 2014 19:22:09 -0700 Guenter Roeck wrote: Hi Linus, Please pull hwmon updates for Linux 3.17 from signed tag: git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git hwmon-for-linus This branch w

[Bugfix 1/2] x86, irq, PCI: Keep IRQ assignment for PCI devices during suspend/hibernation

Now IOAPIC driver dynamically allocates IRQ numbers for IOAPIC pins. We need to keep IRQ assignment for PCI devices during suspend/hibernation, otherwise it may cause failure of suspend/hibernation due to: 1) Device driver calls pci_enable_device() to allocate an IRQ number and register interrup

[Bugfix 2/2] x86, irq: Keep balance of IOAPIC pin reference count

To keep balance of IOAPIC pin reference count, we need to protect pirq_enable_irq(), acpi_pci_irq_enable() and intel_mid_pci_irq_enable() from reentrance. There are two cases which will cause reentrance. The first case is caused by suspend/hibernation. If pcibios_disable_irq is called during suspe

[Bugfix 0/2] Fix bugs caused by "use irqdomain to dynamically allocate IRQ for IOAPIC"

Two issues have been reported against patch set "use irqdomain to dynamically allocate IRQ for IOAPIC" at https://lkml.org/lkml/2014/6/9/44. This first one causes failure of suspend/hibernation, please refer to https://lkml.org/lkml/2014/7/28/822 for more information. And we have worked out a patc

Re: [PATCH v2 18/18] Documentation: ACPI for ARM64

On 2014-8-5 4:48, Randy Dunlap wrote: > On 08/04/14 08:28, Hanjun Guo wrote: >> From: Graeme Gregory >> >> Add documentation for the guidelines of how to use ACPI >> on ARM64. >> >> Signed-off-by: Graeme Gregory >> Signed-off-by: Hanjun Guo >> --- >> Documentation/arm64/arm-acpi.txt | 215 >>

Re: [Linaro-acpi] [PATCH v2 00/18] Introduce ACPI for ARM64 based on ACPI 5.1

On 2014-8-5 1:30, Alexander Spyridakis wrote: > On 4 August 2014 17:28, Hanjun Guo > wrote: >> >> ACPI 5.1 has been released and now be freely available for >> download [1]. It fixed some major gaps to run ACPI on ARM, >> this patch just follow the ACPI 5.1 spec and p

Re: [PATCH] arch/sparc/math-emu/math_32.c: drop stray break operator

From: Andrey Utkin Date: Mon, 4 Aug 2014 23:47:41 +0300 > This commit is a guesswork, but it seems to make sense to drop this > break, as otherwise the following line is never executed and becomes > dead code. And that following line actually saves the result of > local calculation by the pointe

Re: [GIT PULL] hwmon updates for 3.17

Hi Guenter, On Mon, 4 Aug 2014 19:22:09 -0700 Guenter Roeck wrote: > > Hi Linus, > > Please pull hwmon updates for Linux 3.17 from signed tag: > > git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git > hwmon-for-linus This branch was rewritten (but not rebased) to add 5

[GIT PULL] ext4 bug updates for 3.17

The following changes since commit 1795cd9b3a91d4b5473c97f491d63892442212ab: Linux 3.16-rc5 (2014-07-13 14:04:33 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git tags/ext4_for_linus for you to fetch changes up to 86f0afd463215fc3e5

linux-next: build failures after merge of the drm tree

Hi Dave, After merging the drm tree, today's linux-next build (x86_64 allmodconfig) failed like this: ERROR: "drm_sysfs_connector_remove" [drivers/gpu/drm/i2c/tda998x.ko] undefined! ERROR: "drm_sysfs_connector_add" [drivers/gpu/drm/i2c/tda998x.ko] undefined! Caused by commit c707c3619ca8 ("drm/i

Re: Subject: [PATCH 1/1] mtd:nand:fix nand_lock/unlock() function

On Tue, Aug 05, 2014 at 01:54:07AM +, bpqw wrote: > From 0304e9618d8c3ef5360b611f881f1b1bed08be06 Mon Sep 17 00:00:00 2001 > From: White Ding > Date: Thu, 24 Jul 2014 00:10:45 +0800 > Subject: [PATCH 1/1] mtd:nand:fix nand_lock/unlock() function > > Do nand reset before write protect check. >

Re: [PATCH net-next 2/3] netlink: Convert netlink_lookup() to use RCU protected hash table

From: Sasha Levin Date: Mon, 04 Aug 2014 22:10:19 -0400 > On 08/02/2014 05:47 AM, Thomas Graf wrote: >> static void *netlink_seq_start(struct seq_file *seq, loff_t *pos) >> -__acquires(nl_table_lock) >> { >> -read_lock(&nl_table_lock); >> +rcu_read_lock(); >> return *pos ? netl

Re: [PATCH 2/2] softlockup: make detector be aware of task switch of processes hogging cpu

On 08/04/2014 10:31 PM, Don Zickus wrote: > On Mon, Aug 04, 2014 at 03:36:19PM +0800, chai wen wrote: >> >> For now, soft lockup detector warns once for each case of process softlockup. >> But the thread 'watchdog/n' may can not always get cpu at the time slot >> between >> the task switch of two

[RFC PATCH 3/3] ftracetest: Add kprobe basic testcases

Add basic testcases for kprobe dynamic events. This also shows that the ftracetest accepts sub-directory for new testcases. Signed-off-by: Masami Hiramatsu --- .../testing/ftrace/test.d/kprobe/add_and_remove.tc | 11 +++ tools/testing/ftrace/test.d/kprobe/busy_check.tc | 14 +++

[RFC PATCH 2/3] ftracetest: Add ftrace basic testcases

Add ftrace basic testcases. This just checks ftrace debugfs interface works as it is designed. Signed-off-by: Masami Hiramatsu --- tools/testing/ftrace/test.d/basic1.tc |3 +++ tools/testing/ftrace/test.d/basic2.tc |6 ++ tools/testing/ftrace/test.d/basic3.tc |8 3 files

[RFC PATCH 1/3] ftracetest: Initial commit for ftracetest

ftracetest is a collection of testcase shell-scripts for ftrace. To avoid regressions of ftrace, these testcases check correct ftrace behaviors. If someone would like to add any features on ftrace, the patch series should have at least one testcase for checking the new behavior. Signed-off-by: Mas

[RFC PATCH 0/3] ftrace: Add a ftrace test collection

Hi, I'd like to introduce a collection of testcases for ftrace to avoid regressions. For a long time, we've tried to stabilize and extend ftrace tracing infrastructure. This small test framework is a kind of stabilizing work for ftrace. For the first step, this series just introduces a few basic

Re: 3.16-rcX crashes on resume from Suspend-To-RAM

Hi, Markus, On Mon, 2014-08-04 at 09:06 -0700, Markus Gutschke wrote: > Thanks for checking in. And no, I have not heard from Zhang since my > last e-mail. I suspect he is still working on finding a solution. Yes, I was trying to find out what differences commit b04c58b1ed26317bfb4b33d3a2d16377fc

[GIT PULL] hwmon updates for 3.17

Hi Linus, Please pull hwmon updates for Linux 3.17 from signed tag: git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git hwmon-for-linus Thanks, Guenter -- The following changes since commit 64aa90f26c06e1cb2aacfb98a7d0eccfbd6c1a91: Linux 3.16-rc7 (2014-07-27 12:41

Re: [RFC PATCH 00/11] Refactor MSI to support Non-PCI device

On 2014/8/4 22:45, Arnd Bergmann wrote: > On Monday 04 August 2014, Yijing Wang wrote: >> I have another question is some drivers will request more than one >> MSI/MSI-X IRQ, and the driver will use them to process different things. >> Eg. network driver generally uses one of them to process trivia

Re: [RFC][PATCH 4/7] inotify: Deal with nested sleeps

I don't think this one needs nested sleeps. diff --git a/fs/notify/inotify/inotify_user.c b/fs/notify/inotify/inotify_user.c index cc423a3..1ca5888 100644 --- a/fs/notify/inotify/inotify_user.c +++ b/fs/notify/inotify/inotify_user.c @@ -233,15 +233,16 @@ static ssize_t inotify_read(struct file *fi

Re: [RFC PATCH 00/11] Refactor MSI to support Non-PCI device

>>> The method you describe here makes sense for PCI devices that are required >>> to support >>> legacy interrupts and may or may not support MSI on a given system, but not >>> so much >>> for platform devices for which we know exactly whether we want to use MSI >>> or legacy interrupts. >>> >>>

Re: [PATCH net-next 2/3] netlink: Convert netlink_lookup() to use RCU protected hash table

=== [ 531.482951] [ INFO: suspicious RCU usage. ] [ 531.485512] 3.16.0-next-20140804-sasha-00029-gcb12d07 #995 Not tainted [ 531.489198] --- [ 531.491518] net/netlink/af_netlink.c:2953 suspicious rcu_dereference_protected() usage! [ 531.495781] [ 531.495

Re: [request for help] tty: serial: kgdb: fix msm_serial for kgdb

On 8/4/2014 6:33 PM, Stephen Boyd wrote: > On 08/04/14 17:59, Frank Rowand wrote: >> Stephen, >> >> I made some changes to drivers/tty/serial/msm_serial.c to allow kgdb >> to work with the dragon board (which has a qcom,msm-uartdm-v1.4 serial >> port). >> >> I will reply to this email with the patc

Re: [PATCH v2 8/8] staging: iio: accel: sca3000_core.c: Add blank line between declarations and code

On Mon, 2014-08-04 at 22:47 -0300, Murilo Opsfelder Araujo wrote: > This patch adds missing blank line between declarations and code, and > adjust code to fit 80-chars limit. [] > diff --git a/drivers/staging/iio/accel/sca3000_core.c > b/drivers/staging/iio/accel/sca3000_core.c [] > @@ -506,7 +506

Re: zram: device management utility needed

On Wed, Jul 30, 2014 at 12:14:42AM +0100, Sami Kerola wrote: > Hello, > > Not so long ago Timofey has reached both util-linux[1] and kernel[2] > contributors with intention to make zram device management too. I think > the proposal is good, and there should be distribution independent tool > like

Re: btrfs extents related oops.

On Mon, Aug 04, 2014 at 09:28:45PM -0400, Dave Jones wrote: > Possibly related to some changes I've been making to my fuzz tester today > to operate on the same file from multiple threads. > This was on v3.16-829-g98959948a7ba, but probably exists on earlier trees too > given the lack of btrfs

RE: Subject: [PATCH 1/1] mtd:nand:fix nand_lock/unlock() function

>From 0304e9618d8c3ef5360b611f881f1b1bed08be06 Mon Sep 17 00:00:00 2001 From: White Ding Date: Thu, 24 Jul 2014 00:10:45 +0800 Subject: [PATCH 1/1] mtd:nand:fix nand_lock/unlock() function Do nand reset before write protect check. If we want to check the WP# low or high through STATUS READ and c

[PATCH v2 0/8] staging: iio: accel: Multiple coding style fixes

The following patches fix almost all warnings reported by checkpatch.pl. Changes from v1: - Updated commit messages to better reflect changes. Murilo Opsfelder Araujo (8): staging: iio: accel: adis16203_core.c: Add blank lines between declarations and code staging: iio: accel: adis16201_c

[PATCH v2 6/8] staging: iio: accel: lis3l02dq_core.c: Add blank lines between declarations and code

This patch adds missing blank line between declarations and code, satisfying checkpatch.pl. Signed-off-by: Murilo Opsfelder Araujo --- drivers/staging/iio/accel/lis3l02dq_core.c | 4 1 file changed, 4 insertions(+) diff --git a/drivers/staging/iio/accel/lis3l02dq_core.c b/drivers/staging/

[PATCH v2 5/8] staging: iio: accel: adis16240_core.c: Add blank line between declarations and code

This patch adds missing blank line between declarations and code, satisfying checkpatch.pl. Signed-off-by: Murilo Opsfelder Araujo --- drivers/staging/iio/accel/adis16240_core.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/staging/iio/accel/adis16240_core.c b/drivers/staging/iio/

[PATCH v6 1/7] kernel: Add support for kernel restart handler call chain

Various drivers implement architecture and/or device specific means to restart (reset) the system. Various mechanisms have been implemented to support those schemes. The best known mechanism is arm_pm_restart, which is a function pointer to be set either from platform specific code or from drivers.

[PATCH v2 3/8] staging: iio: accel: adis16204_core.c: Add blank line between declarations and code

This patch adds missing blank line between declarations and code, satisfying checkpatch.pl. Signed-off-by: Murilo Opsfelder Araujo --- drivers/staging/iio/accel/adis16204_core.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/staging/iio/accel/adis16204_core.c b/drivers/staging/iio/

[PATCH v6 3/7] arm: Support restart through restart handler call chain

The kernel core now supports a restart handler call chain for system restart functions. With this change, the arm_pm_restart callback is now optional, so check if it is set before calling it. Only call the kernel restart handler if arm_pm_restart is not set. Signed-off-by: Guenter Roeck Acked-by

[PATCH v6 4/7] power/restart: Call machine_restart instead of arm_pm_restart

machine_restart is supported on non-ARM platforms, and and ultimately calls arm_pm_restart, so dont call arm_pm_restart directly but use the more generic function. Cc: Russell King Signed-off-by: Guenter Roeck Acked-by: Catalin Marinas Acked-by: Heiko Stuebner --- v6: No change. v5: No change.

[PATCH v6 7/7] arm/arm64: Unexport restart handlers

Implementing a restart handler in a module don't make sense as there would be no guarantee that the module is loaded when a restart is needed. Unexport arm_pm_restart to ensure that no one gets the idea to do it anyway. Signed-off-by: Guenter Roeck Acked-by: Catalin Marinas Acked-by: Heiko Stueb

[PATCH v6 2/7] arm64: Support restart through restart handler call chain

The kernel core now supports a restart handler call chain to restart the system. Call it if arm_pm_restart is not set. Signed-off-by: Guenter Roeck Acked-by: Catalin Marinas Acked-by: Heiko Stuebner --- v6: No change. v5: Renamed restart function to do_kernel_restart v4: No change. v3: Use wrap

[PATCH v6 5/7] watchdog: moxart: Register restart handler with kernel restart handler

The kernel now provides an API to trigger a system restart. Register with it instead of setting arm_pm_restart. Signed-off-by: Guenter Roeck Acked-by: Catalin Marinas Acked-by: Heiko Stuebner --- v6: No change. v5: Functions and variables renamed: *notifier -> *handler v4: Set notifier priority

[PATCH v6 0/7] kernel: Add support for restart handler call chain

Various drivers implement architecture and/or device specific means to restart (reset) the system. Various mechanisms have been implemented to support those schemes. The best known mechanism is arm_pm_restart, which is a function pointer to be set either from platform specific code or from drivers.

[PATCH v6 6/7] watchdog: alim7101: Register restart handler with kernel restart handler

The kernel core now provides an API to trigger a system restart. Register with it to restart the system instead of misusing the reboot notifier. Signed-off-by: Guenter Roeck Acked-by: Catalin Marinas Acked-by: Heiko Stuebner --- v6: No change. v5: Function and variable renames: *notifier -> *ha

[PATCH v2 4/8] staging: iio: accel: adis16209_core.c: Add blank line between declarations and code

This patch adds missing blank line between declarations and code, satisfying checkpatch.pl. Signed-off-by: Murilo Opsfelder Araujo --- drivers/staging/iio/accel/adis16209_core.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/staging/iio/accel/adis16209_core.c b/drivers/staging/iio/

[PATCH v2 2/8] staging: iio: accel: adis16201_core.c: Add blank line between declarations and code

This patch adds missing blank line between declarations and code, and also fixes lines starting by space, satisfying checkpatch.pl. Signed-off-by: Murilo Opsfelder Araujo --- drivers/staging/iio/accel/adis16201_core.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/drive

[PATCH v2 8/8] staging: iio: accel: sca3000_core.c: Add blank line between declarations and code

This patch adds missing blank line between declarations and code, and ajust code to fit 80-chars limit. Signed-off-by: Murilo Opsfelder Araujo --- drivers/staging/iio/accel/sca3000_core.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/drivers/staging/iio/accel/sca3000_cor

Re: [PATCH v3 RESEND] zram: auto add new devices on demand

On Wed, Jul 30, 2014 at 10:58:31PM +0900, Sergey Senozhatsky wrote: > Hello, > > On (07/29/14 12:00), Minchan Kim wrote: > > Hello Timofey, > > > > Sorry for late response and thanks for suggesting new feature. > > > > First of all, I'd like to know your usecase. > > > > I don't mean I am again

[PATCH v2 7/8] staging: iio: accel: lis3l02dq_ring.c: Add blank line between declarations and code

This patch adds missing blank line between declarations and code, satisfying checkpatch.pl. Signed-off-by: Murilo Opsfelder Araujo --- drivers/staging/iio/accel/lis3l02dq_ring.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/staging/iio/accel/lis3l02dq_ring.c b/drivers/staging/iio/

[PATCH v2 1/8] staging: iio: accel: adis16203_core.c: Add blank lines between declarations and code

This patch adds missing blank lines between declarations and code, satisfying checkpatch.pl. Signed-off-by: Murilo Opsfelder Araujo --- drivers/staging/iio/accel/adis16203_core.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/staging/iio/accel/adis16203_core.c b/drivers/staging/i

Re: [PATCH v3 2/2] usb: dwc2: add 'mode' which based on Kconfig select or dts setting

Doug, On 08/05/2014 12:34 AM, Doug Anderson wrote: Kever, On Mon, Aug 4, 2014 at 6:45 AM, Kever Yang wrote: According to the "dr_mode", the otg controller can work as device role during firmware period, and work as host role in the kernel, without use of usb_id pin. As the commit "usb: dwc3:

Re: [PATCH v2 2/4] pinctrl: qpnp: Qualcomm PMIC pin controller driver

On 07/28/14 01:39, Ivan T. Ivanov wrote: > I am working on proposal from Stephen Boyd to encode GPIO/MPP mode and > source select into combined function. Something like this one: > > #define PM8XXX_DIGITAL_IN 0 > #define PM8XXX_DIGITAL_OUT1 > #define PM8XXX_DIGITAL_IN_OUT

[PATCH 2/8] msm: scm: Get cacheline size from CTR

Instead of hardcoding the cacheline size as 32, get the cacheline size from the CTR register. Signed-off-by: Stephen Boyd --- arch/arm/mach-qcom/scm.c | 14 -- 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/arch/arm/mach-qcom/scm.c b/arch/arm/mach-qcom/scm.c index 820c

  1   2   3   4   5   6   7   8   9   >