In vma_adjust, the current code grabs i_mmap_mutex before calling
vma_adjust_trans_huge. This used to be fine until huge page in page
cache comes in. The problem is the underlying function
split_file_huge_page will also grab the i_mmap_mutex before splitting
the huge page in page cache. Obviously
Most of the CPUFreq drivers do similar things in .exit() and .verify() routines
and .attr. So its better if we have generic routines for them which can be used
by cpufreq drivers then.
This patchset first fixes all existing drivers to do
cpufreq_frequency_table_put_attr() corresponding to
Drivers which have an exit path must call cpufreq_frequency_table_put_attr() if
they have called cpufreq_frequency_table_get_attr() in their init path.
This driver was missing this part and is fixed with this patch.
Cc: Kukjin Kim kgene@samsung.com
Signed-off-by: Viresh Kumar
Most of the CPUFreq drivers do similar things in .exit() and .verify() routines
and .attr. So its better if we have generic routines for them which can be used
by cpufreq drivers then.
This patch introduces generic .attr, .exit() and .verify() cpufreq drivers.
Cc: Andrew Lunn and...@lunn.ch
Cc:
Drivers which have an exit path must call cpufreq_frequency_table_put_attr() if
they have called cpufreq_frequency_table_get_attr() in their init path.
This driver was missing this part and is fixed with this patch.
Cc: Eric Miao eric.y.m...@gmail.com
Signed-off-by: Viresh Kumar
Drivers which have an exit path must call cpufreq_frequency_table_put_attr() if
they have called cpufreq_frequency_table_get_attr() in their init path.
This driver was missing this part and is fixed with this patch.
Cc: David S. Miller da...@davemloft.net
Cc: sparcli...@vger.kernel.org
Drivers which have an exit path must call cpufreq_frequency_table_put_attr() if
they have called cpufreq_frequency_table_get_attr() in their init path.
This driver was missing this part and is fixed with this patch.
Cc: Santosh Shilimkar santosh.shilim...@ti.com
Signed-off-by: Viresh Kumar
Drivers which have an exit path must call cpufreq_frequency_table_put_attr() if
they have called cpufreq_frequency_table_get_attr() in their init path.
This driver was missing this part and is fixed with this patch.
Cc: John Crispin blo...@openwrt.org
Signed-off-by: Viresh Kumar
Drivers which have an exit path must call cpufreq_frequency_table_put_attr() if
they have called cpufreq_frequency_table_get_attr() in their init path.
This driver was missing this part and is fixed with this patch.
Cc: Steven Miao real...@gmail.com
Signed-off-by: Viresh Kumar
Most of the CPUFreq drivers do similar things in .exit() and .verify() routines
and .attr. So its better if we have generic routines for them which can be used
by cpufreq drivers then.
This patch uses these generic routines for this driver.
Signed-off-by: Viresh Kumar viresh.ku...@linaro.org
---
Most of the CPUFreq drivers do similar things in .exit() and .verify() routines
and .attr. So its better if we have generic routines for them which can be used
by cpufreq drivers then.
This patch uses these generic routines for this driver.
Signed-off-by: Viresh Kumar viresh.ku...@linaro.org
---
Most of the CPUFreq drivers do similar things in .exit() and .verify() routines
and .attr. So its better if we have generic routines for them which can be used
by cpufreq drivers then.
This patch uses these generic routines for this driver.
Cc: Shawn Guo shawn@linaro.org
Signed-off-by:
Most of the CPUFreq drivers do similar things in .exit() and .verify() routines
and .attr. So its better if we have generic routines for them which can be used
by cpufreq drivers then.
This patch uses these generic routines for this driver.
Cc: Jesper Nilsson jesper.nils...@axis.com
Cc: Mikael
Most of the CPUFreq drivers do similar things in .exit() and .verify() routines
and .attr. So its better if we have generic routines for them which can be used
by cpufreq drivers then.
This patch uses these generic routines for this driver.
Cc: Hans-Christian Egtvedt egtv...@samfundet.no
Most of the CPUFreq drivers do similar things in .exit() and .verify() routines
and .attr. So its better if we have generic routines for them which can be used
by cpufreq drivers then.
This patch uses these generic routines for this driver.
Cc: Linus Walleij linus.wall...@linaro.org
Most of the CPUFreq drivers do similar things in .exit() and .verify() routines
and .attr. So its better if we have generic routines for them which can be used
by cpufreq drivers then.
This patch uses these generic routines for this driver.
Signed-off-by: Viresh Kumar viresh.ku...@linaro.org
---
Most of the CPUFreq drivers do similar things in .exit() and .verify() routines
and .attr. So its better if we have generic routines for them which can be used
by cpufreq drivers then.
This patch uses these generic routines for this driver.
Cc: Steven Miao real...@gmail.com
Signed-off-by: Viresh
Most of the CPUFreq drivers do similar things in .exit() and .verify() routines
and .attr. So its better if we have generic routines for them which can be used
by cpufreq drivers then.
This patch uses these generic routines for this driver.
Cc: Sekhar Nori nsek...@ti.com
Signed-off-by: Viresh
Most of the CPUFreq drivers do similar things in .exit() and .verify() routines
and .attr. So its better if we have generic routines for them which can be used
by cpufreq drivers then.
This patch uses these generic routines for this driver.
Cc: Kukjin Kim kgene@samsung.com
Signed-off-by:
Most of the CPUFreq drivers do similar things in .exit() and .verify() routines
and .attr. So its better if we have generic routines for them which can be used
by cpufreq drivers then.
This patch uses these generic routines for this driver.
Cc: Andrew Lunn and...@lunn.ch
Signed-off-by: Viresh
Most of the CPUFreq drivers do similar things in .exit() and .verify() routines
and .attr. So its better if we have generic routines for them which can be used
by cpufreq drivers then.
This patch uses these generic routines for this driver.
Signed-off-by: Viresh Kumar viresh.ku...@linaro.org
---
Most of the CPUFreq drivers do similar things in .exit() and .verify() routines
and .attr. So its better if we have generic routines for them which can be used
by cpufreq drivers then.
This patch uses these generic routines for this driver.
Signed-off-by: Viresh Kumar viresh.ku...@linaro.org
---
Most of the CPUFreq drivers do similar things in .exit() and .verify() routines
and .attr. So its better if we have generic routines for them which can be used
by cpufreq drivers then.
This patch uses these generic routines for this driver.
Signed-off-by: Viresh Kumar viresh.ku...@linaro.org
---
On Wed, Aug 7, 2013 at 11:46 AM, Michael Ellerman
mich...@ellerman.id.au wrote:
On powerpc we build kvmtool as a 64bit binary. We do that by setting
-m64 in our CFLAGS. For most things we just call $(CC) and it passes
that info onto the linker.
However there is one place where we explicitly
Most of the CPUFreq drivers do similar things in .exit() and .verify() routines
and .attr. So its better if we have generic routines for them which can be used
by cpufreq drivers then.
This patch uses these generic routines for this driver.
Signed-off-by: Viresh Kumar viresh.ku...@linaro.org
---
Most of the CPUFreq drivers do similar things in .exit() and .verify() routines
and .attr. So its better if we have generic routines for them which can be used
by cpufreq drivers then.
This patch uses these generic routines for this driver.
Cc: David S. Miller da...@davemloft.net
Signed-off-by:
Most of the CPUFreq drivers do similar things in .exit() and .verify() routines
and .attr. So its better if we have generic routines for them which can be used
by cpufreq drivers then.
This patch uses these generic routines for this driver.
Signed-off-by: Viresh Kumar viresh.ku...@linaro.org
---
Most of the CPUFreq drivers do similar things in .exit() and .verify() routines
and .attr. So its better if we have generic routines for them which can be used
by cpufreq drivers then.
This patch uses these generic routines for this driver.
Cc: Kukjin Kim kgene@samsung.com
Signed-off-by:
Most of the CPUFreq drivers do similar things in .exit() and .verify() routines
and .attr. So its better if we have generic routines for them which can be used
by cpufreq drivers then.
This patch uses these generic routines for this driver.
Cc: Tony Luck tony.l...@intel.com
Signed-off-by: Viresh
Most of the CPUFreq drivers do similar things in .exit() and .verify() routines
and .attr. So its better if we have generic routines for them which can be used
by cpufreq drivers then.
This patch uses these generic routines for this driver.
Cc: Shawn Guo shawn@linaro.org
Signed-off-by:
Most of the CPUFreq drivers do similar things in .exit() and .verify() routines
and .attr. So its better if we have generic routines for them which can be used
by cpufreq drivers then.
This patch uses these generic routines for this driver.
Cc: John Crispin blo...@openwrt.org
Signed-off-by:
Most of the CPUFreq drivers do similar things in .exit() and .verify() routines
and .attr. So its better if we have generic routines for them which can be used
by cpufreq drivers then.
This patch uses these generic routines for this driver.
Signed-off-by: Viresh Kumar viresh.ku...@linaro.org
---
Most of the CPUFreq drivers do similar things in .exit() and .verify() routines
and .attr. So its better if we have generic routines for them which can be used
by cpufreq drivers then.
This patch uses these generic routines for this driver.
Cc: Dmitry Eremin-Solenikov dbarysh...@gmail.com
Most of the CPUFreq drivers do similar things in .exit() and .verify() routines
and .attr. So its better if we have generic routines for them which can be used
by cpufreq drivers then.
This patch uses these generic routines for this driver.
Signed-off-by: Viresh Kumar viresh.ku...@linaro.org
---
Most of the CPUFreq drivers do similar things in .exit() and .verify() routines
and .attr. So its better if we have generic routines for them which can be used
by cpufreq drivers then.
This patch uses these generic routines for this driver.
Cc: Eric Miao eric.y.m...@gmail.com
Signed-off-by:
Most of the CPUFreq drivers do similar things in .exit() and .verify() routines
and .attr. So its better if we have generic routines for them which can be used
by cpufreq drivers then.
This patch uses these generic routines for this driver.
Cc: Kukjin Kim kgene@samsung.com
Signed-off-by:
Most of the CPUFreq drivers do similar things in .exit() and .verify() routines
and .attr. So its better if we have generic routines for them which can be used
by cpufreq drivers then.
This patch uses these generic routines for this driver.
Cc: Paul Mundt let...@linux-sh.org
Cc:
Most of the CPUFreq drivers do similar things in .exit() and .verify() routines
and .attr. So its better if we have generic routines for them which can be used
by cpufreq drivers then.
This patch uses these generic routines for this driver.
Signed-off-by: Viresh Kumar viresh.ku...@linaro.org
---
Most of the CPUFreq drivers do similar things in .exit() and .verify() routines
and .attr. So its better if we have generic routines for them which can be used
by cpufreq drivers then.
This patch uses these generic routines for this driver.
Cc: David S. Miller da...@davemloft.net
Signed-off-by:
Most of the CPUFreq drivers do similar things in .exit() and .verify() routines
and .attr. So its better if we have generic routines for them which can be used
by cpufreq drivers then.
This patch uses these generic routines for this driver.
Cc: David S. Miller da...@davemloft.net
Cc:
This tries to remove code redundancy from cpufreq driver by moving some common
part of them to the core. Each driver calls cpufreq_frequency_table_target() to
get a suitable index for a target frequency and then works on it. Its better to
do this at core level before calling cpufreq driver and
Most of the CPUFreq drivers do similar things in .exit() and .verify() routines
and .attr. So its better if we have generic routines for them which can be used
by cpufreq drivers then.
This patch uses these generic routines for this driver.
Cc: Guan Xuetao g...@mprc.pku.edu.cn
Signed-off-by:
Most of the CPUFreq drivers do similar things in .exit() and .verify() routines
and .attr. So its better if we have generic routines for them which can be used
by cpufreq drivers then.
This patch uses these generic routines for this driver.
Cc: Stephen Warren swar...@nvidia.com
Signed-off-by:
Most of the CPUFreq drivers do similar things in .exit() and .verify() routines
and .attr. So its better if we have generic routines for them which can be used
by cpufreq drivers then.
This patch uses these generic routines for this driver.
Cc: spear-de...@list.st.com
Signed-off-by: Viresh Kumar
Most of the CPUFreq drivers do similar things in .exit() and .verify() routines
and .attr. So its better if we have generic routines for them which can be used
by cpufreq drivers then.
This patch uses these generic routines for this driver.
Signed-off-by: Viresh Kumar viresh.ku...@linaro.org
---
Most of the CPUFreq drivers do similar things in .exit() and .verify() routines
and .attr. So its better if we have generic routines for them which can be used
by cpufreq drivers then.
This patch uses these generic routines for this driver.
Cc: Santosh Shilimkar santosh.shilim...@ti.com
Drivers which have an exit path must call cpufreq_frequency_table_put_attr() if
they have called cpufreq_frequency_table_get_attr() in their init path.
This driver was missing this part and is fixed with this patch.
Signed-off-by: Viresh Kumar viresh.ku...@linaro.org
---
On Wed, May 15, 2013 at 04:46:44PM +0800, Huang Shijie wrote:
Add a new sys node to show the ecc step size.
The application then can uses this node to get the ecc step
size.
Signed-off-by: Huang Shijie b32...@freescale.com
---
drivers/mtd/mtdcore.c | 11 +++
1 files changed, 11
Use devm_* functions in order to simplify cleanup
paths.
Signed-off-by: Gabor Juhos juh...@openwrt.org
---
drivers/tty/serial/ar933x_uart.c | 26 --
1 file changed, 8 insertions(+), 18 deletions(-)
diff --git a/drivers/tty/serial/ar933x_uart.c
Separate the W90X900(W90P910) on-chip host controller driver from
ehci-hcd host code so that it can be built as a separate driver module.
This work is part of enabling multi-platform kernels on ARM;
however, note that other changes are still needed before W90X900(W90P910)
can be booted with a
On Wed, Aug 07, 2013 at 02:54:27PM -0700, Kent Overstreet wrote:
This adds a generic mechanism for chaining bio completions. This is
going to be used for a bio_split() replacement, and some other things in
the future.
This is implemented with a new bio flag that bio_endio() checks; it
would
On Wed, May 15, 2013 at 04:46:46PM +0800, Huang Shijie wrote:
update the ecc step size when we have already get the right value.
Signed-off-by: Huang Shijie b32...@freescale.com
---
drivers/mtd/nand/gpmi-nand/gpmi-nand.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff
On 10 August 2013 12:14, Viresh Kumar viresh.ku...@linaro.org wrote:
This tries to remove code redundancy from cpufreq driver by moving some common
part of them to the core. Each driver calls cpufreq_frequency_table_target()
to
get a suitable index for a target frequency and then works on it.
On 10 August 2013 12:13, Viresh Kumar viresh.ku...@linaro.org wrote:
cpufreq: pass suitable index instead of freq to
cpufreq_driver-target()
This one is sent by mistake.. It isn't ready yet and will be sent separately
later. :(
--
To unsubscribe from this list: send the line unsubscribe
The problem here is that the dma_xfer() functions in
drivers/ata/pata_arasan_cf.c and drivers/mtd/nand/fsmc_nand.c expect
dma_submit_error() to return an error code so they return 1 when they
intended to return a negative.
So far as I can tell, none of the -tx_submit() functions ever do
return
v4: fixed broken BTN_TOUCH events
ideapad_slidebar is a new driver which enables slidebars on some
Lenovo IdeaPad laptops (the slidebars work with SlideNav/Desktop
Navigator under Windows)
Fixes this: https://bugzilla.kernel.org/show_bug.cgi?id=16004
Registers 'IdeaPad Slidebar' input device
On Sat, Aug 10, 2013 at 12:41 AM, Brian Norris
computersforpe...@gmail.com wrote:
On Wed, May 15, 2013 at 04:46:46PM +0800, Huang Shijie wrote:
update the ecc step size when we have already get the right value.
Signed-off-by: Huang Shijie b32...@freescale.com
---
On Thu, May 16, 2013 at 12:09:43PM +0800, Huang Shijie wrote:
We add a new sys node for ecc step. So update the ABI document about it.
Signed-off-by: Huang Shijie b32...@freescale.com
---
Documentation/ABI/testing/sysfs-class-mtd | 11 +++
1 files changed, 11 insertions(+), 0
Around Sat 10 Aug 2013 12:14:07 +0530 or thereabout, Viresh Kumar wrote:
Most of the CPUFreq drivers do similar things in .exit() and .verify()
routines
and .attr. So its better if we have generic routines for them which can be
used
by cpufreq drivers then.
This patch uses these generic
On 10.08.2013 03:07, Alan Stern wrote:
Nope. udevd refuses to start and says that it requires at least 2.6.32,
which means that apparently something changed in the kernel-userland
interface in 2.6.32. Thus, my conclusion that there's probably something
nasty going on in userland with udev.
Dear Jean-Francois Moine,
On Fri, 9 Aug 2013 11:06:23 +0200, Jean-Francois Moine wrote:
we need at least two more compatibles for the audio controller found on
Dove and Kirkwood respectively. This is how we are going to distinguish
those two, e.g. Kirkwood has SPDIF in which Dove hasn't.
On Sat, Aug 10, 2013 at 12:42:09AM +0100, Mark Brown wrote:
On Fri, Aug 09, 2013 at 09:38:47PM +0100, Russell King - ARM Linux wrote:
On Fri, Aug 09, 2013 at 08:44:34PM +0100, Mark Brown wrote:
If someone wants to it should also be possible to convert the existing
platforms without
On Fri 2013-08-02 01:43:55, Pavel Machek wrote:
On Sun 2013-07-28 15:44:09, Pavel Machek wrote:
On Mon 2013-07-15 01:28:19, Aaro Koskinen wrote:
Hi,
On Sat, Jul 13, 2013 at 02:17:09PM +0200, Pavel Machek wrote:
This adds device tree with neccessary support to boot with
On Sat, Aug 10, 2013 at 10:31:37AM +0100, Russell King - ARM Linux wrote:
Right, so what you're proposing is to come up with a DT description for
the existing stuff, and then have to change (or at the very least augment)
that description later when the DPCM stuff goes in.
What should be done
Hi Alan,
later... ok, bisected this even more. 2.6.31.14 kernel, old udev works
fine. Then removed /etc/rcS.d/S02udev to be sure the 2.6.32 kernel would
not pull the new udev. Rebuild 2.6.32.1 with *identical* kernel
configuration, booted up, manually started the *old* udev as in
2.6.31.14,
On Sat 2013-08-10 13:09:55, Pavel Machek wrote:
On Fri 2013-08-02 01:43:55, Pavel Machek wrote:
On Sun 2013-07-28 15:44:09, Pavel Machek wrote:
On Mon 2013-07-15 01:28:19, Aaro Koskinen wrote:
Hi,
On Sat, Jul 13, 2013 at 02:17:09PM +0200, Pavel Machek wrote:
This
Hi All,
On Sat, Aug 10, 2013 at 1:09 PM, Pavel Machek pa...@ucw.cz wrote:
On Fri 2013-08-02 01:43:55, Pavel Machek wrote:
On Sun 2013-07-28 15:44:09, Pavel Machek wrote:
On Mon 2013-07-15 01:28:19, Aaro Koskinen wrote:
Hi,
On Sat, Jul 13, 2013 at 02:17:09PM +0200, Pavel Machek wrote:
On Fri, 9 Aug 2013, David Daney wrote:
From: David Daney david.da...@cavium.com
When CONFIG_USB_SUPPORT is not selected we get things like:
scripts/kconfig/mconf Kconfig
warning: (MIPS_SEAD3 PMC_MSP CPU_CAVIUM_OCTEON) selects
USB_EHCI_BIG_ENDIAN_MMIO which has unmet direct
On Fri, Jul 19, 2013 at 06:04:33PM +0530, George Cherian wrote:
This patch series adds phy support for AM335X platform.
This patch series is based on Generic PHY framework [1].
This series has
- adds dual musb instances support for am335x platform
- adds phy-am-usb
On Sat, 10 Aug 2013, Thomas Richter wrote:
Which modules are relevant for handling the communication with the
device, and where would you suggest to start looking? I assume
yenta_socket is one thing for the cartbus adapter, then we have ehci_hcd
and ehci_pci. Do I assume correctly that we
On Fri, Aug 09, 2013 at 10:50:27AM -0400, Vince Weaver wrote:
On Wed, 7 Aug 2013, Arnaldo Carvalho de Melo wrote:
From: Jiri Olsa jo...@redhat.com
The only way to get the event ID is by reading the event fd,
followed by parsing the ID value out of the returned data.
While this is
Hi Linus
Please pull my for-linus branch:
git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus
These are assorted fixes, mostly from Josef nailing down xfstests runs.
Zach also has a long standing fix for problems with readdir wrapping
f_pos (or ctx-pos)
These patches
Some SoC have MMIO regions that are shared across orthogonal
subsystems. This commit implements a possible solution for the
thread-safe access of such regions through a spinlock-protected API
with clear-set semantics.
Concurrent access is protected with a single spinlock for the
entire MMIO
Following a suggestion from Sebastian Hesselbarth and Russell King
here's some work to introduce a generic thread-safe clear-set register
access.
The original motivation for this comes from the need to access the same
register from a clocksource driver and a watchdog driver as we find
in
Replace the driver-specific thread-safe shared register API
by the recently introduced atomic_io_clear_set().
Signed-off-by: Ezequiel Garcia ezequiel.gar...@free-electrons.com
---
drivers/clocksource/time-orion.c | 9 ++---
1 file changed, 2 insertions(+), 7 deletions(-)
diff --git
Since the timer control register is shared with the clocksource driver,
use the recently introduced atomic_io_clear_set() to access such register.
Signed-off-by: Ezequiel Garcia ezequiel.gar...@free-electrons.com
---
drivers/watchdog/orion_wdt.c | 8 ++--
1 file changed, 2 insertions(+), 6
Some SoC have MMIO regions that are shared across orthogonal
subsystems. This commit implements a possible solution for the
thread-safe access of such regions through a spinlock-protected API
with clear-set semantics.
Concurrent access is protected with a single spinlock for the
entire
When a UART transmitter is connected to (eg) a RS485 driver, it is
necessary to turn the driver on/off as quickly as possible. This is
best achieved in the serial driver itself (rather than in userspace
where the latency can be quite large).
This patch allows the GPIO pin to be defined (via DT)
On Fri, Aug 9, 2013 at 12:50 PM, Jason Cooper ja...@lakedaemon.net wrote:
Randy,
On Fri, Aug 09, 2013 at 09:41:38AM -0700, Randy Dunlap wrote:
On 08/09/13 07:59, Jason Cooper wrote:
Randy,
On Thu, Aug 08, 2013 at 01:03:04PM -0700, Randy Dunlap wrote:
On 08/08/13 00:08, Stephen Rothwell
On Sat, Aug 10, 2013 at 04:49:28PM +0400, Alexander Shiyan wrote:
Some SoC have MMIO regions that are shared across orthogonal
subsystems. This commit implements a possible solution for the
thread-safe access of such regions through a spinlock-protected API
with clear-set semantics.
On Sat, Aug 10, 2013 at 9:41 AM, zhangwei(Jovi) jovi.zhang...@gmail.com wrote:
On Sat, Aug 10, 2013 at 9:26 AM, zhangwei(Jovi) jovi.zhang...@gmail.com
wrote:
On Sat, Aug 10, 2013 at 12:20 AM, Oleg Nesterov o...@redhat.com wrote:
Sorry, I didn't read this series yet. Not that I think this
On Sat, Aug 10, 2013 at 11:02:38AM -0300, Ezequiel Garcia wrote:
On Sat, Aug 10, 2013 at 04:49:28PM +0400, Alexander Shiyan wrote:
Some SoC have MMIO regions that are shared across orthogonal
subsystems. This commit implements a possible solution for the
thread-safe access of such
commit 203489a33 (checkpatch: add --types option
to report only specific message types) uses a
perl syntax introduced in perl version 5.14.
Use the backward compatible perl syntax instead.
Reported-by: Julia Lawall julia.law...@lip6.fr
Signed-off-by: Joe Perches j...@perches.com
---
On Fri, Jul 19, 2013 at 09:50:15AM -0700, Luck, Tony wrote:
From: Naveen N. Rao naveen.n@linux.vnet.ibm.com
Randconfig testing found this error:
hest.c(.init.text+0x6004): undefined reference to 'mce_disable_bank'
Fix by wrapping body of hest_parse_cmc() inside #ifdef CONFIG_X86_MCE
On Sat, Aug 10, 2013 at 11:43:59AM +0800, Lai Jiangshan wrote:
Hi, Steven
I was considering rtmutex's lock-wait_lock is a scheduler lock,
But it is not, and it is just a spinlock of process context.
I hope you change it to a spinlock of irq context.
1) it causes rcu read site more
On Sat, Aug 10, 2013 at 08:07:15AM -0700, Paul E. McKenney wrote:
On Sat, Aug 10, 2013 at 11:43:59AM +0800, Lai Jiangshan wrote:
Hi, Steven
I was considering rtmutex's lock-wait_lock is a scheduler lock,
But it is not, and it is just a spinlock of process context.
I hope you change it
On Fri, Aug 09, 2013 at 11:54:49AM -0500, Aravind Gopalakrishnan wrote:
Adding support for handling ECC error decoding for new F15 models.
On newer models, support has been included for upto 4 DCT's, however,
only DCT0 and DCT3 are currently configured. (Refer BKDG Section 2.10)
Routing DRAM
From: Borislav Petkov b...@suse.de
Date: Sat, 10 Aug 2013 13:54:48 +0200
Subject: [PATCH] amd64_edac: Get rid of boot_cpu_data accesses
Now that we cache (family, model, stepping) locally, use them instead of
boot_cpu_data.
No functionality change.
Signed-off-by: Borislav Petkov b...@suse.de
Change isa bus to register dev_pm_ops via bus_type.pm. Add freeze ops for
PM_EVENT_FREEZE handling.
Signed-off-by: Shuah Khan shuah...@samsung.com
---
drivers/base/isa.c | 21 ++---
1 file changed, 18 insertions(+), 3 deletions(-)
diff --git a/drivers/base/isa.c
Change rtsx_pci_sdmmc platform driver to register pm ops using dev_pm_ops
instead of legacy pm_ops infrastructure.
Signed-off-by: Shuah Khan shuah...@samsung.com
---
drivers/mmc/host/rtsx_pci_sdmmc.c | 13 -
1 file changed, 8 insertions(+), 5 deletions(-)
diff --git
Change mvsd platform driver to register pm ops using dev_pm_ops instead of
legacy pm_ops infrastructure.
Signed-off-by: Shuah Khan shuah...@samsung.com
---
drivers/mmc/host/mvsdio.c | 13 +++--
1 file changed, 7 insertions(+), 6 deletions(-)
diff --git a/drivers/mmc/host/mvsdio.c
Fix the following build warning in sdh_dma_irq()
drivers/mmc/host/bfin_sdh.c:466:2: warning: format ‘%lx’ expects argument of
type ‘long unsigned int’, but argument 5 has type ‘int’ [-Wformat]
dev_dbg(mmc_dev(host-mmc), %s enter, irq_stat: 0x%04x\n, __func__,
From: Julia Lawall julia.law...@lip6.fr
Because ARRAY_AND_SIZE changes the apparent arity of a function, if it is
used for one call to a given function, it would be better, if possible, to
use it for all of them.
The semantic patch that fixes this problem is as follows:
Change tmio_mmc platform driver to register pm ops using dev_pm_ops instead of
legacy pm_ops infrastructure.
Signed-off-by: Shuah Khan shuah...@samsung.com
---
drivers/mmc/host/tmio_mmc.c | 24 ++--
1 file changed, 14 insertions(+), 10 deletions(-)
diff --git
Change bfin sdh platform driver to register pm ops using dev_pm_ops instead of
legacy pm_ops infrastructure.
Signed-off-by: Shuah Khan shuah...@samsung.com
---
drivers/mmc/host/bfin_sdh.c | 21 -
1 file changed, 12 insertions(+), 9 deletions(-)
diff --git
Change cb710_mmc platform driver register pm ops using dev_pm_ops instead of
legacy pm_ops infrastructure.
Signed-off-by: Shuah Khan shuah...@samsung.com
---
drivers/mmc/host/cb710-mmc.c | 11 +++
1 file changed, 7 insertions(+), 4 deletions(-)
diff --git
Change msmsdcc platform driver to register pm ops using dev_pm_ops instead of
legacy pm_ops infrastructure.
Signed-off-by: Shuah Khan shuah...@samsung.com
---
drivers/mmc/host/msm_sdcc.c | 13 +++--
1 file changed, 7 insertions(+), 6 deletions(-)
diff --git
Change au1xmmc platform driver to register pm ops using dev_pm_ops instead of
legacy pm_ops infrastructure.
Signed-off-by: Shuah Khan shuah...@samsung.com
---
drivers/mmc/host/au1xmmc.c | 15 +--
1 file changed, 9 insertions(+), 6 deletions(-)
diff --git
On Sat, 2013-08-10 at 17:25 +0200, Julia Lawall wrote:
From: Julia Lawall julia.law...@lip6.fr
Because ARRAY_AND_SIZE changes the apparent arity of a function, if it is
used for one call to a given function, it would be better, if possible, to
use it for all of them.
I think it'd be better
On Sat, 10 Aug 2013, Joe Perches wrote:
On Sat, 2013-08-10 at 17:25 +0200, Julia Lawall wrote:
From: Julia Lawall julia.law...@lip6.fr
Because ARRAY_AND_SIZE changes the apparent arity of a function, if it is
used for one call to a given function, it would be better, if possible, to
1 - 100 of 528 matches
Mail list logo
