On Sat, Mar 08, 2014 at 09:18:57PM -0700, Shuah Khan wrote:
> On 03/08/2014 01:50 PM, Satoru Takeuchi wrote:
> > At Sat, 08 Mar 2014 09:10:00 -0800,
> > Guenter Roeck wrote:
> >>
> >> On 03/08/2014 08:18 AM, Greg Kroah-Hartman wrote:
> >>> On Sat, Mar 08, 2014 at 06:35:52AM -0800, Guenter Roeck wro
On Wed, Mar 12, 2014 at 04:59:47AM +0400, Max Filippov wrote:
> And tlv320aic23 has the following regmap:
> const struct regmap_config tlv320aic23_regmap = {
> .reg_bits = 7,
> .val_bits = 9,
> and its SPI interface accordingly does the following in .probe:
> spi->bits_p
On Tuesday, March 11, 2014 3:19 PM, Fred Akers wrote:
> This patch fixes a few function names that are very long and are
> not in the correct naming style
>
> Signed-off-by: Fred Akers
> ---
> .../comedi/drivers/addi-data/hwdrv_apci035.c | 58 +--
> .../comedi/drivers/addi-data/hwd
On 05/03/14 16:24, Lasse Collin wrote:
On 2014-03-05 Phillip Lougher wrote:
(BTW Kyle you should have CC'd me on the patch as a courtesy).
I could have done that too but somehow I didn't, sorry.
np
But speaking as the Squashfs author, the lack of BCJ support for
an architecture creates a
This patch fixes a compilation problem (unused variable) with the
new SNB/IVB/HSW uncore IMC code.
In V2, we simplify the fix as suggested by Peter Zjilstra.
Reported-by: Stephen Rothwell
Signed-off-by: Stephane Eranian
--
diff --git a/arch/x86/kernel/cpu/perf_event_intel_uncore.c
b/arch/x86
On Tue, Mar 11, 2014 at 10:45:17PM +, Lee Jones wrote:
> > > > Add a driver for the BCM590xx PMU multi-function devices. The driver
> > > > initially supports regmap initialization and instantiation of the
> > > > voltage regulator device function of the PMU.
> > > >
> > > > Signed-off-by: Mat
Add a DT binding for the BCM590xx PMUs. The binding inherits from
the generic regulator bindings.
Signed-off-by: Matt Porter
Reviewed-by: Tim Kryger
Reviewed-by: Markus Mayer
---
Documentation/devicetree/bindings/mfd/bcm590xx.txt | 41 ++
1 file changed, 41 insertions(+)
c
Add a driver for the BCM590xx PMU multi-function devices. The driver
initially supports regmap initialization and instantiation of the
voltage regulator device function of the PMU.
Signed-off-by: Matt Porter
Reviewed-by: Tim Kryger
Reviewed-by: Markus Mayer
---
drivers/mfd/Kconfig |
Add a dtsi to support the BCM590xx PMUs used by the BCM281xx family
of SoCs. Enable regulators for use with the dwc2 and sdhci on
bcm28155-ap.
Signed-off-by: Tim Kryger
Signed-off-by: Matt Porter
Reviewed-by: Markus Mayer
---
arch/arm/boot/dts/bcm28155-ap.dts | 47 +++-
arc
On Wed, 12 Mar 2014 00:52:33 + (UTC)
Mathieu Desnoyers wrote:
> - Original Message -
> > From: "Steven Rostedt"
> > To: "Mathieu Desnoyers"
> > Cc: linux-kernel@vger.kernel.org, "Ingo Molnar" ,
> > "Frederic Weisbecker" ,
> > "Andrew Morton"
> > Sent: Tuesday, March 11, 2014 7:34:
Enable BCM590xx MFD and regulator drivers to manage voltage
regulators on BCM281xx platforms.
Signed-off-by: Tim Kryger
Signed-off-by: Matt Porter
Reviewed-by: Markus Mayer
---
arch/arm/configs/bcm_defconfig | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/arm/configs/bcm_defcon
Hi,
On 03/11/2014 11:35 PM, Will Deacon wrote:
Hi Akashi,
On Fri, Feb 28, 2014 at 05:18:37AM +, AKASHI Takahiro wrote:
This patchset implements a function tracer on arm64.
There was another implementation from Cavium network, but both of us agreed
to use my patchset as future base. He is s
On Wed, Mar 12, 2014 at 01:27:01AM +, Mark Brown wrote:
> Hi Greg,
You should look at the Subject: you are generating, I think something is
missing :)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordom
Add a regulator driver for the BCM590xx PMU voltage regulators.
The driver supports LDOs and DCDCs in normal mode only. There is
no support for low-power mode or power sequencing.
Signed-off-by: Matt Porter
Reviewed-by: Tim Kryger
Reviewed-by: Markus Mayer
---
drivers/regulator/Kconfig
On Mon, 10 Mar 2014 21:04:57 -0400
Mathieu Desnoyers wrote:
> Describe the @data argument (probe private data).
>
> Fixes: 38516ab59fbc "tracing: Let tracepoints have data passed to tracepoint
> callbacks"
> CC: Steven Rostedt
> CC: Ingo Molnar
> CC: Frederic Weisbecker
> CC: Andrew Morton
From: Michal Hocko
__mem_cgroup_try_charge duplicates get_mem_cgroup_from_mm for charges
which came without a memcg. The only reason seems to be a tiny
optimization when css_tryget is not called if the charge can be
consumed from the stock. Nevertheless css_tryget is very cheap since
it has been
Hi Greg,
Today's linux-next merge of the staging tree got a conflict in
arch/arm/boot/dts/imx53-qsb.dts between various commits from the arm-soc tree
and commit 17b5001b5143e3b ("imx-drm: convert to componentised device support")
from the staging tree.
I fixed it up (see below) and can carry t
Users pass either a mm that has been established under task lock, or
use a verified current->mm, which means the task can't be exiting.
Signed-off-by: Johannes Weiner
Acked-by: Michal Hocko
---
mm/memcontrol.c | 7 ---
1 file changed, 7 deletions(-)
diff --git a/mm/memcontrol.c b/mm/memcon
Only page cache charges can happen without an mm context, so push this
special case out of the inner core and into the cache charge function.
An ancient comment explains that the mm can also be NULL in case the
task is currently being migrated, but that is not actually true with
the current case,
The BCM59056 is a multi-function power management unit used with the
BCM281xx family of SoCs. This series adds an MFD and voltage regulator
driver to support the BCM59056. The bcm28155-ap DT support is updated
to enable use of regulators on the otg and sdhci peripherals.
Changes since v3:
Hi all,
After merging the kvm tree, today's linux-next build (20140311)
failed like this:
/home/broonie/next/next/arch/x86/kvm/vmx.c: In function
'nested_vmx_setup_ctls_msrs':
/home/broonie/next/next/arch/x86/kvm/vmx.c:2292:2: error: implicit declaration
of function &#x
I decided to run my tests on linux-next, and my wakeup_rt tracer was
broken. After running a bisect, I found that the problem commit was:
linux-next commit c365c292d059
"sched: Consider pi boosting in setscheduler()"
And the reason the wake_rt tracer test was failing, was because it had
no
On Fri, 2014-03-07 at 12:58 +0800, Chenhui Zhao wrote:
> diff --git a/arch/powerpc/kernel/smp.c b/arch/powerpc/kernel/smp.c
> index ac2621a..f3f4401 100644
> --- a/arch/powerpc/kernel/smp.c
> +++ b/arch/powerpc/kernel/smp.c
> @@ -405,8 +405,12 @@ void generic_cpu_die(unsigned int cpu)
>
> f
On Fri, 2014-03-07 at 12:58 +0800, Chenhui Zhao wrote:
> From: Wang Dongsheng
>
> Add booke_cpu_state_save() and booke_cpu_state_restore() functions which can
> be
> used to save/restore CPU's registers in the case of deep sleep and
> hibernation.
>
> Supported processors: E6500, E5500, E500MC
On Mon, Mar 10, 2014 at 10:40:07AM +, Luís Henriques wrote:
> On Fri, Mar 07, 2014 at 05:07:21PM -0800, Greg Kroah-Hartman wrote:
> > 3.4-stable review patch. If anyone has any objections, please let me know.
> >
>
> As per Tony request, I've dropped this patch from the 3.5 kernel. Looks
>
On Sun, Mar 9, 2014 at 12:39 AM, Arnd Bergmann wrote:
> On Saturday 08 March 2014, Rob Herring wrote:
>> On Fri, Mar 7, 2014 at 10:02 AM, Arnd Bergmann wrote:
>
>> > a) Follow what we do for PCI devices: assume that we can do DMA_MASK(32)
>> > on any device, and have drivers call dma_set_mask(DMA
On Wed, Mar 12, 2014 at 5:08 AM, Mark Brown wrote:
> On Wed, Mar 12, 2014 at 04:59:47AM +0400, Max Filippov wrote:
>> On Wed, Mar 12, 2014 at 4:34 AM, Mark Brown wrote:
>
>> > This driver is not actually compatible with the tlv320aic23 driver since
>> > it needs 8 bit words, you need to at least
On Wed, Mar 12, 2014 at 12:40:30AM +, Mark Brown wrote:
> On Tue, Mar 11, 2014 at 07:25:45PM -0400, Matt Porter wrote:
> > On Tue, Mar 11, 2014 at 10:45:17PM +, Lee Jones wrote:
>
> > > Are there any inter-patch dependencies in the set? If so, we should
> > > know about them so we can coor
On Tue, Mar 11, 2014 at 07:11:18PM +0100, Radim Krčmář wrote:
> We always disable cr8 intercept in its handler, but only re-enable it
> if handling KVM_REQ_EVENT, so there can be a window where we do not
> intercept cr8 writes, which allows an interrupt to disrupt a higher
> priority task.
>
> Fix
Hi Greg,
Today's linux-next merge of the usb tree got a conflict in
arch/arm/mach-tegra/Kconfig between commit 06c886a95cbb533 ("phy: mvebu-sata:
prepare new Dove DT Kconfig variable") from the USB tree and commit
ff1f0018cf66 ("drivers: Enable building of Kirkwood drivers for mach-mvebu")
fro
On Tuesday, March 11, 2014 3:19 PM, Fred Akers wrote:
> This patch fixes a few function names that are very long and are
> not in the correct naming style
>
> Signed-off-by: Fred Akers
Fred,
I pulled Greg's staging tree to see if your patches apply.
Patch 1/2 is ok but patch 2/2 does not apply:
On Fri, 2014-03-07 at 12:58 +0800, Chenhui Zhao wrote:
> From: Hongbo Zhang
>
> In the last stage of deep sleep, software will trigger a Finite
> State Machine (FSM) to control the hardware precedure, such as
> board isolation, killing PLLs, removing power, and so on.
>
> When the system is wake
On Tue, Mar 11, 2014 at 01:26:16PM -0700, Kees Cook wrote:
> This makes sure that the name coming out of configfs cannot be used
> accidentally as a format string.
>
> Signed-off-by: Kees Cook
> ---
> drivers/usb/gadget/tcm_usb_gadget.c |2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
On 03/12/2014 04:07 AM, Sasha Levin wrote:
> Hi all,
>
> While fuzzing with trinity inside a KVM tools guest running latest -next
> kernel
> I've stumbled on the following spew:
>
> [ 477.301955] kernel BUG at mm/swap.c:609!
> [ 477.302564] invalid opcode: [#1] PREEMPT SMP DEBUG_PAGEALLOC
Register for the device are mapped in uio_mmap_physical().
In this case, it might not be the same as the size of VMA always.
This uses PAGE_ALIGN to memory size, fix the check of the memory size
to be mapped.
Signed-off-by: Nobuhiro Iwamatsu
---
drivers/uio/uio.c | 2 +-
1 file changed, 1 insert
On Wed, Mar 12, 2014 at 1:32 AM, Laurent Pinchart
wrote:
> On Tuesday 11 March 2014 17:23:37 Geert Uytterhoeven wrote:
>> Hi Laurent,
>>
>> On Tue, Mar 11, 2014 at 4:55 PM, Laurent Pinchart wrote:
>> > Does this require drivers/sh/pm_runtime.c to be compiled in ?
>>
>> Let's check...
>>
>> My koel
Hi Greg,
Today's linux-next merge of the staging tree got a conflict in between commit
f080a51bef2ca ("USB: complain if userspace resets an active endpoint") from the
usb tree and commit 9b6f0c4b98171f2a3 ("usbcore: rename struct dev_state to
struct usb_dev_state") from the staging tree.
I fi
Hi Greg,
Today's linux-next merge of the usb tree got a conflict in between commit
22f6a0f0e3549 ("usb: move hub init and LED blink work to power efficient
workqueue") from the usb tree and commit 77fa83cf747820 ("usb: don't use
PREPARE_DELAYED_WORK") from the workqueues tree.
I fixed it up (
mem_cgroup_charge_common() is used by both cache and anon pages, but
most of its body only applies to anon pages and the remainder is not
worth having in a separate function.
Signed-off-by: Johannes Weiner
---
mm/memcontrol.c | 40
1 file changed, 16 inse
- Original Message -
> From: "Steven Rostedt"
> To: "Mathieu Desnoyers"
> Cc: linux-kernel@vger.kernel.org, "Ingo Molnar" , "Frederic
> Weisbecker" ,
> "Andrew Morton"
> Sent: Tuesday, March 11, 2014 9:14:02 PM
> Subject: Re: [PATCH 1/2] Tracepoint API doc update: data argument
>
> On
Some callsites pass a memcg directly, some callsites pass a mm that
first has to be translated to an mm. This makes for a terrible
function interface.
Just push the mm-to-memcg translation into the respective callsites
and always pass a memcg to mem_cgroup_try_charge().
Signed-off-by: Johannes W
It used to disable preemption and run sanity checks but now it's only
taking a number out of one percpu counter and putting it into another.
Do this directly in the callsite and save the indirection.
Signed-off-by: Johannes Weiner
Acked-by: Michal Hocko
---
mm/memcontrol.c | 28
On Wed, Mar 12, 2014 at 4:34 AM, Mark Brown wrote:
> On Wed, Mar 12, 2014 at 12:20:49AM +0400, Max Filippov wrote:
>> On Tue, Mar 11, 2014 at 11:49 PM, Mark Brown wrote:
>> > On Tue, Mar 11, 2014 at 04:44:49PM +0400, Max Filippov wrote:
>
>> >> + unsigned long timeout = jiffies + msecs_to_jif
Hi Andrew,
here are some cleanups and refactoring efforts of the memcg charge
path for 3.15 from Michal and me.
mm/memcontrol.c | 319 +++---
1 file changed, 112 insertions(+), 207 deletions(-)
--
To unsubscribe from this list: send the line "unsu
Instead of returning NULL from try_get_mem_cgroup_from_mm() when the
mm owner is exiting, just return root_mem_cgroup. This makes sense
for all callsites and gets rid of some of them having to fallback
manually.
Signed-off-by: Johannes Weiner
Acked-by: Michal Hocko
---
mm/memcontrol.c | 18 +++
In some cases we want to do an ack right before the unmask of an irq.
A typical example of such a case is having an i2c device which uses a level
interrupt. Such devices usually have an interrupt status register with
write to clear status bits. This means that the interrupt handler needs to
sleep
On Tue, 2014-03-11 at 17:02 -0700, Ruchi Kandoi wrote:
> This API would be called from the platform specific code,
[]
> This is already in use on some Android devices. We are trying to make
> this a generic API which could be called by other platforms as well,
> standardizing the format in which th
Hello Mel,
On Wed, Feb 12, 2014 at 02:00:52PM +, Mel Gorman wrote:
> On Fri, Jan 10, 2014 at 01:10:39PM -0500, Johannes Weiner wrote:
> > @@ -248,12 +248,15 @@ pgoff_t page_cache_next_hole(struct address_space
> > *mapping,
> > pgoff_t page_cache_prev_hole(struct address_space *mapping,
> >
Hi Greg,
Today's linux-next merge of the staging tree got a conflict in
drivers/staging/cxt1e1/linux.c between commit 084b6e7765b95
("staging/cxt1e1/linux.c: Correct arbitrary memory write in c4_ioctl()") from
Linus' tree and commit aa562fa70931d ("staging: cxt1e1: Fix no spaces at the
start o
Hi Nicolin
> The current simple-card driver separates the daimft for cpu_dai and codec_dai.
> So we might get different values for them (0x4003 and 0x1003 for example):
>
> asoc-simple-card sound-cs42888.12: cpu : 2024000.esai / 4003 / 13200
> asoc-simple-card sound-cs42888.12: codec : cs428
Describe the @data argument (probe private data).
Fixes: 38516ab59fbc "tracing: Let tracepoints have data passed to tracepoint
callbacks"
Signed-off-by: Mathieu Desnoyers
CC: Steven Rostedt
CC: Ingo Molnar
CC: Frederic Weisbecker
CC: Andrew Morton
---
kernel/tracepoint.c |4
1 file
On Tuesday, March 11, 2014 10:03:00 AM Soren Brinkmann wrote:
> From: Joe Perches
>
> - Add missing newlines
> - Coalesce format fragments
> - Convert printks to pr_
> - Align arguments
>
> Original-patch-by: Sören Brinkmann
> Signed-off-by: Joe Perches
> Acked-by: Viresh Kumar
> ---
> I
On Fri, 2014-03-07 at 12:58 +0800, Chenhui Zhao wrote:
> In 64-bit mode, kernel just clears the irq soft-enable flag
> in struct paca_struct to disable external irqs. But, in
> the case of suspend, irqs should be disabled by hardware.
> Therefore, hook a function to ppc_md.suspend_disable_irqs
> to
lock_page_cgroup() disables preemption, remove explicit preemption
disabling for code paths holding this lock.
Signed-off-by: Johannes Weiner
Acked-by: Michal Hocko
---
mm/memcontrol.c | 15 ---
1 file changed, 4 insertions(+), 11 deletions(-)
diff --git a/mm/memcontrol.c b/mm/memc
On Wednesday, March 12, 2014 01:06:27 AM Hartley Sweeten wrote:
> On Tuesday, March 11, 2014 3:19 PM, Fred Akers wrote:
> > This patch fixes a few function names that are very long and are
> > not in the correct naming style
> >
> > Signed-off-by: Fred Akers
>
> Fred,
>
> I pulled Greg's stagin
phy_ethtool_get_wol is a helper to get current WOL settings from
a phy device. When using this helper on a PHY without .get_wol
callback, struct ethtool_wolinfo is never set-up correctly and
may contain misleading information about WOL status.
To fix this, always zero relevant fields of struct eth
On 03/11/2014 11:35 AM, Geert Uytterhoeven wrote:
On Tue, Mar 11, 2014 at 12:49 PM, Peter Hurley wrote:
On 03/11/2014 06:58 AM, Geert Uytterhoeven wrote:
On Tue, Mar 11, 2014 at 4:14 AM, Peter Hurley
wrote:
[...]
/*
* Indicate that there isn't a port here
From: Maxime Ripard
Switch the device tree to the new compatibles introduced in the timer driver
to have a common pattern accross all Allwinner SoCs.
Signed-off-by: Maxime Ripard
Signed-off-by: Daniel Lezcano
---
arch/arm/boot/dts/sun4i-a10.dtsi |2 +-
arch/arm/boot/dts/sun5i-a10s.dtsi |
> > > Add a driver for the BCM590xx PMU multi-function devices. The driver
> > > initially supports regmap initialization and instantiation of the
> > > voltage regulator device function of the PMU.
> > >
> > > Signed-off-by: Matt Porter
> > > Reviewed-by: Tim Kryger
> > > Reviewed-by: Markus Ma
From: Maxime Ripard
The Allwinner A10 compatibles were following a slightly different compatible
patterns than the rest of the SoCs for historical reasons. Add compatibles
matching the other pattern to the timer driver for consistency, and keep the
older one for backward compatibility.
Signed-of
From: Ivan Khoronzhuk
This patch provides bindings for the 64-bit timer in the KeyStone
architecture devices. The timer can be configured as a general-purpose 64-bit
timer, dual general-purpose 32-bit timers. When configured as dual 32-bit
timers, each half can operate in conjunction (chain mode)
From: Matthias Brugger
Commit 438e0bff5257 added the timer-keystone device driver but make use
of an unnecessary variable in the init function. This patch deletes this
variable.
Signed-off-by: Matthias Brugger
Signed-off-by: Daniel Lezcano
---
drivers/clocksource/timer-keystone.c |5 +
From: Linus Walleij
Move the U300 timer driver down to the clocksource driver
subsystem and keep arch/arm clean.
Cc: Daniel Lezcano
Cc: Thomas Gleixner
Signed-off-by: Linus Walleij
Signed-off-by: Daniel Lezcano
---
MAINTAINERS |1 +
arch/arm/mach-u300/Makefile
From: Magnus Damm
Now when drivers/clocksource/Kconfig has been
updated with entires for CMT, TMU and MTU2
it is safe to remove these from SH.
Signed-off-by: Magnus Damm
Acked-by: John Stultz
Signed-off-by: Wolfram Sang
Signed-off-by: Daniel Lezcano
---
arch/sh/Kconfig | 76 ++
From: Magnus Damm
Add Kconfig entries for CMT, MTU2, TMU and STI to
drivers/clocksource/Kconfig. This will allow us to
get rid of duplicated entires in architecture code
such as arch/sh and arch/arm/mach-shmobile.
Signed-off-by: Magnus Damm
Signed-off-by: Wolfram Sang
Signed-off-by: Daniel Lez
From: Ezequiel Garcia
Replace the driver-specific thread-safe shared register API
by the recently introduced atomic_io_clear_set().
Cc: Daniel Lezcano
Tested-by: Sebastian Hesselbarth
Tested-by: Willy Tarreau
Acked-by: Jason Cooper
Signed-off-by: Ezequiel Garcia
Signed-off-by: Daniel Lezcan
From: Ezequiel Garcia
Replace the driver-specific thread-safe shared register API
by the recently introduced atomic_io_clear_set().
Signed-off-by: Ezequiel Garcia
Signed-off-by: Daniel Lezcano
---
drivers/clocksource/time-armada-370-xp.c | 12
1 file changed, 4 insertions(+), 8
From: Soren Brinkmann
The timer core takes care of serialization and IRQs. Hence the driver is
no longer required to disable interrupts when calling
clockevents_update_freq().
Signed-off-by: Soren Brinkmann
Signed-off-by: Daniel Lezcano
Acked-by: Michal Simek
---
drivers/clocksource/cadence_
From: Magnus Damm
Now when drivers/clocksource/Kconfig has been
updated with entires for CMT, TMU, MTU2, and STI
it is safe to remove these from mach-shmobile.
Also select timers per SoC via SYS_SUPPORTS_xxx.
Signed-off-by: Magnus Damm
Acked-by: John Stultz
Signed-off-by: Wolfram Sang
Signed
From: Soren Brinkmann
The generic cpufreq-cpu0 driver can scale the CPU frequency on Zynq
SOCs. Add the required platform device to the BSP and appropriate
OPPs to the dts.
Cc: Rob Herring
Cc: Pawel Moll
Cc: Mark Rutland
Cc: Ian Campbell
Cc: Kumar Gala
Cc: Russell King
Cc: devicet...@vger.
From: Soren Brinkmann
The timer frequency of the arm_global_timer depends on the CPU
frequency. With cpufreq altering that frequency the arm_global_timer
does not maintain a stable time base. Therefore don't enable that timer
in case cpufreq is enabled.
Cc: Russell King
Signed-off-by: Soren Bri
From: Dan Carpenter
My guess is we aren't going to have a 2 digit cpuid here any time soon
but the static checkers don't know that and complain that the snprintf()
could overflow.
Signed-off-by: Dan Carpenter
Signed-off-by: Daniel Lezcano
---
drivers/clocksource/exynos_mct.c |2 +-
1 file
From: Soren Brinkmann
The currently used method adjusting the clocksource to a changing input
frequency does not work on kernels from 3.11 on.
The new approach is to keep the timer frequency as constant as possible.
I.e.
- due to the TTC's prescaler limitations, allow frequency changes
only i
From: Ivan Khoronzhuk
Add broadcast clock-event device for the Keystone arch.
The timer can be configured as a general-purpose 64-bit timer,
dual general-purpose 32-bit timers. When configured as dual 32-bit
timers, each half can operate in conjunction (chain mode) or
independently (unchained mo
From: Stephen Boyd
Set the CLOCK_EVT_FEAT_DYNIRQ flag on the memory mapped
clockevent so that we save power by waking up the CPU with the
next event when this timer is used in broadcast mode.
Signed-off-by: Stephen Boyd
Signed-off-by: Daniel Lezcano
---
drivers/clocksource/arm_arch_timer.c |
> On Tue, 11 Mar 2014 14:49:25 +0200
> Tomas Winkler wrote:
>
> > From: Alexander Usyskin
> >
> > Consistently display error on possible copy_from/to_user failures
> > and replace dev_dbg with dev_err
>
> NAK
>
> This allows users to flood the logs by deliberately causing lots of these
> fai
Hi Thomas, Ingo,
here it the pull request for 3.15:
* Ezequiel Garcia used the atomic access for shared register for orion
and armada-370-xp. It allows to use the watchdog which shares the register
* Ivan Khoronzhuk added the keystone driver
* Linus Walleij moved the u300 d
On Tue, Mar 11, 2014 at 3:13 PM, Sören Brinkmann
wrote:
> On Tue, 2014-03-11 at 02:31PM -0700, Olof Johansson wrote:
>> Hi Michal,
>>
>> Sorry for the late review, I didn't notice the driver when it was
>> posted and I only saw it now with the pull request. Comments below.
>>
>>
>> On Mon, Jan 6,
>
> >> If an administrator wants to use MEI, they can search the logs for
> >> 'mei'. Otherwise they don't need a glaring reminder that their
> >> hardware doesn't actually support MEI.
> >>
> >> Signed-off-by: Andy Lutomirski
> >> ---
> >> drivers/misc/mei/pci-me.c | 2 +-
> >> 1 file change
(Sorry for the formatting, iPhone email)
The mailing list is alive (judging for all the spam bounces I get) but valid
traffic has been pretty much nothing for a long time.
Patches have trickled through for the last years with me maybe once having to
ack.
So I'm ok with either.
> On Mar 11,
Hayes Wang :
> The tx descriptor version of RTL8111B belong to RTL_TD_0.
>
> Signed-off-by: Hayes Wang
Acked-by: Francois Romieu
All 8168b chipsets should had shared the same Tx descriptor layout.
2b7b431858c284b62c18baaf2cea571be2797d5a ("r8169: TSO fixes.") got it
right but it was broken a
On Sat, Mar 8, 2014 at 11:14 AM, Paul Bolle wrote:
> On Sat, 2014-03-08 at 10:58 -0800, Andy Lutomirski wrote:
>> Some of them are errors; some are not. Annotate them accordingly.
>>
>> Signed-off-by: Andy Lutomirski
>> ---
>> lib/raid6/algos.c | 13 +++--
>> 1 file changed, 7 insertion
The existing SBS code explicitly sets the selected battery in the SBS
manager regardless of whether the battery in question is already selected.
This causes bus timeouts on Apple hardware. Check for this case and avoid
it.
Signed-off-by: Matthew Garrett
---
drivers/acpi/sbs.c | 18 +-
On 03/11/2014 05:45 PM, Davidlohr Bueso wrote:
On Tue, 2014-03-11 at 17:02 -0400, Sasha Levin wrote:
>On 03/11/2014 04:47 PM, Davidlohr Bueso wrote:
> >>Bingo! With the above patch:
> >> >
> >> >[ 243.565794] kernel BUG at mm/vmacache.c:76!
> >> >[ 243.566720] invalid opcode: [#1] PREEM
The Apple PCI _OSC method has the following code:
if (LEqual (0x01, OSDW ()))
if (LAnd (LEqual (Arg0, GUID), NEXP)
(do stuff)
else
(fail)
NEXP is a value in high memory and is presumably under the control of the
firmware. No methods set it. The methods that are called in the "do stuff
Apple hardware queries _OSI("Darwin") in order to determine whether the
system is running OS X, and changes firmware behaviour based on the answer.
The most obvious difference in behaviour is that Thunderbolt hardware is
forcibly powered down unless the system is running OS X. The obvious solution
Various Apple hardware features are disabled unless the OS claims to be
"Darwin" when queried by the firmware, most notably Thunderbolt hotplug
support. This patchset provides support for Darwin at the ACPI layer and
includes a couple of additional fixes to handle issues uncovered by the
change in
On Tue, Mar 11, 2014 at 04:08:37PM +, Lee Jones wrote:
> > Add a driver for the BCM590xx PMU multi-function devices. The driver
> > initially supports regmap initialization and instantiation of the
> > voltage regulator device function of the PMU.
> >
> > Signed-off-by: Matt Porter
> > Review
On Tue, Mar 11, 2014 at 3:03 AM, Winkler, Tomas wrote:
>
>
>> -Original Message-
>> From: Andy Lutomirski [mailto:l...@amacapital.net]
>> Sent: Saturday, March 08, 2014 20:58
>> To: linux-kernel@vger.kernel.org
>> Cc: triv...@kernel.org; Andy Lutomirski; Winkler, Tomas
>> Subject: [PATCH 1
The meat of this patch series is in patch 1. Patch 2 is split out for
improved bisectability.
Changes from v1: Split into two patches and fixed a comment.
Andy Lutomirski (2):
x86: Dynamically relocate the compat vdso
x86_32: Remove user bit from identity map PDE
Documentation/kernel-param
The only reason that the user bit was set was to support userspace
access to the compat vDSO in the fixmap. The compat vDSO now lives
in an ordinary vma, so the user bit can be removed.
Signed-off-by: Andy Lutomirski
---
arch/x86/include/asm/pgtable_types.h | 7 +--
1 file changed, 1 insert
This removes the compat vdso from the fixmap and instead relocates
it each time it's mapped. It also documents the reason for the
compat vDSO.
Before this patch, using the compat vDSO partially defeated ASLR.
With this patch, ASLR is left alone, but starting a 32-bit process
with the compat vDSO
On Tue, 2014-03-11 at 02:31PM -0700, Olof Johansson wrote:
> Hi Michal,
>
> Sorry for the late review, I didn't notice the driver when it was
> posted and I only saw it now with the pull request. Comments below.
>
>
> On Mon, Jan 6, 2014 at 7:36 AM, Michal Simek wrote:
> > The driver provide me
On Tue, 11 Mar 2014 02:03:52 +0530 "Srivatsa S. Bhat"
wrote:
> Hi,
>
> Many subsystems and drivers have the need to register CPU hotplug callbacks
> from their init routines and also perform initialization for the CPUs that are
> already online. But unfortunately there is no race-free way to ac
On Tue, Mar 11, 2014 at 01:47:24PM -0700, Davidlohr Bueso wrote:
> On Tue, 2014-03-11 at 16:45 -0400, Sasha Levin wrote:
> > On 03/11/2014 04:30 PM, Andrew Morton wrote:
> > > All I can think is that find_vma() went and returned a vma from a
> > > different mm, which would be odd. How about I
On Tue, Mar 11, 2014 at 3:44 PM, Yinghai Lu wrote:
> On Tue, Mar 11, 2014 at 10:42 AM, Bjorn Helgaas wrote:
>> We don't set the type (I/O, memory, etc.) of resources added by
>> __request_region(), which leads to confusing messages like this:
>>
>> address space collision: [io 0x1000-0x107f]
On Tue, Mar 11, 2014 at 3:39 PM, Yinghai Lu wrote:
> On Tue, Mar 11, 2014 at 10:42 AM, Bjorn Helgaas wrote:
>> Paul reported that after f75b99d5a77d ("PCI: Enforce bus address limits in
>> resource allocation") on a 32-bit kernel (CONFIG_PHYS_ADDR_T_64BIT not
>> set), intel-gtt complained "can't
On Tue, Mar 11, 2014 at 1:07 PM, Davidlohr Bueso wrote:
> On Tue, 2014-03-11 at 15:39 -0400, Sasha Levin wrote:
>> I've ended up deleting the log file by mistake, but this bug does seem to be
>> important
>> so I'd rather not wait before the same issue is triggered again.
>>
>> The call chain is
g_device[2-6]/cur_state be set to 1, the others left and/or
rewritten with 0. And the fan speed algorithm then accumulates
only one 1 without seeing the [_LEVEL_] number of
cooling_device[2-6]... or re-requesting the related trigger
temperature.
I hope this leads you developers nearer to a
On the vast majority of modern systems, no processes will use the
userspsace I/O syscalls, iopl and ioperm. Add a new config option,
CONFIG_X86_IOPORT, to support configuring them out of the kernel
entirely. Most current systems do not run programs using these
syscalls, so X86_IOPORT does not dep
101 - 200 of 823 matches
Mail list logo
