On Tue, Sep 10, 2013 at 04:42:17PM +0400, Sergei Shtylyov wrote:
>This contradicts to the patch subject.
Sorry, Sergei et al.
I screwed this series is bit. The second 5/9 fixes that.
> WBR, Sergei
>
--
Regards,
Alexander Gordeev
agord...@redhat.com
--
To unsubscribe from this list: send
On Tue, Sep 10, 2013 at 3:00 PM, Arnaldo Carvalho de Melo
wrote:
>
>
> Em Mon, Sep 09, 2013 at 04:48:44PM -0300, Arnaldo Carvalho de Melo escreveu:
> > Em Mon, Sep 09, 2013 at 04:47:45PM -0300, Arnaldo Carvalho de Melo escreveu:
> > > I noticed the kernel part is in, and I'm going to use MMAP2 on
Hi guys,
On Mon, Sep 09, 2013 at 07:15:31AM +0100, Alexandre Courbot wrote:
> On Fri, Sep 6, 2013 at 3:35 AM, Rob Herring wrote:
> > On 09/04/2013 10:27 PM, Alexandre Courbot wrote:
> >> Trusted Foundations is a TrustZone-based secure monitor for ARM that
> >> can be invoked using a consistent
Hi Jonathan,
Sorry for the continued development and resubmission. I won't write
anymore patches now. At least until these have been accepted.
This patch-set includes a few clean-ups surrounding error handling and
non-mandatory functionality along with regulator support and the addition
of a new
Turns out that they're actually not required and the driver probes just
fine without them. The ID is incorrect at the moment anyway. They actually
currently specify the stn8815.
Signed-off-by: Lee Jones
---
arch/arm/boot/dts/ste-dbx5x0.dtsi | 5 -
1 file changed, 5 deletions(-)
diff --git
After applying this node the LPS001WP sensor chip should probe
successfully once the driver support has also been applied.
Signed-off-by: Lee Jones
---
arch/arm/boot/dts/ste-snowball.dts | 10 ++
1 file changed, 10 insertions(+)
diff --git a/arch/arm/boot/dts/ste-snowball.dts
LPS001WP is a Pressure and Temperature sensor.
Signed-off-by: Lee Jones
---
.../devicetree/bindings/iio/pressure/lps001wp.txt | 21 +
1 file changed, 21 insertions(+)
create mode 100644 Documentation/devicetree/bindings/iio/pressure/lps001wp.txt
diff --git
Signed-off-by: Lee Jones
---
arch/arm/configs/u8500_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/configs/u8500_defconfig b/arch/arm/configs/u8500_defconfig
index 24f88d6..4b94b42 100644
--- a/arch/arm/configs/u8500_defconfig
+++ b/arch/arm/configs/u8500_defconfig
@@
After applying this node the L3G4200D sensor chip should probe
successfully once the driver support has also been applied.
Signed-off-by: Lee Jones
---
arch/arm/boot/dts/ste-snowball.dts | 8
1 file changed, 8 insertions(+)
diff --git a/arch/arm/boot/dts/ste-snowball.dts
Signed-off-by: Lee Jones
---
arch/arm/configs/u8500_defconfig | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/configs/u8500_defconfig b/arch/arm/configs/u8500_defconfig
index a0025dc..6b29109 100644
--- a/arch/arm/configs/u8500_defconfig
+++ b/arch/arm/configs/u8500_defconfig
@@
Signed-off-by: Lee Jones
---
arch/arm/configs/u8500_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/configs/u8500_defconfig b/arch/arm/configs/u8500_defconfig
index 6b29109..24f88d6 100644
--- a/arch/arm/configs/u8500_defconfig
+++ b/arch/arm/configs/u8500_defconfig
@@
Em Mon, Sep 09, 2013 at 04:48:44PM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Mon, Sep 09, 2013 at 04:47:45PM -0300, Arnaldo Carvalho de Melo escreveu:
> > I noticed the kernel part is in, and I'm going to use MMAP2 on that new
> > tool, so tried merging it, but:
> >
> > I fixed it up wrt
After applying this node the LSM303DLH sensor chip should probe
successfully once the driver support has also been applied.
Signed-off-by: Lee Jones
---
arch/arm/boot/dts/ste-snowball.dts | 8
1 file changed, 8 insertions(+)
diff --git a/arch/arm/boot/dts/ste-snowball.dts
Signed-off-by: Lee Jones
---
arch/arm/configs/u8500_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/configs/u8500_defconfig b/arch/arm/configs/u8500_defconfig
index 4b94b42..aaa6c0a 100644
--- a/arch/arm/configs/u8500_defconfig
+++ b/arch/arm/configs/u8500_defconfig
@@
L3G4200D is a Gyroscope Sensor
Signed-off-by: Lee Jones
---
.../devicetree/bindings/iio/gyro/l3g4200d.txt | 21 +
1 file changed, 21 insertions(+)
create mode 100644 Documentation/devicetree/bindings/iio/gyro/l3g4200d.txt
diff --git
Strip out all those unnecessary gotos and just return the error right away.
Aids to simplicity and reduces code.
Signed-off-by: Lee Jones
---
drivers/iio/common/st_sensors/st_sensors_core.c | 18 +++---
1 file changed, 7 insertions(+), 11 deletions(-)
diff --git
LSM303DLH is a Accelerometer Sensor
Signed-off-by: Lee Jones
---
.../devicetree/bindings/iio/accel/lsm303dlh.txt | 21 +
1 file changed, 21 insertions(+)
create mode 100644 Documentation/devicetree/bindings/iio/accel/lsm303dlh.txt
diff --git
Gets rid of those unnecessary gotos.
Signed-off-by: Lee Jones
---
drivers/iio/common/st_sensors/st_sensors_core.c | 17 +++--
1 file changed, 7 insertions(+), 10 deletions(-)
diff --git a/drivers/iio/common/st_sensors/st_sensors_core.c
Some of ST's sensors are appended with their sensor type and some
are not. For consistency we're extending the same naming convention
throughout.
Signed-off-by: Lee Jones
---
drivers/iio/pressure/st_pressure.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Some of ST's sensors are appended with their sensor type and some
are not. For consistency we're extending the same naming convention
throughout.
Signed-off-by: Lee Jones
---
drivers/iio/magnetometer/st_magn.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Some of ST's sensors are appended with their sensor type and some
are not. For consistency we're extending the same naming convention
throughout.
Signed-off-by: Lee Jones
---
drivers/iio/accel/st_accel.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
Some of ST's sensors are appended with their sensor type and some
are not. For consistency we're extending the same naming convention
throughout.
Signed-off-by: Lee Jones
---
drivers/iio/gyro/st_gyro.h | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git
LSM303DLH is a Magnetometer Sensor
Signed-off-by: Lee Jones
---
.../bindings/iio/magnetometer/lsm303dlh.txt | 21 +
1 file changed, 21 insertions(+)
create mode 100644
Documentation/devicetree/bindings/iio/magnetometer/lsm303dlh.txt
diff --git
Not all ST's sensors support data ready, so let's make the declaration
of one conditional.
Signed-off-by: Lee Jones
---
drivers/iio/common/st_sensors/st_sensors_core.c | 24 +++-
drivers/iio/pressure/st_pressure_core.c | 3 ++-
2 files changed, 21 insertions(+), 6
Saving a few lines of code.
Signed-off-by: Lee Jones
---
drivers/iio/common/st_sensors/st_sensors_core.c | 11 ---
1 file changed, 4 insertions(+), 7 deletions(-)
diff --git a/drivers/iio/common/st_sensors/st_sensors_core.c
b/drivers/iio/common/st_sensors/st_sensors_core.c
index
On Tue, Sep 10, 2013 at 5:51 AM, Ramkumar Ramachandra
wrote:
> Stephane Eranian wrote:
>> a simple multithreaded program where
>> #threads >> #CPUs
>
> To put it another way, does Intel's HT work for CPU intensive and IO
> minimal tasks? I think HT assumes some amount of inefficient IO
> coupled
On Mon, Sep 09, 2013 at 09:13:07PM +0800, Yijing Wang wrote:
> The PCI core caches the "PCI-E Max Payload Size Supported" in
> pci_dev->pcie_mpss, so use that instead of pcie_capability_read_dword().
> Also use pcie_set_readrq() instead of pcie_capability_clear_and_set_word()
> to simplify code.
>
On Tuesday 10 September 2013 05:39 PM, Mark Brown wrote:
* PGP Signed by an unknown key
On Tue, Sep 10, 2013 at 04:48:08PM +0530, Laxman Dewangan wrote:
+- regulator-enable-time: Turn ON time for regulator(in uS)
This is unclear - what is a "turn on time" and is this in addition to or
Some chips either don't support it or fail to provide adequate documentation,
so sometimes it's impossible to enable the feature even if it is supported.
Signed-off-by: Lee Jones
---
drivers/iio/common/st_sensors/st_sensors_core.c | 11 +++
drivers/iio/pressure/st_pressure_core.c
Here we use existing practices to introduce support for another
pressure/temperature sensor, the LPS001WP.
Signed-off-by: Lee Jones
---
drivers/iio/pressure/st_pressure.h | 1 +
drivers/iio/pressure/st_pressure_core.c | 84 +
They're currently named *_1_*, for 'Sensor 1', but the code will be much
more readable if we use the naming convention *_LPS331AP_* instead.
Signed-off-by: Lee Jones
---
drivers/iio/pressure/st_pressure_core.c | 94 -
1 file changed, 46 insertions(+), 48
Due to the MACRO used, the task of reading, understanding and maintaining
the LPS331AP's channel descriptor is substantially difficult. This patch
is based on the view that it's better to have easy to read, maintainable
code than to save a few lines here and there. For that reason we're
expanding
The power to some of the sensors are controlled by regulators. In most
cases these are 'always on', but if not they will fail to work until
the regulator is enabled using the relevant APIs. This patch allows for
the Vdd power supply to be specified by either platform data or Device
Tree.
This patch contains some pretty basic clean-ups in probe() pertaining to
the simplification of error handling and a couple of readability adaptions.
Signed-off-by: Lee Jones
---
drivers/iio/pressure/st_pressure_core.c | 32
1 file changed, 16 insertions(+), 16
The power to some of the sensors are controlled by regulators. In most
cases these are 'always on', but if not they will fail to work until
the regulator is enabled using the relevant APIs. This patch allows for
the Vdd_IO power supply to be specified by either platform data or
Device Tree.
Reduce the amount of those unnecessary goto calls, as in most cases
we can simply return immediately. We also only call for the IRQ number
once and use that value throughout.
Signed-off-by: Lee Jones
---
drivers/iio/accel/st_accel_core.c | 21 ++---
1 file changed, 10
The LSM303DLH's WAI (WhoAmI) is 0x33, meaning it should be enabled by
Accel Sensor group one. For the device to probe without error, we'll
need to ensure it's registered with the correct WAI.
Signed-off-by: Lee Jones
---
drivers/iio/accel/st_accel_core.c | 4 ++--
1 file changed, 2
At the moment the driver is silent in some error cases and if successful.
Prior to this patch there was no clear way to know if the driver succeeded
or not without looking deep into sysfs.
Signed-off-by: Lee Jones
---
drivers/iio/pressure/st_pressure_core.c | 3 +++
1 file changed, 3
At the moment the driver is silent in some error cases and if successful.
Prior to this patch there was no clear way to know if the driver succeeded
or not without looking deep into sysfs.
Signed-off-by: Lee Jones
---
drivers/iio/gyro/st_gyro_core.c | 3 +++
1 file changed, 3 insertions(+)
At the moment the driver is silent in some error cases and if successful.
Prior to this patch there was no clear way to know if the driver succeeded
or not without looking deep into sysfs.
Signed-off-by: Lee Jones
---
drivers/iio/accel/st_accel_core.c | 3 +++
1 file changed, 3 insertions(+)
Stephane Eranian wrote:
> a simple multithreaded program where
> #threads >> #CPUs
To put it another way, does Intel's HT work for CPU intensive and IO
minimal tasks? I think HT assumes some amount of inefficient IO
coupled with pure CPU usage.
--
To unsubscribe from this list: send the line
Reduce the amount of those unnecessary goto calls, as in most cases
we can simply return immediately. We also only call for the IRQ number
once and use that value throughout.
Signed-off-by: Lee Jones
---
drivers/iio/gyro/st_gyro_core.c | 21 ++---
1 file changed, 10
Reduce the amount of those unnecessary goto calls, as in most cases
we can simply return immediately. We also only call for the IRQ number
once and use that value throughout.
Signed-off-by: Lee Jones
---
drivers/iio/magnetometer/st_magn_core.c | 21 ++---
1 file changed, 10
At the moment the number of channels specified is dictated by the first
sensor supported by the driver. As we add support for more sensors this
is likely to vary. Instead of using the ARRAY_SIZE() of the LPS331AP's
channel specifier we'll use a new adaptable 'struct st_sensors' element
instead.
Trivial patch adding the LSM303DLH to the list of already supported
Magnetometer Sensors.
Signed-off-by: Lee Jones
---
drivers/iio/magnetometer/st_magn.h | 1 +
drivers/iio/magnetometer/st_magn_core.c | 3 ++-
2 files changed, 3 insertions(+), 1 deletion(-)
diff --git
At the moment the driver is silent in some error cases and if successful.
Prior to this patch there was no clear way to know if the driver succeeded
or not without looking deep into sysfs.
Signed-off-by: Lee Jones
---
drivers/iio/magnetometer/st_magn_core.c | 3 +++
1 file changed, 3
After applying this node the LSM303DLH sensor chip should probe
successfully once the driver support has also been applied.
Signed-off-by: Lee Jones
---
arch/arm/boot/dts/ste-snowball.dts | 8
1 file changed, 8 insertions(+)
diff --git a/arch/arm/boot/dts/ste-snowball.dts
Il 28/08/2013 22:58, Chris Metcalf ha scritto:
> This change enables support for a virtio-based console,
> network support, and block driver support.
>
> We remove some debug code in relocate_kernel_64.S that made raw
> calls to the hv_console_putc Tilera hypervisor API, since everything
> now
On Mon, 2013-09-09 at 14:19 +0800, Joe Jin wrote:
> When do disk pull/insert test we encountered below:
>
> WARNING: at fs/sysfs/dir.c:455 sysfs_add_one+0xbc/0xe0()
> Hardware name: SUN FIRE X4370 M2 SERVER
> sysfs: cannot create duplicate filename
>
Hey Linus,
Please git pull the following tag:
git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git
stable/for-linus-3.12-rc0-tag-two
This pull I usually do after rc1 is out but because we have a nice amount
of fixes, some bootup related fixes for ARM, and it is early in the cycle we
Stephane Eranian wrote:
> [ 2229.021966] Call Trace:
> [ 2229.021967][] dump_stack+0x46/0x58
> [ 2229.021976] [] warn_slowpath_common+0x8c/0xc0
> [ 2229.021979] [] warn_slowpath_fmt+0x46/0x50
> [ 2229.021982] [] intel_pmu_drain_pebs_hsw+0xa8/0xc0
> [ 2229.021986] []
Hello.
On 09-09-2013 19:26, Alexander Gordeev wrote:
Signed-off-by: Alexander Gordeev
---
arch/s390/pci/pci.c |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/arch/s390/pci/pci.c b/arch/s390/pci/pci.c
index f17a834..c79c6e4 100644
--- a/arch/s390/pci/pci.c
+++
Add missing cc of linux-scsi
On Tue, 2013-09-10 at 15:03 +0900, Tetsuo Handa wrote:
> Hello.
>
> I got below warning on current linux.git .
>
> --
> [2.612237] scsi: * BusLogic SCSI Driver Version 2.1.16 of 18 July
> 2002 *
> [2.613067] scsi: Copyright 1995-1998 by
Milosz Tanski wrote:
> __fscache_check_consistency() does not decrement the count of operations
> active after it finishes in the success case. This leads to a hung tasks on
> cookie de-registration (commonly in inode eviction).
>
> INFO: task kworker/1:2:4214 blocked for more than 120 seconds.
On Tue, Sep 10, 2013 at 10:51:00AM +0300, Mika Westerberg wrote:
> On Mon, Sep 09, 2013 at 04:40:28PM +0100, Mark Brown wrote:
> > How is this going to interact with client devices which are already
> > enabling runtime PM for themselves, and what are the advantages of doing
> > this over having
Hello,
I recent upgraded from 3.10 to 3.11 and see these on occasion in the kernel log:
perf samples too long (2501 > 2500), lowering
kernel.perf_event_max_sample_rate to 5
perf samples too long (5040 > 5000), lowering
kernel.perf_event_max_sample_rate to 25000
I was curious what is causing
Hi,
Ok, so I am able to reproduce the problem using a simpler
test case with a simple multithreaded program where
#threads >> #CPUs.
[ 2229.021934] WARNING: CPU: 6 PID: 17496 at
arch/x86/kernel/cpu/perf_event_intel_ds.c:1003
intel_pmu_drain_pebs_hsw+0xa8/0xc0()
[ 2229.021936] Unexpected number
On Tue, Sep 10, 2013 at 07:29:40PM +0800, Wei Ni wrote:
> On my platform, it use palmas-regulator.c, ldo6 for this lm90 power
> rail. I checked this driver, it will handle ramp_delay except LDOx.
> Since I'm not familiar with this palmas device and driver, so do you
> mean I can set
On Tue, Sep 10, 2013 at 04:48:07PM +0530, Laxman Dewangan wrote:
> As per datasheet (Referred TPS65913), the on-time for LDO is
> 500micro second. If LDO6 is in vibrator mode then the on-time
> is 2000us.
Applied, thanks.
signature.asc
Description: Digital signature
On Tue, Sep 10, 2013 at 04:48:08PM +0530, Laxman Dewangan wrote:
> +- regulator-enable-time: Turn ON time for regulator(in uS)
This is unclear - what is a "turn on time" and is this in addition to or
separate from the underlying enable time of the device? It needs to be
clear that this is the
On Tuesday 10 September 2013 05:27 PM, George Cherian wrote:
On 9/10/2013 2:47 PM, Laxman Dewangan wrote:
On Tuesday 10 September 2013 01:19 PM, George Cherian wrote:
In OMAP5 when USB-HOST is set true, the VBUS regulator is turned ON.
This causes a VBUS interrupt, ignore the same if we are
On Fri, Sep 06, 2013 at 05:14:49PM +0100, Catalin Marinas wrote:
> On Fri, Sep 06, 2013 at 10:19:18AM +0100, Leif Lindholm wrote:
> > --- a/arch/arm/kernel/setup.c
> > +++ b/arch/arm/kernel/setup.c
> > @@ -877,6 +878,10 @@ void __init setup_arch(char **cmdline_p)
> >
> >
Il 10/09/2013 12:53, Gleb Natapov ha scritto:
>> > +#ifndef __KERNEL__
>> > +/* For hv_*() */
>> > +#define KVM_EMULATE(name) [HV_SYS_##name] = qemu_emulate_illegal,
>> > +#define USER_EMULATE(name) [HV_SYS_##name] = qemu_emulate_hv_##name,
>> > +#define NO_EMULATE(name) [HV_SYS_##name] =
On Tue, Sep 10, 2013 at 05:24:15PM +0900, Namhyung Kim wrote:
> Hello,
>
> Linus reported that perf report was stuck in after "processing time
> ordered events". It turned out that merging/collapsing the callchain
> takes most of time to look up a matching callchain. Since it did a
> linear
On 9/10/2013 2:47 PM, Laxman Dewangan wrote:
On Tuesday 10 September 2013 01:19 PM, George Cherian wrote:
In OMAP5 when USB-HOST is set true, the VBUS regulator is turned ON.
This causes a VBUS interrupt, ignore the same if we are already in
USB-HOST.
Signed-off-by: George Cherian
---
* Stephane Eranian wrote:
> Hi,
>
>
> And what was the perf record command line for this crash?
AFAICS it wasn't a crash but the WARN_ON() in intel_pmu_drain_pebs_hsw(),
at arch/x86/kernel/cpu/perf_event_intel_ds.c:1003.
at = (struct pebs_record_hsw *)(unsigned
Frantisek Hrbata writes:
> On Mon, Sep 09, 2013 at 10:44:03AM +0930, Rusty Russell wrote:
>> Kyle McMartin writes:
>> > On Fri, Sep 06, 2013 at 07:51:18PM +0200, Frantisek Hrbata wrote:
>> >> > > v2: - reuse mod->ctors for .init_array section for modules, because
>> >> > > gcc uses
>> >> > >
On Tue, Sep 10, 2013 at 1:31 PM, Stephan Mueller wrote:
> /dev/random uses the get_cycles() function to obtain entropy in addition to
> jiffies and the event value of hardware events.
>
> Typically the high-resolution timer of get_cycles delivers the majority of
> entropy, because the event
On Mon, Sep 9, 2013 at 7:28 AM, Wang Shilong wrote:
> On 09/08/2013 12:15 AM, Azat Khuzhin wrote:
>>
>> Signed-off-by: Azat Khuzhin
>> ---
>> fs/btrfs/volumes.c |2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/fs/btrfs/volumes.c b/fs/btrfs/volumes.c
>> index
On Tuesday, September 10, 2013 04:59:29 PM Viresh Kumar wrote:
> On 9 September 2013 20:41, Guennadi Liakhovetski
> wrote:
> > Sorry guys, I'm trying my best to stop this patch from propagating to
> > stable and to get it fixed asap, so, the CC list might be a bit excessive.
> > Also trying to
On Tue, Sep 10, 2013 at 12:25:54PM +0200, Ingo Molnar wrote:
>
> * Jiri Olsa wrote:
>
> > On Tue, Sep 10, 2013 at 05:24:16PM +0900, Namhyung Kim wrote:
> > > From: Namhyung Kim
> > >
> > > Current collapse stage has a scalability problem which can be
> > > reproduced easily with parallel
Hi Ralf,
I was poking about the preempt_count muck and stumbled upon this..
Should you be using the pagefault_*() methods here?
--- a/arch/mips/mm/init.c
+++ b/arch/mips/mm/init.c
@@ -124,7 +124,7 @@ void *kmap_coherent(struct page *page, u
BUG_ON(Page_dcache_dirty(page));
-
Hi,
/dev/random uses the get_cycles() function to obtain entropy in addition to
jiffies and the event value of hardware events.
Typically the high-resolution timer of get_cycles delivers the majority of
entropy, because the event value is quite deterministic and jiffies are very
coarse.
On 9 September 2013 20:41, Guennadi Liakhovetski wrote:
> Sorry guys, I'm trying my best to stop this patch from propagating to
> stable and to get it fixed asap, so, the CC list might be a bit excessive.
> Also trying to fix the originally spare cc list, which makes it impossible
> for me to
Hi,
And what was the perf record command line for this crash?
On Mon, Sep 9, 2013 at 12:05 PM, Peter Zijlstra wrote:
> On Sat, Sep 07, 2013 at 07:17:28PM -0700, Linus Torvalds wrote:
>> This is new for me, but I suspect it is more related to the new
>> Haswell CPU I have than necessarily the
On 09/10/2013 06:13 PM, Mark Brown wrote:
> * PGP Signed by an unknown key
>
> On Tue, Sep 10, 2013 at 01:39:59PM +0800, Wei Ni wrote:
>
>> I think the device need time to wait stable after power on, but it's
>> difficult to get an exact delay value, and this delay may also relate
>> with
On Tuesday, September 10, 2013 10:51:00 AM Mika Westerberg wrote:
> On Mon, Sep 09, 2013 at 04:40:28PM +0100, Mark Brown wrote:
> > On Mon, Sep 09, 2013 at 04:34:38PM +0300, Mika Westerberg wrote:
> >
> > > + /*
> > > + * Enable runtime PM for the client device. If the client wants to
> > > + *
On Tue, 10 Sep 2013, Sachin Kamat wrote:
> Fixes the following error:
> drivers/mfd/aat2870-core.c:296:20: error:
> incompatible types in comparison expression (different type sizes)
>
> Signed-off-by: Sachin Kamat
> Cc: Jin Park
> ---
> drivers/mfd/aat2870-core.c |2 +-
> 1 file changed,
On Monday, September 09, 2013 11:52:44 PM Jonathan Callen wrote:
> On 07/27/2013 09:24 AM, Rafael J. Wysocki wrote:
> > From: Rafael J. Wysocki Subject: ACPI: Move
> > acpi_bus_get_device()
> > from bus.c to scan.c
> >
> > Move acpi_bus_get_device() from bus.c to scan.c which allows
> >
On Tue, Sep 10, 2013 at 11:56:17AM +0100, Sudeep KarkadaNagesha wrote:
> > So we only need to change all clkdev registration to use "cpu0" as
> > dev_id intstead of "cpufreq-cpu0.0", something like below.
> >
> > And for imx, it should work even without the changes, because we have
> > device
On Tue, Sep 10, 2013 at 05:06:06PM +0900, Namhyung Kim wrote:
> Hi,
>
> On Thu, 5 Sep 2013 14:42:44 +0200, Frederic Weisbecker wrote:
> > On Thu, Sep 05, 2013 at 12:56:39PM +0200, Ingo Molnar wrote:
> >>
> >> (Cc:-ed Frederic and Namhyung as well, it's about bad overhead in
> >>
Fixes the following error:
drivers/mfd/aat2870-core.c:296:20: error:
incompatible types in comparison expression (different type sizes)
Signed-off-by: Sachin Kamat
Cc: Jin Park
---
drivers/mfd/aat2870-core.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On Tue, 10 Sep 2013, wwang wrote:
> 于 2013年09月10日 17:28, Lee Jones 写道:
> >I would like some more information in the commit log though. You're
> >making a lot of configuration changes here and due to the
> >incomprehensible 'magic numbers' used previously, it's impossible to
> >know what you're
As per datasheet (Referred TPS65913), the on-time for LDO is
500micro second. If LDO6 is in vibrator mode then the on-time
is 2000us.
Set the enable_time on regulator descriptor accordingly.
Signed-off-by: Laxman Dewangan
---
drivers/regulator/palmas-regulator.c |6 ++
1 files changed,
The Turn-ON time of the regulator depends on the regulator device's
electrical characteristics. Sometimes regulator turn-on time also
depends on the capacitive load on the given platform and it can be
more than the datasheet value.
The driver provides the enable-time as per datasheet.
Add
There is a small race between copy_process() and cgroup_attach_task()
where child->se.parent,cfs_rq point to invalid(old) ones.
parent doing fork() | someone moving the parent to another cgroup
---+-
On 10/09/13 03:44, Shawn Guo wrote:
> On Mon, Sep 09, 2013 at 04:24:18PM +0100, Sudeep KarkadaNagesha wrote:
>> Hi Shawn,
>>
>> Ok. But I am bit suspicious about devm_clk_get(cpu_dev, NULL).
>> I don't understand completely as how the clock are registered(whether
>> with dev_id or with
register_blkdev(0, NULL) can result kernel Oops by copying from NULL
in strlcpy(). Fix it by checking NULL pointer at the beginning.
Signed-off-by: Vaughan Cao
---
block/genhd.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/block/genhd.c b/block/genhd.c
index dadf42b..9564f19 100644
Commit-ID: 6979287a7df66a92d6f308338e972a406f9ef842
Gitweb: http://git.kernel.org/tip/6979287a7df66a92d6f308338e972a406f9ef842
Author: Yinghai Lu
AuthorDate: Fri, 6 Sep 2013 19:07:09 -0700
Committer: Ingo Molnar
CommitDate: Tue, 10 Sep 2013 09:51:34 +0200
x86/mm: Add 'step_size'
On Tue, Sep 10, 2013 at 11:24:52AM +0300, Ville Syrjälä wrote:
> On Tue, Sep 10, 2013 at 10:02:48AM +0200, Daniel Vetter wrote:
> > Instead of just a flag bit for each of the positive/negative sync
> > modes drm actually uses a separate flag for each ... This upsets the
> > modeset checker since
On Tue, Sep 10, 2013 at 01:54:01PM +0800, ZHAO Gang wrote:
> When running ` scripts/kernel-doc include/linux/regulator/driver.h
> >/dev/null`, I get following error and warning:
Applied, thanks.
signature.asc
Description: Digital signature
On Tue, Sep 10, 2013 at 10:58:12AM +0100, Will Deacon wrote:
> Vince's perf fuzzer uncovered the following issue on Alpha:
>
> Unable to handle kernel paging request at virtual address fbfe4e46a0e8
> CPU 0 perf_fuzzer(1278): Oops 0
> pc = [] ra = [] ps = 0007Not tainted
> pc is at
* Jiri Olsa wrote:
> On Tue, Sep 10, 2013 at 05:24:16PM +0900, Namhyung Kim wrote:
> > From: Namhyung Kim
> >
> > Current collapse stage has a scalability problem which can be
> > reproduced easily with parallel kernel build. This is because it
> > needs to traverse every children of
On Tue, Sep 10, 2013 at 01:39:59PM +0800, Wei Ni wrote:
> I think the device need time to wait stable after power on, but it's
> difficult to get an exact delay value, and this delay may also relate
> with platform design, so how about to add a optional property in the DT
> node, such as
On 10.09.2013 11:44, Daniel Vetter wrote:
Thanks. Combined with your two patches and Jesse Barnes' patch
"add early quirk for reserving Intel graphics stolen memory v5",
current linux master branch works fine on i915GM hardware now.
cu,
Knut
--
To unsubscribe from this list: send the line
On Mon, Sep 09, 2013 at 10:13:56PM -0600, Stephen Warren wrote:
> On 09/09/2013 09:53 PM, Guenter Roeck wrote:
> > Earlier comments suggest that this is not the intended use case for
> > regulator_get_optional().
That's right.
> Isn't the issue only whether the optional aspect of the regulator
Christian Kujau writes:
> On Sun, 8 Sep 2013 at 23:42, Eric W. Biederman wrote:
>> The check with hidepid is can you ptrace the process. I expect there
>> is something with those sgid processes that keeps you from ptracing
>> them.
>
> Indeed, I cannot strace the process. But still, I wonder if
Vince's perf fuzzer uncovered the following issue on Alpha:
Unable to handle kernel paging request at virtual address fbfe4e46a0e8
CPU 0 perf_fuzzer(1278): Oops 0
pc = [] ra = [] ps = 0007Not tainted
pc is at alpha_perf_event_set_period+0x60/0xf0
ra is at alpha_pmu_enable+0x1a4/0x1c0
v0
于 2013年09月10日 17:28, Lee Jones 写道:
I would like some more information in the commit log though. You're
making a lot of configuration changes here and due to the
incomprehensible 'magic numbers' used previously, it's impossible to
know what you're changing by just reading the code.
Why won't the
Provide the rail supply voltage through descriptor to the
core and remove the callbacks which implement the get_voltage
and list_voltage.
Signed-off-by: Laxman Dewangan
---
drivers/regulator/fixed.c | 28 ++--
1 files changed, 2 insertions(+), 26 deletions(-)
diff
701 - 800 of 1878 matches
Mail list logo