On Sun, Sep 15, 2013 at 05:49:13PM +0400, Vladimir Davydov wrote:
> In busiest->group_imb case we can come to calculate_imbalance() with
> local->avg_load >= busiest->avg_load >= sds->avg_load. This can result
> in imbalance overflow, because it is calculated as follows
>
> env->imbalance = min(
On 09/10/2013 11:57 AM, Vineet Gupta wrote:
> On 09/05/2013 11:55 PM, David Miller wrote:
>> From: Vineet Gupta
>> Date: Wed, 4 Sep 2013 17:17:15 +0530
>>
>>> copying large files to a NFS mounted host was taking absurdly large
>>> time.
>>>
>>> Turns out that TX BD reclaim had a sublte bug.
>>>
On Sun, Sep 15, 2013 at 09:30:14PM +0400, Vladimir Davydov wrote:
> Firstly, reset env.dst_cpu/dst_rq to this_cpu/this_rq, because it could
> have changed in 'some pinned' case. Otherwise, should_we_balance() can
> stop balancing beforehand.
>
> Secondly, reset env.flags, because it can have
Pass '0' in place of hardcoded "irq_base" value as "first_irq" parameter to
"irq_domain_add_simple" in order to use linear irq domain.
Signed-off-by: Chander Kashyap
---
drivers/irqchip/exynos-combiner.c | 15 +++
1 file changed, 3 insertions(+), 12 deletions(-)
diff --git
Hi Linus,
On Fri, Sep 13, 2013 at 10:29 PM, Linus Torvalds
wrote:
> On Thu, Sep 12, 2013 at 10:12 PM, Steven Miao wrote:
>> arch/blackfin/mach-bf609/Kconfig | 1655
>>
>
> WTF? This is getting crazy. The blackfin board Kconfig files are being
> used as a
On Sat, Sep 14, 2013 at 05:42:07PM +0800, Lennox Wu wrote:
> Hi Linus,
> Please pull these updates for S+core architecture. These updates include
> updating information of maintainers, fix some trivial errors, and add
> a necessary function for supporting ipv6.
>
> The following changes since
The driver core clears the driver data to NULL after device_release
or on probe failure. Thus, it is not needed to manually clear the
device driver data to NULL.
Signed-off-by: Jingoo Han
---
drivers/block/sx8.c |1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/block/sx8.c
From: Michael Opdenacker
Date: Fri, 13 Sep 2013 06:27:47 +0200
> This patch proposes to remove the IRQF_DISABLED flag from
> code in drivers/net/ethernet/smsc/
>
> It's a NOOP since 2.6.35 and it will be removed one day.
>
> Signed-off-by: Michael Opdenacker
Applied.
--
To unsubscribe from
From: Michael Opdenacker
Date: Fri, 13 Sep 2013 06:33:18 +0200
> This patch proposes to remove the IRQF_DISABLED flag from
> drivers/net/ethernet/toshiba/ps3_gelic_net.c
>
> It's a NOOP since 2.6.35 and I will remove it one day ;)
>
> Signed-off-by: Michael Opdenacker
Applied.
--
To
From: Michael Opdenacker
Date: Fri, 13 Sep 2013 06:16:53 +0200
> This patch proposes to remove the IRQF_DISABLED flag from
> code in drivers/net/ethernet/natsemi/
>
> It's a NOOP since 2.6.35 and it will be removed one day.
>
> Signed-off-by: Michael Opdenacker
Applied.
--
To unsubscribe
From: Michael Opdenacker
Date: Fri, 13 Sep 2013 05:59:42 +0200
> This patch proposes to remove the IRQF_DISABLED flag from
> drivers/net/ethernet/lantiq_etop.c
>
> It's a NOOP since 2.6.35 and it will be removed one day.
>
> Signed-off-by: Michael Opdenacker
Applied.
--
To unsubscribe from
Use module_pci_driver() macro which makes the code smaller and
simpler.
Signed-off-by: Jingoo Han
---
drivers/block/sx8.c | 15 +--
1 file changed, 1 insertion(+), 14 deletions(-)
diff --git a/drivers/block/sx8.c b/drivers/block/sx8.c
index 3fb6ab4..7b2ac95 100644
---
From: Michael Opdenacker
Date: Fri, 13 Sep 2013 06:10:10 +0200
> This patch proposes to remove the IRQF_DISABLED flag from
> drivers/net/ethernet/micrel/ks8851_mll.c
>
> It's a NOOP since 2.6.35 and it will be removed one day.
>
> Signed-off-by: Michael Opdenacker
Applied.
--
To unsubscribe
From: Michael Opdenacker
Date: Fri, 13 Sep 2013 05:51:24 +0200
> This patch proposes to remove the IRQF_DISABLED flag from
> drivers/net/ethernet/hp/hp100.c
>
> It's a NOOP since 2.6.35 and it will be removed one day.
>
> Signed-off-by: Michael Opdenacker
Applied.
--
To unsubscribe from this
From: Michael Opdenacker
Date: Fri, 13 Sep 2013 06:21:24 +0200
> This patch proposes to remove the IRQF_DISABLED flag from
> drivers/net/ethernet/pasemi/pasemi_mac.c
>
> It's a NOOP since 2.6.35 and it will be removed one day.
>
> Signed-off-by: Michael Opdenacker
Applied.
--
To unsubscribe
From: Michael Opdenacker
Date: Fri, 13 Sep 2013 06:04:23 +0200
> Signed-off-by: Michael Opdenacker
Applied.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at
From: Michael Opdenacker
Date: Fri, 13 Sep 2013 05:44:38 +0200
> This patch proposes to remove the IRQF_DISABLED flag from
> drivers/net/ethernet/freescale/fec_main.c
>
> It's a NOOP since 2.6.35 and it will be removed one day.
>
> Signed-off-by: Michael Opdenacker
Applied.
--
To unsubscribe
From: Antonio Alecrim Jr
Date: Sat, 14 Sep 2013 14:20:40 -0300
> Signed-off-by: Antonio Alecrim Jr
Applied.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at
i have a business proposal for you, write me back for more info.
-Sent from my ipad.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the
Add a new driver to support synthetic keyboard. On the next generation
Hyper-V guest firmware, many legacy devices will not be emulated and this
driver will be required.
I would like to thank Vojtech Pavlik for helping me with the
details of the AT keyboard driver.
Signed-off-by: K. Y.
Hi Chao,
On 09/16/2013 11:26 AM, Chao Yu wrote:
> Hi Gu
>
>> -Original Message-
>> From: Gu Zheng [mailto:guz.f...@cn.fujitsu.com]
>> Sent: Monday, September 16, 2013 10:09 AM
>> To: Chao Yu
>> Cc: Kim Jaegeuk; linux-f2fs-de...@lists.sourceforge.net;
>> linux-fsde...@vger.kernel.org;
On 15 September 2013 10:35, Rafael J. Wysocki wrote:
> Well, I guess you can assume that everyone has a chance to review the series
> by now and send it as one patch in the next iteration.
Yeah, that's what I thought..
> A patch that adds 192 lines of code isn't shockingly large by any measure.
On 09/12/2013 11:00 PM, Stephen Warren wrote:
> On 09/12/2013 05:24 AM, Wei Ni wrote:
>> Add OF document for LM90 in Documentation/devicetree/.
>
>> diff --git a/Documentation/devicetree/bindings/hwmon/lm90.txt
>> b/Documentation/devicetree/bindings/hwmon/lm90.txt
>
>> +Optional properties:
>>
On 09/12/2013 07:51 PM, Mark Brown wrote:
> * PGP Signed by an unknown key
>
> On Thu, Sep 12, 2013 at 07:24:19PM +0800, Wei Ni wrote:
>
>> +#include
>
> You don't need this any more, otherwise
Oh, yes, I will remove it.
>
> Reviewed-by: Mark Brown
>
> * Unknown Key
> * 0x7EA229BD
>
--
On 9/1/13 4:48 AM, Jiri Olsa wrote:
Backporting options support for traceevent lib.
ditto -- where's the code from and last commit id.
It's now possible to use following interface
to load options for 'struct pevent' object:
void traceevent_add_options(const char *name, struct plugin_option
On 9/1/13 4:48 AM, Jiri Olsa wrote:
Backporting plugin support for traceevent lib.
It would be worthwhile to not where the code is ported from --
repository and as of commit id.
David
It's now possible to use following interface
to load plugins for 'struct pevent' object:
struct
Hi Gu
> -Original Message-
> From: Gu Zheng [mailto:guz.f...@cn.fujitsu.com]
> Sent: Monday, September 16, 2013 10:09 AM
> To: Chao Yu
> Cc: Kim Jaegeuk; linux-f2fs-de...@lists.sourceforge.net;
> linux-fsde...@vger.kernel.org; linux-kernel@vger.kernel.org; 谭姝
> Subject: Re:
Hi Linus,
On Fri, Sep 13, 2013 at 10:29 PM, Linus Torvalds
wrote:
> On Thu, Sep 12, 2013 at 10:12 PM, Steven Miao wrote:
>> arch/blackfin/mach-bf609/Kconfig | 1655
>>
>
> WTF? This is getting crazy. The blackfin board Kconfig files are being
> used as a
Hi all,
Please do not add any code for v3.13 to your linux-next included branches
until after v3.12-rc1 is released.
Changes since 20130913:
The h8300-remove tree gained a conflict against Linus' tree.
The aio-direct tree gained a conflict against Linus' tree.
On Thursday 12 September 2013 07:12 PM, Roger Quadros wrote:
Hi,
On 09/02/2013 06:43 PM, Kishon Vijay Abraham I wrote:
renamed struct omap_control_usb to struct omap_control_phy since it can
be used to control PHY of USB, SATA and PCIE. Also moved the driver and
include files under *phy* and
This fixes a race in shmat() between finding the msq and
actually attaching the segment, as another thread can delete shmid
underneath us if we are preempted before acquiring the kern_ipc_perm.lock.
Reported-by: Manfred Spraul
Signed-off-by: Davidlohr Bueso
---
ipc/shm.c | 8
1 file
This patchset deals with the selinux and rmid races Manfred found on
the ipc scaling work that has been going on. It specifically addresses
shared mem and msg queues. While semaphores still need updated, I want
to make sure these are correct first. Also, Manfred had already sent out
a patchset
Currently, we check shm security only under RCU. Since selinux
can free the security structure, through selinux_sem_free_security(),
we can run into a use-after-free condition. This bug affects both
shmctl and shmat syscalls.
The fix is obvious, make sure we hold the kern_ipc_perm.lock while
Currently, we check msg security only under RCU. Since selinux
can free the security structure, through selinux_sem_free_security(),
we can run into a use-after-free condition. This bug only affects
msgctl syscalls, as msgsnd and msgrcv have already been updated.
The fix is obvious, make sure we
This fixes a race in both msgrcv() and msgsnd() between finding the msg and
actually dealing with the queue, as another thread can delete shmid
underneath us if we are preempted before acquiring the kern_ipc_perm.lock.
Manfred illustrates this nicely:
Assume a preemptible kernel that is
On Thursday 12 September 2013 06:53 PM, Roger Quadros wrote:
On 09/02/2013 06:43 PM, Kishon Vijay Abraham I wrote:
Since now we have a separate folder for phy, move the PHY dt binding
documentation of OMAP to that folder.
Signed-off-by: Kishon Vijay Abraham I
---
On Thursday 12 September 2013 04:49 PM, Roger Quadros wrote:
Hi Kishon,
On 09/02/2013 06:43 PM, Kishon Vijay Abraham I wrote:
Adapted omap-usb3 PHY driver to Generic PHY Framework and moved phy-omap-usb3
driver in drivers/usb/phy to drivers/phy and also renamed the file to
phy-omap-pipe3 since
[resent to the right list this time around]
Hi folks !
So I don't have the bandwidth to follow closely what's going on, but I
just today noticed the crackpot that went into 3.11 as part of commit:
9d8eab7af79cb4ce2de5de39f82c455b1f796963
drivers: of: add initialization code for dma reserved
> Anyone else have an opinion?
tl;dr: seq_printf() whould return void.
Well, certainly *if* seq_printf returns a value, it should be consistent
with printf, i.e. length or -errno.
If it's going to be anything else, then it should be incompatible with
an integer, so attempted uses cause
On Thursday 12 September 2013 06:49 PM, Roger Quadros wrote:
On 09/02/2013 06:43 PM, Kishon Vijay Abraham I wrote:
Adapted dwc3 core to use the Generic PHY Framework. So for init, exit,
power_on and power_off the following APIs are used phy_init(), phy_exit(),
phy_power_on() and
> > +- fsl,pwm-counter-clk: The FTM PWM counter clock source, should be
> > +one of the
> > + entries in clock-names.
>
> So the IP block has 3 input clocks, and also a mux to select which one to
> use? That sounds slightly unusual, but possible.
>
> If there is really only 1 clock input to the
Hi folks !
So I don't have the bandwidth to follow closely what's going on, but I
just today noticed the crackpot that went into 3.11 as part of commit:
9d8eab7af79cb4ce2de5de39f82c455b1f796963
drivers: of: add initialization code for dma reserved memory
Fist of all, do NOT add (or change) a
Hey Andi.
I ran the updated checkpatch tests against the -next tree
and get this patch below:
There are slightly suspicious conversions of
from:
static const char *foo __initdata = { "bar", "baz" };
to:
static const char *foo __initconst = { "bar", "baz" };
Maybe these should
People get this regularly wrong and it breaks the LTO builds,
as it causes a section attribute conflict.
Add --fix capability too.
Original-patch-by: Andi Kleen
Signed-off-by: Joe Perches
---
V2: Move it closer to the other attribute check
and add the --fix options too.
--
ADMIN WARNING!!!
Your Web-mail Quota Has Exceeded The Set Quota/Limit Which Is 20GB.
You Are Currently Running On 23GB Due To Hidden Files And Folder On
Your Mailbox.
Please Click the Link Below To Validate Your Mailbox And Increase Your
Quota.
On 09/14/2013 12:43 PM, Wang YanQing wrote:
> On Sat, Sep 14, 2013 at 12:41:36PM +0800, Wang YanQing wrote:
>> On Thu, Sep 12, 2013 at 12:07:05AM +0800, Jiang Liu wrote:
>>> From: Jiang Liu
>>>
>>> Commit f44310b98ddb7 "smp: Fix SMP function call empty cpu mask race"
>>> introduced field
Hi Chao,
On 09/13/2013 09:27 PM, Chao Yu wrote:
> This patch add macro MAX_BIO_BLOCKS to limit value of npages in
> f2fs_bio_alloc,
> it can avoid allocating failure in bio_alloc caused by npages is larger than
> UIO_MAXIOV.
As I know bio_alloc is based of *fs_bio_set* pool, without the
From: Namhyung Kim
Some files need additional compiler flags to be built successfully.
Cleanup Makefile by using optional per-file CFLAGS which look like
CFLAGS_dir_filename.o
Signed-off-by: Namhyung Kim
---
tools/perf/Makefile| 128 ++---
Fix some typos in three documentations.
Signed-off-by: Xishi Qiu
---
Documentation/IRQ-domain.txt|2 +-
Documentation/email-clients.txt |2 +-
Documentation/io-mapping.txt|2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/Documentation/IRQ-domain.txt
On 2013/9/15 0:49, Randy Dunlap wrote:
> On 09/13/13 20:49, Xishi Qiu wrote:
>
>> diff --git a/Documentation/kprobes.txt b/Documentation/kprobes.txt
>> index 0cfb00f..ca278d5 100644
>> --- a/Documentation/kprobes.txt
>> +++ b/Documentation/kprobes.txt
>> @@ -92,7 +92,7 @@ stack contents as the
Hello toshi-san,
On 09/14/2013 05:53 AM, Toshi Kani wrote:
> On Fri, 2013-09-13 at 17:30 +0800, Tang Chen wrote:
> :
>> @@ -100,8 +180,7 @@ phys_addr_t __init_memblock
>> memblock_find_in_range_node(phys_addr_t start,
>> phys_addr_t end, phys_addr_t size,
>>
> From: linux-acpi-ow...@vger.kernel.org
> [mailto:linux-acpi-ow...@vger.kernel.org] On Behalf Of Zheng, Lv
> Sent: Monday, September 16, 2013 8:47 AM
>
> > From: Mika Westerberg [mailto:mika.westerb...@linux.intel.com]
> > Sent: Sunday, September 15, 2013 2:52 PM
> >
> > On Sat, Sep 14, 2013 at
On Mon, Sep 02 2013, majianpeng wrote:
> Hi axboe:
> How about this patch?
Applied.
--
Jens Axboe
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at
Oleg Nesterov wrote:
> Please look at call_usermodehelper_exec() which does this trick. The
> logic is the same, just you need to xchg(create->completion) instead
> of create->owner.
OK. I understood that we can use the same logic.
>From
> From: Mika Westerberg [mailto:mika.westerb...@linux.intel.com]
> Sent: Sunday, September 15, 2013 2:52 PM
>
> On Sat, Sep 14, 2013 at 12:10:37AM +, Zheng, Lv wrote:
> > Is it possible to install the handler for ACPI_ROOT_OBJECT?
> > Can it be achieved by implementing a setup callback?
>
>
Hi, Thomas
On 2013年09月13日 22:32, Thomas Gleixner wrote:
On Fri, 13 Sep 2013, Fan Du wrote:
(2) What I have been bugging you around here for this long time is really the
second
problem, I'm sorry I didn't make it clearly to you and others, which is
below:
Why using wall clock time to
Hi Dave,
Today's linux-next merge of the aio-direct tree got a conflict in
fs/block_dev.c between commits 02afc27faec9 ("direct-io: Handle O_(D)SYNC
AIO") and 73a7075e3f6e ("aio: Kill aio_rw_vect_retry()") from Linus' tree
and commit b176eedb2a8b ("block_dev: add support for read_iter,
On Sun, Sep 15, 2013 at 10:19:41PM +0300, Marcus Sundman wrote:
>
> It's a SanDisk SSD U100.
Here's one report of someone who had an experience with U100 in an
Asus UX31E:
https://communities.intel.com/thread/32515
> A lot. I have lsyncd running here most of the time, backing up to my
> raid-z
Hi Guenter,
Today's linux-next merge of the h8300-remove tree got a conflict in
arch/h8300/Kconfig between commit 0244ad004a54 ("Remove GENERIC_HARDIRQ
config option") from Linus' tree and commit d02babe847bf ("Drop support
for Renesas H8/300 (h8300) architecture") from the h8300-remove tree.
I
On 09/15/2013 03:02 PM, Eduardo Valentin wrote:
This patch adds to tmp102 temperature sensor the possibility
to expose itself as thermal zone device, registered on the
thermal framework.
The thermal zone is built only if a device tree node
describing a thermal zone for this sensor is present
On 09/15/2013 03:02 PM, Eduardo Valentin wrote:
This patch adds to lm75 temperature sensor the possibility
to expose itself as thermal zone device, registered on the
thermal framework.
The thermal zone is built only if a device tree node
describing a thermal zone for this sensor is present
On Thu, 12 Sep 2013 09:50:40 -0700, Soren Brinkmann
wrote:
> Zynq is based on an ARM Cortex-A9 MPCore, which features the
> arm_global_timer in its SCU. Therefore enable the timer for Zynq.
>
> Signed-off-by: Soren Brinkmann
> ---
> arch/arm/boot/dts/zynq-7000.dtsi | 8
>
Hi Lee,
On 09/15/2013 08:17 PM, Thierry Reding wrote:
On Thu, Sep 12, 2013 at 04:28:09PM +0100, Lee Jones wrote:
* Documentation
From Thierry's suggestion, detailed driver description was moved to
'Documentation/lp3943.txt'.
Really? Why here? Do we really want 1000's of driver docs in
This patch improves the ti-soc-thermal driver by adding the
support to build the thermal zones based on DT nodes.
The driver will have two options now to build the thermal
zones. The first option is the zones originally coded
in this driver. So, the driver behavior will be same
if there is no DT
This patch changes the thermal core driver to allow
registration of thermal zones without the .get_temp callback.
The idea behind this change is to allow lazy registration
of sensor callbacks.
The thermal zone will be disabled whenever the ops
does not contain a .get_temp callback. The sysfs
This patch introduces a device tree bindings for
describing the hardware thermal behavior and limits.
Also a parser to read and interpret the data and feed
it in the thermal framework is presented.
This patch introduces a thermal data parser for device
tree. The parsed data is used to build
This patch changes a dtsi file to contain the thermal data
for GPU domain on OMAP5 and later SoCs. This data will
enable a thermal shutdown at 125C.
This thermal data can be reused across TI SoC devices.
Cc: "Benoît Cousson"
Cc: Tony Lindgren
Cc: Rob Herring
Cc: Pawel Moll
Cc: Mark Rutland
This patch changes the dtsi entry on omap5 to contain
the thermal data. This data will enable the passive
cooling with CPUfreq cooling device at 100C. The
system will do a thermal shutdown at 125C whenever
any of its sensors sees this level.
Cc: "Benoît Cousson"
Cc: Tony Lindgren
Cc: Rob
OMAP5 devices can reach high temperatures and thus
needs to have cpufreq-cooling on systems running on it.
This patch adds the required cooling device properties
so that cpufreq-cpu0 driver loads the cooling device.
Cc: "Benoît Cousson"
Cc: Tony Lindgren
Cc: Rob Herring
Cc: Pawel Moll
Cc:
OMAP4430 devices can reach high temperatures and thus
needs to have cpufreq-cooling on systems running on it.
This patch adds the required cooling device properties
so that cpufreq-cpu0 driver loads the cooling device.
Cc: "Benoît Cousson"
Cc: Tony Lindgren
Cc: Russell King
Cc:
OMAP4460 devices can reach high temperatures and thus
needs to have cpufreq-cooling on systems running on it.
This patch adds the required cooling device properties
so that cpufreq-cpu0 driver loads the cooling device.
Cc: "Benoît Cousson"
Cc: Tony Lindgren
Cc: Rob Herring
Cc: Pawel Moll
Cc:
This patch changes a dtsi file to contain the thermal data
for CORE domain on OMAP5 and later SoCs. This data will
enable a thermal shutdown at 125C.
This thermal data can be reused across TI SoC devices.
Cc: "Benoît Cousson"
Cc: Tony Lindgren
Cc: Rob Herring
Cc: Pawel Moll
Cc: Mark Rutland
This patch adds to tmp102 temperature sensor the possibility
to expose itself as thermal zone device, registered on the
thermal framework.
The thermal zone is built only if a device tree node
describing a thermal zone for this sensor is present
inside the tmp102 DT node. Otherwise, the driver
This patch changes the dtsi entry on omap4460 to contain
the thermal data. This data will enable the passive
cooling with CPUfreq cooling device at 100C and the
system will do a thermal shutdown at 125C.
Cc: "Benoît Cousson"
Cc: Tony Lindgren
Cc: Rob Herring
Cc: Pawel Moll
Cc: Mark Rutland
This patch adds to lm75 temperature sensor the possibility
to expose itself as thermal zone device, registered on the
thermal framework.
The thermal zone is built only if a device tree node
describing a thermal zone for this sensor is present
inside the lm75 DT node. Otherwise, the driver
This patch changes a dtsi file to contain the thermal data
for MPU domain on OMAP4 and later SoCs. This data will
enable the passive cooling with CPUfreq cooling device
at 100C and the system will do a thermal shutdown at 125C.
This thermal data can be reused across TI SoC devices.
Cc: "Benoît
This patch changes the dtsi entry on omap4430 to contain
the thermal data. This data will enable the passive
cooling with CPUfreq cooling device at 100C and the
system will do a thermal shutdown at 125C.
Cc: "Benoît Cousson"
Cc: Tony Lindgren
Cc: Russell King
Cc: linux-o...@vger.kernel.org
Cc:
Hello all,
Here is the continuation of work of representing hardware thermal properties
in device tree infrastructure. The present patch series is the third version
of this work. Previous versions were sent as RFCs and can be found here:
RFCv2: http://lkml.org/lkml/2013/8/23/594
RFCv1:
This patch introduces an API to register cpufreq cooling device
based on device tree node.
The registration via device tree node differs from normal
registration due to the fact that it is needed to fill
the device_node structure in order to be able to match
the cooling devices with trip points.
This patch changes the cpufreq-cpu0 driver to consider if
a cpu needs cooling (with cpufreq). In case the cooling is needed,
the cpu0 device tree node needs to be properly configured
with cooling device properties.
In case these properties are present,, the driver will
load a cpufreq cooling
Zaurus collie contains 2 LH28F640BFHE-PTTL90 (64M 4Mx16) and
at the moment cfi will not detect the collie NOR.
In the meanwhile we can revert to the jedec-probe map which has been
fixed with following commit:
mtd: jedec_probe: fix LH28F640BF definition
fe2f4c8e0bf2756b670ee78fa9772613a2ea8495
After commit 72662e01088394577be4a3f14da94cf87bea2591
ARM: head.S: only include __turn_mmu_on in the initial identity mapping
Zaurus PXA devices call sharpsl_save_param() during fixup and hang on
boot because memcpy refers to physical addresses no longer valid if the
MMU is setup.
Zaurus collie
On Sun, Sep 15, 2013 at 4:25 PM, James Bottomley
wrote:
> This patch set is a set of driver updates (megaraid_sas, fnic, lpfc,
> ufs, hpsa) we also have a couple of bug fixes (sd out of bounds and
> ibmvfc error handling) and the first round of esas2r checker fixes and
> finally the much
On Sun, Sep 15, 2013 at 11:04:26PM +0200, Ondrej Zary wrote:
> On Sunday 15 September 2013 22:35:20 Andreas Mohr wrote:
> > What!?!? I didn't quite expect any kernel dev to have that one, too ;)
>
> Don't remember where I got it from but it looked nice so I bought it :)
Yup, e.g. the builtin amp
On Sun, Sep 15, 2013 at 01:26:23PM -0700, Joe Perches wrote:
> People get this regularly wrong and it breaks the LTO builds,
> as it causes a section attribute conflict.
>
> Original-patch-by: Andi Kleen
> Signed-off-by: Joe Perches
Thanks looks good.
-Andi
--
To unsubscribe from this list:
On Sunday 15 September 2013 22:35:20 Andreas Mohr wrote:
> Hi,
>
> On Sun, Sep 15, 2013 at 10:25:45PM +0200, Ondrej Zary wrote:
> > On Sunday 15 September 2013 20:49:02 Andreas Mohr wrote:
> > BTW. I've got an AZT3328 card and it works fine with your driver. Thanks
> > for it.
>
> What!?!? I
Hi,
Here is the second round of the OMAP SSI driver patches.
In this round I added/fixed:
- Usage of runtime PM
Previously runtime PM was only used to enable/disable the involved
clocks. Now the driver makes use of resume/suspend callbacks, which
simplified its code (the driver did its own
Add SSI device tree data for OMAP34xx and Nokia N900.
Signed-off-by: Sebastian Reichel
---
Documentation/devicetree/bindings/hsi/omap_ssi.txt | 73 ++
arch/arm/boot/dts/omap3-n900.dts | 8 +++
arch/arm/boot/dts/omap34xx.dtsi| 49
This patch adds Synchronous Serial Interface (SSI) hwmod support for
OMAP34xx SoCs.
Signed-off-by: Sebastian Reichel
---
arch/arm/mach-omap2/omap_hwmod_3xxx_data.c | 48 ++
1 file changed, 48 insertions(+)
diff --git a/arch/arm/mach-omap2/omap_hwmod_3xxx_data.c
Hi,
On Sun, Sep 15, 2013 at 10:25:45PM +0200, Ondrej Zary wrote:
> On Sunday 15 September 2013 20:49:02 Andreas Mohr wrote:
> BTW. I've got an AZT3328 card and it works fine with your driver. Thanks for
> it.
What!?!? I didn't quite expect any kernel dev to have that one, too ;)
(got several
People get this regularly wrong and it breaks the LTO builds,
as it causes a section attribute conflict.
Original-patch-by: Andi Kleen
Signed-off-by: Joe Perches
---
scripts/checkpatch.pl | 24 ++--
1 file changed, 22 insertions(+), 2 deletions(-)
diff --git
On Sunday 15 September 2013 20:49:02 Andreas Mohr wrote:
> Hi,
>
> > ES938 is controlled by MIDI SysEx commands sent through card's MPU401
> > port.
> >
> > The following patch works but has a problem: the midi port cannot be used
> > by userspace applications. Opening and closing the rawmidi
This patch set is a set of driver updates (megaraid_sas, fnic, lpfc,
ufs, hpsa) we also have a couple of bug fixes (sd out of bounds and
ibmvfc error handling) and the first round of esas2r checker fixes and
finally the much anticipated big endian additions for megaraid_sas.
The patch is
Hello My Dear,
My name is Miss Glory , I like to be your friends ok;
Please send me your e-mail to my inbox at (glory01...@yahoo.com)
so i will send you my Photos to you
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On Sun, 2013-09-15 at 13:34 +0200, Manfred Spraul wrote:
> Hi all,
>
> On 09/15/2013 08:09 AM, Mike Galbraith wrote:
> > On Sat, 2013-09-14 at 23:34 +0200, Manfred Spraul wrote:
> >
> >> The bug is probably also present in 3.10 and 3.11, but for these kernels
> >> is is probably simpler just to
This patch changes the behavior of TI SoC thermal driver
when there is a PCB thermal zone.
Instead of reporting an error code when reading from
PCB temperature sensor fails, this patch will make
the driver attempt to compose the hotspot extrapolation
based on bandgap readings only.
Cc: Zhang Rui
On 14.09.2013 05:41, Theodore Ts'o wrote:
On Thu, Sep 12, 2013 at 08:59:07PM +0300, Marcus Sundman wrote:
At 128 GB it is extremely small as it is, and I'm really struggling
to fit all on it. Most of my stuff is on my NAS (which has almost 10
TB space), but still I need several code
Hello Greg!
On Wed, Sep 04, 2013 at 11:28:59PM -0700, Greg Thelen wrote:
> --- a/Documentation/cgroups/memory.txt
> +++ b/Documentation/cgroups/memory.txt
> @@ -571,15 +571,19 @@ an memcg since the pages are allowed to be allocated
> from any physical
> node. One of the use cases is evaluating
Hi Greg,
On Wed, Sep 04, 2013 at 11:28:58PM -0700, Greg Thelen wrote:
> + struct numa_stat {
> + const char *name;
> + unsigned int lru_mask;
> + };
> +
> + static const struct numa_stat stats[] = {
> + { "total", LRU_ALL },
> + {
Hi,
> ES938 is controlled by MIDI SysEx commands sent through card's MPU401 port.
>
> The following patch works but has a problem: the midi port cannot be used by
> userspace applications. Opening and closing the rawmidi device on each control
> change would probably work (as long as the port is
1 - 100 of 360 matches
Mail list logo
