> The pm8xxx read/write wrappers are no longer necessary now that
> all the sub-device drivers are using the regmap API. Remove it.
>
> Signed-off-by: Stephen Boyd
> ---
>
> Based on Linus' tip as of a7963eb7f4c4 (Merge branch 'for_linus' of
>
On 04/29/2014 04:52 PM, Lee Jones wrote:
>> This patch removes wrapper functions used to access regmap, and
>> make driver using regmap_*() functions instead.
>>
>> Signed-off-by: Robert Baldyga
>> ---
>> drivers/extcon/extcon-max77693.c | 32 ++---
>>
On Sun, Apr 27, 2014 at 12:05:56PM +0200, Jiri Olsa wrote:
> On Sat, Apr 26, 2014 at 01:17:55PM -0400, Richard Yao wrote:
> > Modules installed outside of the kernel's build system should go into
> > "%s/lib/modules/%s/extra", but at present, perf will only look at them
> > when they are in
Hi
On Thu, Apr 24, 2014 at 7:27 AM, Dmitry Torokhov
wrote:
> We put this workaround in 2008 and the offending userspace has been fixed
> up long time ago; the link in the message is no longer valid either, so it
> is time to retire it.
>
> Signed-off-by: Dmitry Torokhov
Yes, plase!
On 04/29/2014 01:34 PM, Viresh Kumar wrote:
> On 29 April 2014 13:05, Srivatsa S. Bhat
> wrote:
>> On 04/29/2014 12:19 PM, Viresh Kumar wrote:
>>> + WARN_ON(!(cpufreq_driver->flags & CPUFREQ_ASYNC_NOTIFICATION)
>>> && (current == policy->transition_task));
>>>
On Mon, Apr 28, 2014 at 09:23:04AM -0600, David Ahern wrote:
> On 4/28/14, 9:17 AM, Jiri Olsa wrote:
> >On Mon, Apr 28, 2014 at 09:01:57AM -0600, David Ahern wrote:
> >>On 4/28/14, 3:22 AM, Jiri Olsa wrote:
> >>>From: Jiri Olsa
> >>>
> >>>There's false assumption in the library detection code
>
Hi Kim,
> -Original Message-
> From: Jaegeuk Kim [mailto:jaegeuk@samsung.com]
> Sent: Tuesday, April 29, 2014 4:02 PM
> To: Chao Yu
> Cc: linux-f2fs-de...@lists.sourceforge.net; linux-fsde...@vger.kernel.org;
> linux-kernel@vger.kernel.org
> Subject: RE: [f2fs-dev][PATCH 3/3 v3] f2fs:
On 29.04.14 09:22:20, Masanari Iida wrote:
> Fix format string mismatch in oprofile_perf_create_files.
Please provide a compiler warning.
>
> Signed-off-by: Masanari Iida
> ---
> drivers/oprofile/oprofile_perf.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git
The site-specific OOM messages are unnecessary, because they
duplicate the MM subsystem generic OOM message.
Signed-off-by: Jingoo Han
---
drivers/char/hw_random/omap-rng.c |4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/char/hw_random/omap-rng.c
The site-specific OOM messages are unnecessary, because they
duplicate the MM subsystem generic OOM message.
Signed-off-by: Jingoo Han
---
drivers/char/hw_random/timeriomem-rng.c |4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/char/hw_random/timeriomem-rng.c
Hartley,
Ah geez...my brain got all tangled looking at old git commits for
other addi-data drivers. I apologize for this silly mistake. I'll
fix that title and send a new version of the patchset tomorrow.
Thanks,
Chase
On Mon, Apr 28, 2014 at 12:59 PM, Hartley Sweeten
wrote:
> On Saturday,
On Mon, Apr 28, 2014 at 10:27:48PM +0800, Lan Tianyu wrote:
> This patch is to add CONFIG_I2C_ACPI. Current there is a race between
> removing I2C ACPI operation region and ACPI AML code accessing.
> So make i2c core built-in if CONFIG_I2C_ACPI is set.
>
> Signed-off-by: Lan Tianyu
> ---
>
From: Srinivas Kandagatla
Hi Russell,
This patch series adds Qualcomm SD Card Controller support in pl180 mmci
driver. QCom SDCC is basically a pl180, but bit more customized, some of the
register layouts and offsets are different to the ones mentioned in pl180
datasheet. The plan is to totally
From: Srinivas Kandagatla
This patch adds Qualcomm amba vendor Id to the list. This ID is used in mmci
driver.
Signed-off-by: Srinivas Kandagatla
---
include/linux/amba/bus.h |1 +
1 file changed, 1 insertion(+)
diff --git a/include/linux/amba/bus.h b/include/linux/amba/bus.h
index
From: Srinivas Kandagatla
This patch adds a fake Qualcomm ID 0x00051180 to the amba_ids, as Qualcomm
SDCC controller is pl180, but amba id registers read 0x0's.
The plan is to remove SDCC driver totally and use mmci as the main SD
controller driver for Qualcomm SOCs.
Signed-off-by: Srinivas
From: Srinivas Kandagatla
Instance of this IP on Qualcomm's SOCs has bit different layout for datactrl
register. Bit postion datactrl[16:4] hold the true block size instead of power
of 2.
Signed-off-by: Srinivas Kandagatla
---
drivers/mmc/host/mmci.c |6 ++
1 file changed, 6
From: Srinivas Kandagatla
This patch adds wrappers for readl/writel functions used in the driver. The
reason for this wrappers is to accommodate SOCs like Qualcomm which has
requirement for delaying the write for few cycles when writing to its SD Card
Controller registers.
Signed-off-by:
From: Srinivas Kandagatla
This patch replaces a constant used in calculating timeout with a proper
macro. This is make code more readable.
Signed-off-by: Srinivas Kandagatla
---
drivers/mmc/host/mmci.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
From: Srinivas Kandagatla
Most of the Qcomm SD card controller registers must be updated to the MCLK
domain so subsequent writes to registers will be ignored until 3 clock cycles
have passed.
This patch adds a 3 clock cycle delay required after writing to controller
registers on Qualcomm SOCs.
From: Srinivas Kandagatla
This patch moves some of the ST specific register extensions access under
condition, so that other SOCs like Qualcomm or ARM would not a side effect of
writing to those reserved/different purpose bits.
Signed-off-by: Srinivas Kandagatla
---
drivers/mmc/host/mmci.c |
From: Srinivas Kandagatla
MCICLK register layout is bit different to the standard pl180 register layout.
Qcom SDCC controller some setup in MCICLK register to get it going. So this
patch adds new setup and makes it specific to Qcom hw designer.
Signed-off-by: Srinivas Kandagatla
---
From: Srinivas Kandagatla
Some bits which control Command Path State Machine (CPSM) are new in Qcom
integration, so this patch adds support to those bits.
Signed-off-by: Srinivas Kandagatla
---
drivers/mmc/host/mmci.c |4
drivers/mmc/host/mmci.h |7 +++
2 files changed, 11
From: Srinivas Kandagatla
MCICLK going to card bus is directly driven by the clock controller, so the
driver has to set the required rates depending on the state of the card. This
bit of support is very much similar to bypass mode but there is no such thing
called bypass mode in MCICLK register
From: Srinivas Kandagatla
MCIFIFOCNT register behaviour on Qcom chips is very different than the other
pl180 integrations. MCIFIFOCNT register contains the number of
words that are still waiting to be transferred through the FIFO. It keeps
decrementing once the host CPU reads the MCIFIFO. With
Hartley and Ian,
Yes, I had a feeling I should have gone with what was present, but my
desire to follow the documentation I wasn't too familiar with won out
:P
I'll spin a new revision of this patchset ASAP with this changed back
and all of my bad titles (oof...) fixed as well and I'll make sure
The site-specific OOM messages are unnecessary, because they
duplicate the MM subsystem generic OOM message. For example,
k.alloc and v.alloc failures use dump_stack().
Jingoo Han (4):
clocksource: em_sti: remove unnecessary OOM messages
clocksource: sh_cmt: remove unnecessary OOM
The site-specific OOM messages are unnecessary, because they
duplicate the MM subsystem generic OOM message.
Signed-off-by: Jingoo Han
---
drivers/clocksource/em_sti.c |4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/clocksource/em_sti.c
The site-specific OOM messages are unnecessary, because they
duplicate the MM subsystem generic OOM message.
Signed-off-by: Jingoo Han
---
drivers/clocksource/sh_mtu2.c |4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/clocksource/sh_mtu2.c
On Mon, 28 Apr 2014, Doug Anderson wrote:
> Lee,
>
> On Mon, Apr 28, 2014 at 4:57 AM, Lee Jones wrote:
> >> >> > Nearly all of the registers in tps65090 combine control bits and
> >> >> > status bits. Turn off caching of all registers except the select few
> >> >> > that can be cached.
> >> >>
The site-specific OOM messages are unnecessary, because they
duplicate the MM subsystem generic OOM message.
Signed-off-by: Jingoo Han
---
drivers/clocksource/sh_cmt.c |4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/clocksource/sh_cmt.c
On 04/29/2014 05:30 AM, Dave Jones wrote:
> On Tue, Apr 29, 2014 at 12:48:14AM +0530, Srivatsa S. Bhat wrote:
> > Hi,
> >
> > I hit this during boot on v3.15-rc3, just once so far.
> > Subsequent reboots went fine, and a few quick runs of multi-
> > threaded ebizzy also didn't recreate the
The site-specific OOM messages are unnecessary, because they
duplicate the MM subsystem generic OOM message.
Signed-off-by: Jingoo Han
---
drivers/clocksource/sh_tmu.c |4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/clocksource/sh_tmu.c
Adding test for building static perf build into the automated
suite. Also available via following commands:
$ make -f tests/make make_static
- make_static: cd . && make -f Makefile DESTDIR=/tmp/tmp.7u5MlB4njo
LDFLAGS=-static
$ make -f tests/make make_static_O
- make_static_O: cd . &&
This board always has 32 digital inputs. Remove the test when
initializing the subdevice.
Also, since this board is the only one supported by this driver,
remove the boardinfo about the digital inputs and just use the
data directly in the subdevice init.
Signed-off-by: Chase Southwood
Cc: Ian
Hello,
On 2014-04-28 20:09, Davidlohr Bueso wrote:
Performing vma lookups without taking the mm->mmap_sem is asking
for trouble. While doing the search, the vma in question can
be modified or even removed before returning to the caller.
Take the lock in order to avoid races while iterating
This driver only uses PCI bar 1 (devpriv->i_IobaseAmcc), and PCI bar 2
(dev->iobase) doon't bother reading the unused PCI bars.
Signed-off-by: Chase Southwood
Cc: Ian Abbott
Cc: H Hartley Sweeten
---
2: Bad PCI bar numbers corrected.
drivers/staging/comedi/drivers/addi_apci_1564.c | 11
The i_IorangeBase1, i_PCIEeprom, and pc_EepromChip data in the boardinfo
was only needed to work out the usage of the PCI bars. Now that that is
squared away, this info is no longer needed and can be removed.
Signed-off-by: Chase Southwood
Cc: Ian Abbott
Cc: H Hartley Sweeten
---
2: Incorrect
On Mon, Apr 28, 2014 at 09:13:04PM +0100, Paul E. McKenney wrote:
> On Mon, Apr 28, 2014 at 08:03:35PM +0100, Will Deacon wrote:
> > By the time rcutorture is initialised via its module_init callback, the
> > .init.text section of torture.ko has already been freed, so the calls to
> >
This driver no longer reads the eeprom to find the board specific data,
all the necessary data is in the boardinfo. Use the boardinfo directly
instead of passing through devpriv->s_EeParameters.
Signed-off-by: Chase Southwood
Cc: Ian Abbott
Cc: H Hartley Sweeten
---
2: Incorrect patch title
in
> console_trylock_for_printk() if we don't have a console to print to.
> Attached patch should fix the problem.
Besides it doesn't apply clearly on top of today's linux-next, it
doesn't fix the issue, but modifies it a bit.
[0.00]
Hi Jeff,
I've been looking a bit at the fcntl() documentation of traditional
(F_SETLK) record locking, and a question just jumped out at me. Is
it worth considering some future-proofing in the design of OFD locks
("open file description locks", formerly known as "file-private locks")?
What I
Hi,
On Mon, 28 Apr 2014 11:57:25 +0900
"yjay.kim" wrote:
> From: "yjay.kim"
>
> yield_task_dl() sets dl.dl_new as 1 and dequeue current dl task.
> After that it expects that next bandwidth timer callback `dl_task_timer()`
> will
> replenish budget of dl task and enqueue it again.
>
> But
On 04/25/2014 10:29 AM, Joonsoo Kim wrote:
On Wed, Apr 23, 2014 at 04:31:14PM +0200, Vlastimil Babka wrote:
Hello,
How about doing more clean-up at this time?
What I did is that taking end_pfn out of the loop and consider zone
boundary once. After then, we just subtract pageblock_nr_pages on
Peter,
Things have changed with regard to printk() in linux-next. Now it
appears that lockdep is going haywire over it. I don't understand the
exact reason for the lockdep_off() and lockdep_on() logic that is in
printk(), but it obviously seems to be causing issues with the new
changes.
Care to
On Mon, 28 Apr 2014 19:51:39 +0200
Jan Kara wrote:
> On Mon 28-04-14 13:43:31, Steven Rostedt wrote:
> > Things have changed with regard to printk() in linux-next. Now it
> > appears that lockdep is going haywire over it. I don't understand the
> > exact reason for the lockdep_off() and
[CC+= linux-nfs@]
On 04/29/2014 10:38 AM, Michael Kerrisk (man-pages) wrote:
> Hi Jeff,
>
> I've been looking a bit at the fcntl() documentation of traditional
> (F_SETLK) record locking, and a question just jumped out at me. Is
> it worth considering some future-proofing in the design of OFD
On Mon, Apr 28, 2014 at 10:21:34AM -0400, Vince Weaver wrote:
> so it's looking more and more like this issue is with a
> PERF_COUNT_SW_TASK_CLOCK
> event.
But they don't actually use the hlist thing..
> It's being deallocated in a different process than it was started (due to
> fork).
>
On Tue, Apr 29, 2014 at 12:51:18AM +0100, Rob Herring wrote:
> On Mon, Apr 28, 2014 at 1:50 PM, Marc Zyngier wrote:
> > Commit d57c33c5daa4 (add generic fixmap.h) added (among other
> > similar things) set_fixmap_io to deal with early ioremap of devices.
> >
> > More recently, commit bf4b558eba92
I am announcing the release of the Linux 3.11.10.9 kernel.
The updated 3.11.y tree can be found at:
git://kernel.ubuntu.com/ubuntu/linux.git linux-3.11.y
and can be browsed at:
http://kernel.ubuntu.com/git?p=ubuntu/linux.git;h=refs/heads/linux-3.11.y;a=shortlog
The diff from v3.11.10.8 is
On 28/04/14 18:44, Colin Cross wrote:
>>> Is that case documented somewhere in the code comments?
>>
>> Perhaps not near enough to the _nolock but the primary bit of comment is
>> here (and in same file as kdb_sr).
>> --- cut here ---
>> * kdb_main_loop - After initial setup and assignment of the
On 04/27/2014 11:28 PM, NeilBrown wrote:
> On Sun, 27 Apr 2014 13:11:33 +0200 "Michael Kerrisk (man-pages)"
> wrote:
>
>> On Sun, Apr 27, 2014 at 12:04 PM, NeilBrown wrote:
>>> On Sun, 27 Apr 2014 11:16:02 +0200 "Michael Kerrisk (man-pages)"
>>> wrote:
>>>
[Trimming some folk from CC, and
On Sun, Apr 27, 2014 at 01:06:42PM -0400, Oleg Drokin wrote:
> diff --git a/drivers/staging/lustre/lustre/llite/dir.c
> b/drivers/staging/lustre/lustre/llite/dir.c
> index 7fbc18e..c391b60 100644
> --- a/drivers/staging/lustre/lustre/llite/dir.c
> +++ b/drivers/staging/lustre/lustre/llite/dir.c
>
This patchset modifies max77693 driver and associated function drivers
to improve regmap support. It removes unnecessary wrapper functions,
which make code more clean, and modifies IRQ handling to use regmap irq.
Best regards
Robert Baldyga
Samsung R Institute Poland
Changelog:
v3:
- fix some
This patch modifies mfd driver to use regmap for handling interrupts.
It allows to simplify irq handling process. This modifications needed
to make small changes in function drivers, which use interrupts.
Signed-off-by: Robert Baldyga
Reviewed-by: Krzysztof Kozlowski
[For extcon part]
This patch removes wrapper functions used to access regmap, and
make driver using regmap_*() functions instead.
Signed-off-by: Robert Baldyga
Reviewed-by: Krzysztof Kozlowski
Acked-by: Lee Jones
[For extcon part]
Acked-by: Chanwoo Choi
---
drivers/extcon/extcon-max77693.c | 32
Hi,
This patch series is intended to:
* Introduce "manual mode" support (Patch 1 & 2), which is needed to control
the fan of a few new models.
* Add an appropriate thermal governor (Patch 3 & 4). Manipulating and
fiddling around with the step-wise governor has been a very fragile
On Mon, Apr 28, 2014 at 06:21:49PM +0100, Joel Fernandes wrote:
> On 04/28/2014 12:20 PM, Joel Fernandes wrote:
> > On 04/28/2014 11:43 AM, Dave Martin wrote:
> >> On Tue, Apr 22, 2014 at 01:31:46PM -0500, Joel Fernandes wrote:
> >>> On my DRA7 system, when the kernel is built in THUMB mode, the
Some Acer models require an additional command to turn off the fan after
bios mode has been enabled. Adding new section in bios table to allow
support for those models, by writing an extra "manual mode" register.
Cc: Andreas Mohr
Cc: Borislav Petkov
Signed-off-by: Peter Feuerer
---
acerhdf has been doing an on-off fan control using hysteresis by
post-manipulating the outcome of thermal subsystem trip point handling.
This patch enables acerhdf to use the bang-bang governor, which is
intended for on-off controlled fans.
CC: Zhang Rui
Cc: Andreas Mohr
Cc: Borislav Petkov
The bang-bang thermal governor uses a hysteresis to switch abruptly on
or off a cooling device. It is intended to control fans, which can
not be throttled but just switched on or off.
Bang-bang cannot be set as default governor as it is intended for
special devices only. For those special
added following new models:
* Aspire 5755G
* AO521
* AO751h
* Aspire One 753
* Extensa 5420
* Aspire 5315
* Aspire 5739G
* TravelMate TM8573T
Cc: Andreas Mohr
Cc: Borislav Petkov
Signed-off-by: Peter Feuerer
---
drivers/platform/x86/acerhdf.c | 25
On Mon, Apr 28, 2014 at 10:55:36AM -0500, Felipe Balbi wrote:
> On Mon, Apr 28, 2014 at 04:49:23PM -0400, Zhuang Jin Can wrote:
> > Adds a debugfs file "snapshot" to dump dwc3 requests, trbs and events.
>
> you need to explain what are you trying to provide to our users here.
>
> What "problem"
Hi!
> > > > Configuring kernels from scratch has become an incredibly long and
> > > > tedious task. The reason is that the number of drivers and options has
> > > > exploded in the past few years. Which in itself is great - Linux is
> > > > successful, yeah! - but the side effects must be dealt
On Sat 2014-04-26 01:56:15, Sebastian Reichel wrote:
> Add common DT binding documentation for touchscreen devices and
> implement input_parse_touchscreen_of_params, which parses the common
> properties and configures the input device accordingly.
>
> The method currently does not interpret the
On Sat 2014-04-26 01:56:17, Sebastian Reichel wrote:
> Simplify the driver by using managed resources for memory allocation of
> internal struct, input device allocation and irq request.
>
> Signed-off-by: Sebastian Reichel
Reviewed-by: Pavel Machek
--
(english)
On Sat 2014-04-26 01:56:19, Sebastian Reichel wrote:
> Add devicetree binding documentation for TSC2005 touchscreen.
>
Reviewed-by: Pavel Machek
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures)
http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To
On Tue, 29 Apr 2014 11:07:16 +0200 "Michael Kerrisk (man-pages)"
wrote:
> On 04/27/2014 11:28 PM, NeilBrown wrote:
> > On Sun, 27 Apr 2014 13:11:33 +0200 "Michael Kerrisk (man-pages)"
> > wrote:
> >
> >> On Sun, Apr 27, 2014 at 12:04 PM, NeilBrown wrote:
> >>> On Sun, 27 Apr 2014 11:16:02
On Sat 2014-04-26 01:56:16, Sebastian Reichel wrote:
> Change some dev_dbg() invocations to dev_err() ones, because they
> are supposed to output error messages.
>
> Signed-off-by: Sebastian Reichel
Reviewed-by: Pavel Machek
--
(english) http://www.livejournal.com/~pavelmachek
(cesky,
On Mon, Apr 28, 2014 at 12:07:31PM +0100, Daniel Lezcano wrote:
> I'm really wondering if the cgroup couldn't be a good solution:
>
> Amit pointed the conflict about the power vs performance with some
> applications. We want to have for example a game to run fast performance
> and some other
> >>This patch moves Exynos PMU driver implementation from
> >>"arm/mach-exynos" to "drivers/mfd".
> >>This driver is mainly used for setting misc bits of register from PMU IP
> >>of Exynos SoC which will be required to configure before Suspend/Resume.
> >>Currently all these settings are done in
smatch says:
skd_acquire_msix() info: redundant null check
on entries calling kfree()
Signed-off-by: Daeseok Youn
---
drivers/block/skd_main.c |3 +--
1 files changed, 1 insertions(+), 2 deletions(-)
diff --git a/drivers/block/skd_main.c b/drivers/block/skd_main.c
index 608532d..fac4c08
On Sat 2014-04-26 01:56:18, Sebastian Reichel wrote:
> This adds DT support to the tsc2005 touchscreen
> driver.
>
> Signed-off-by: Sebastian Reichel
> @@ -100,6 +102,11 @@
>TSC2005_CFR2_AVG_7)
>
> #define MAX_12BIT0xfff
> +#define
- Adds DT configuration support for ksz9031
- Renames micrel-ksz9021.txt to micrel-ksz90x1.txt and adds ksz9031 binding
documentation
Changes since v2:
- Merged together ksz9031_load_{clk,data,ctrl}_skew_values()
- Added field length and number of fields prameter to account for registers
Adds support for ksz9031 PAD skew configuration over devicetree.
Signed-off-by: Hubert Chaumette
---
drivers/net/phy/micrel.c | 167 +--
1 file changed, 44 insertions(+), 123 deletions(-)
diff --git a/drivers/net/phy/micrel.c
Renames micrel-ksz9021.txt to micrel-ksz90x1.txt and adds documentation for
the KSZ9031 binding from patch 1. Also adds step increment information, and
note about phy fixups.
Signed-off-by: Hubert Chaumette
---
.../devicetree/bindings/net/micrel-ksz9021.txt | 49 -
On Monday 28 April 2014 03:06 PM, Kirill A. Shutemov wrote:
> Madhavan Srinivasan wrote:
>> Kirill A. Shutemov with 8c6e50b029 commit introduced
>> vm_ops->map_pages() for mapping easy accessible pages around
>> fault address in hope to reduce number of minor page faults.
>>
>> This patch creates
On Monday 28 April 2014 02:36 PM, Peter Zijlstra wrote:
> On Mon, Apr 28, 2014 at 02:31:29PM +0530, Madhavan Srinivasan wrote:
>> +unsigned int fault_around_order = CONFIG_FAULT_AROUND_ORDER;
>
> __read_mostly?
>
Agreed. Will add it.
Thanks for review.
With regards
Maddy
--
To unsubscribe from
On Tuesday 29 April 2014 07:48 AM, Rusty Russell wrote:
> Madhavan Srinivasan writes:
>> diff --git a/arch/powerpc/platforms/pseries/setup.c
>> b/arch/powerpc/platforms/pseries/setup.c
>> index 2db8cc6..c87e6b6 100644
>> --- a/arch/powerpc/platforms/pseries/setup.c
>> +++
On Sat 2014-04-26 02:11:51, Rafael J. Wysocki wrote:
> Hi Linus,
>
> Please pull from
>
> git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \
> pm+acpi-3.15-rc3
>
> to receive ACPI, power management and PNP fixes for v3.15-rc3
> with top-most commit
Currently, put_compound_page should carefully handle tricky case
to avoid racing with compound page releasing or spliting, which
makes it growing quite lenthy(about 200+ lines) and need deep
tab indention, which makes it quite hard to follow and maintain.
Now based on two helpers introduced in
Currently, put_compound_page should carefully handle tricky case
to avoid racing with compound page releasing or spliting, which
makes it growing quite lenthy(about 200+ lines) and need deep
tab indention, which makes it quite hard to follow and maintain.
This patch(and the next patch) tries to
On Sun, Apr 27, 2014 at 08:44:12PM +0100, Larry Bassel wrote:
> diff --git a/arch/arm64/kernel/entry.S b/arch/arm64/kernel/entry.S
> index 39ac630..eda7755 100644
> --- a/arch/arm64/kernel/entry.S
> +++ b/arch/arm64/kernel/entry.S
[...]
> @@ -421,28 +421,30 @@ el0_da:
> /*
>* Data
Currently, in put_compound_page(), we have such code
--- snipt
if (likely(!PageTail(page))) { <-- (1)
if (put_page_testzero(page)) {
/*
¦* By the time all refcounts have been released
¦* split_huge_page cannot
On Sun, Apr 27, 2014 at 08:44:14PM +0100, Larry Bassel wrote:
> Make calls to ct_user_enter when the kernel is exited
> and ct_user_exit when the kernel is entered (in el0_da,
> el0_ia, el0_svc, el0_irq).
>
> These macros expand to function calls which will only work
> properly if el0_sync and
It is currently not possible for various wait_on_bit functions to
implement a timeout.
While the "action" function that is called to do the waiting could
certainly use schedule_timeout(), there is no way to carry forward the
remaining timeout after a false wake-up.
As false-wakeups a clearly
Use dev_err() insted of printk() in order to provice userspace with
more useful information and use the common kernel coding style.
Signed-off-by: Martin Kepplinger
---
drivers/staging/dgnc/dgnc_sysfs.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On Sat, 26 Apr, at 03:28:21PM, Dave Young wrote:
>
> There's other kernel messages without appending ,keep.
>
> Also console=ttyS0 does not work with earlyprintk=efi,keep, removing
> ,keep it works well.
Try console=efi
> > > Actually efi earlyprintk is using __init functions such as
[hijacking the thread since it has the right Cc list already, sorry]
I stumbled over this doing randconfig builds on linux-next
8<--
>From c11f54f1e5ea0557e076867ca31c90bcb20e3e0c Mon Sep 17 00:00:00 2001
From: Arnd Bergmann
Date: Tue, 29 Apr 2014 11:41:40 +0200
Subject: [PATCH] mmc:
On Mon, Apr 28, 2014 at 03:38:38PM -0400, Vince Weaver wrote:
>
> OK, this is my current theory as to what's going on. I'd appreciate any
> comments.
>
>
> We have an event, let's call it #16.
>
> Event #16 is a SW event created and running in the parent on CPU0.
A regular software one,
On Sun, Apr 27, 2014 at 01:06:35PM -0400, Oleg Drokin wrote:
> diff --git a/drivers/staging/lustre/lustre/ptlrpc/ptlrpc_module.c
> b/drivers/staging/lustre/lustre/ptlrpc/ptlrpc_module.c
> index 0efd358..251ae75 100644
> --- a/drivers/staging/lustre/lustre/ptlrpc/ptlrpc_module.c
> +++
"dev" and "net" are NULL when alloc_netdev() is failed.
So just unlock and return an error.
Signed-off-by: Daeseok Youn
---
drivers/firewire/net.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/firewire/net.c b/drivers/firewire/net.c
index 4af0a7b..c398645
On Mon, Apr 28, 2014 at 9:37 PM, Will Deacon wrote:
> On Mon, Apr 28, 2014 at 04:52:42PM +0100, Antonios Motakis wrote:
>> The ARM SMMU can take an IOMMU_EXEC protection flag in addition to
>> IOMMU_READ and IOMMU_WRITE. Expose this as an IOMMU capability.
>
> The other way of handling this would
On 04/29/2014 11:24 AM, NeilBrown wrote:
> On Tue, 29 Apr 2014 11:07:16 +0200 "Michael Kerrisk (man-pages)"
> wrote:
>
>> On 04/27/2014 11:28 PM, NeilBrown wrote:
>>> On Sun, 27 Apr 2014 13:11:33 +0200 "Michael Kerrisk (man-pages)"
>>> wrote:
>>>
On Sun, Apr 27, 2014 at 12:04 PM, NeilBrown
Use dev_err() insted of printk() and remove "dgnc:" from the message.
This should provide userspace with more useful information and use
the common kernel coding style.
Signed-off-by: Martin Kepplinger
---
This makes probably more sense than the previous one.
drivers/staging/dgnc/dgnc_sysfs.c
On Tue, Apr 29, 2014 at 12:11:47AM +0100, Rafael J. Wysocki wrote:
> On Monday, April 28, 2014 01:07:31 PM Daniel Lezcano wrote:
[...]
> > I'm really wondering if the cgroup couldn't be a good solution:
> >
> > Amit pointed the conflict about the power vs performance with some
> >
On 04/29/2014 03:55 AM, Linus Torvalds wrote:
> On Mon, Apr 28, 2014 at 3:14 PM, Davidlohr Bueso wrote:
>>
>> I think that returning some stale/bogus vma is causing those segfaults
>> in udev. It shouldn't occur in a normal scenario. What puzzles me is
>> that it's not always reproducible. This
On 04/29/14 at 10:45am, Matt Fleming wrote:
> On Sat, 26 Apr, at 03:28:21PM, Dave Young wrote:
> >
> > There's other kernel messages without appending ,keep.
> >
> > Also console=ttyS0 does not work with earlyprintk=efi,keep, removing
> > ,keep it works well.
>
> Try console=efi
With
On 04/29/2014 05:41 AM, Davidlohr Bueso wrote:
> On Mon, 2014-04-28 at 16:57 -0700, Linus Torvalds wrote:
>> On Mon, Apr 28, 2014 at 4:11 PM, Andrew Morton
>> wrote:
>>>
>>> unuse_mm() leaves current->mm at NULL so we'd hear about it pretty
>>> quickly if a user task was running use_mm/unuse_mm.
* Oleg Nesterov [2014-04-19 19:01:47]:
> validate_insn_32bits() and validate_insn_64bits() are very similar,
> turn them into the single uprobe_init_insn() which has the additional
> "bool x86_64" argument which can be passed to insn_init() and used to
> choose between
* Oleg Nesterov [2014-04-19 19:01:51]:
> 1. Extract the ->ia32_compat check from 64bit validate_insn_bits()
>into the new helper, is_64bit_mm(), it will have more users.
>
>TODO: this checks is actually wrong if mm owner is X32 task,
>we need another fix which changes
801 - 900 of 1468 matches
Mail list logo