On Tue, Feb 11, 2014 at 08:50:13AM -0300, Arnaldo Carvalho de Melo wrote:
Em Tue, Feb 11, 2014 at 12:14:21PM +0100, Peter Zijlstra escreveu:
On Tue, Feb 11, 2014 at 12:08:56PM +0100, Stephane Eranian wrote:
Assuming you can decode and get the info about the base registers used,
you'd have
On Wed, 12 Feb 2014, dl...@gmx.de wrote:
From: Behan Webster beh...@converseincode.com
The only real change is passing in event_mask to the formerly nested
functions.
Otherwise it's just moving around function and macro code.
This is the only place in the Linux kernel where nested
On Tue, Feb 11, 2014 at 6:10 PM, Pawel Moll pawel.m...@arm.com wrote:
... so debugfs interfaces are easier to use.
Cc: Linus Walleij linus.wall...@linaro.org
Cc: Alexandre Courbot gnu...@gmail.com
Cc: Samuel Ortiz sa...@linux.intel.com
Cc: Lee Jones lee.jo...@linaro.org
Signed-off-by:
On Thu, Feb 13, 2014 at 2:02 PM, Jiri Olsa jo...@redhat.com wrote:
On Tue, Feb 11, 2014 at 08:50:13AM -0300, Arnaldo Carvalho de Melo wrote:
Em Tue, Feb 11, 2014 at 12:14:21PM +0100, Peter Zijlstra escreveu:
On Tue, Feb 11, 2014 at 12:08:56PM +0100, Stephane Eranian wrote:
Assuming you can
On Tue, Feb 11, 2014 at 11:29 AM, Linus Walleij
linus.wall...@linaro.org wrote:
The DBx500 and ABx500 should be getting their IRQs from the
device tree and nowhere else. Get rid of all the static assignments
everywhere, delete it from the driver, platform data and the
board files in one swift
On Thu, 2014-02-13 at 13:08 +, Linus Walleij wrote:
On Tue, Feb 11, 2014 at 6:10 PM, Pawel Moll pawel.m...@arm.com wrote:
... so debugfs interfaces are easier to use.
Cc: Linus Walleij linus.wall...@linaro.org
Cc: Alexandre Courbot gnu...@gmail.com
Cc: Samuel Ortiz
On Wed, Feb 12, 2014 at 11:30:44PM +0200, Kalle Valo wrote:
Bjorn Helgaas bhelg...@google.com writes:
Well, as this series is small I thought it could quickly go thru your
tree. But since ipr had conflicts, there is no point routing all patches
altogether, so up to you guys. The wil6210
On Thu, Feb 13, 2014 at 12:57 PM, Jean Delvare jdelv...@suse.de wrote:
Hi Laszlo,
On Thu, 13 Feb 2014 12:27:28 +, Laszlo Papp wrote:
On Thu, Feb 13, 2014 at 11:33 AM, Lee Jones lee.jo...@linaro.org wrote:
Right, I've had enough. I'm removing your patch from the MFD tree.
I've asked
linus.wall...@linaro.org wrote:
The DBx500 and ABx500 should be getting their IRQs from the
device tree and nowhere else. Get rid of all the static assignments
everywhere, delete it from the driver, platform data and the
board files in one swift strike.
Lots of cross-dependencies in
m...@console-pimps.org writes:
On Wed, 12 Feb, at 09:15:03AM, Toshi Kani wrote:
Hi Matt,
Yes, I agree that the table size should be 0x38. However, ACPI spec
states that bit0 of status indicates if the boot image graphic is valid.
This bit is set to 0 (invalid) on the system. Can you
It's the current Arch Linux GCC package:
$ gcc -v
Using built-in specs.
COLLECT_GCC=/usr/bin/gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-unknown-linux-gnu/4.8.2/lto-wrapper
Target: x86_64-unknown-linux-gnu
Configured with: /build/gcc/src/gcc-4.8-20140206/configure
--prefix=/usr --libdir=/usr/lib
commit:
From 0cd8f9cc0654c06adde353c6532114c5f53a18e8 Mon Sep 17 00:00:00 2001
From: Mugunthan V N mugunthan...@ti.com
Date: Thu, 23 Jan 2014 00:03:12 +0530
Subject: [PATCH] drivers: net: cpsw: enable promiscuous mode support
Enable promiscuous mode support for CPSW.
Introduced a crash on an
In panel_probe() the backlight node is never found, correct this.
Signed-off-by: Heiko Schocher h...@denx.de
Cc: Anatolij Gustschin ag...@denx.de
Cc: Benoit Parrot bpar...@ti.com
Cc: Rob Clark robdcl...@gmail.com
Cc: David Airlie airl...@linux.ie
Cc: Grant Likely grant.lik...@linaro.org
Cc: Rob
On 02/13/2014 02:47 AM, Ulf Hansson wrote:
On 12 February 2014 22:21, Shuah Khan shuah...@samsung.com wrote:
Change cb710-mmc platform driver to register pm ops using dev_pm_ops instead
of legacy pm_ops. The existing legacy suspend/resume routines are identical
and simply clear IRQ mask in the
On 02/13/2014 02:31 AM, Matt Fleming wrote:
On Wed, 12 Feb, at 03:31:05PM, H. Peter Anvin wrote:
The real answer IMO ought to be that since arch/x86/boot/string.c is now
used separately from boot.h (eboot.c which includes efi-stub-helper.c
does *not* include boot.h) we may have to move those
On Wed, Feb 12, 2014 at 04:33:11PM -0800, Paul E. McKenney wrote:
Fair point! I wordsmithed it into the following. Seem reasonable?
Thanx, Paul
At system suspend_late, runtime PM has been disabled by the PM core
which means we can safely operate on these resources. Consequentially
we no longer have to wait until the noirq phase of the system suspend.
Cc: Alessandro Rubini rub...@unipv.it
Cc: Linus Walleij linus.wall...@linaro.org
Cc:
For !CONFIG_PM_RUNTIME, the device were never put back into active
state while resuming.
For CONFIG_PM_RUNTIME, we blindly trusted the device to be inactive
while we were about to handle it at suspend late, which is just too
optimistic.
Even if the driver uses pm_runtime_put_sync() after each
Since the runtime PM state is expected to be active according to the
amba bus, we must align our behaviour while probing to it.
Moreover, this is needed to be able to have the driver fully functional
without depending on CONFIG_RUNTIME_PM.
Since the device is active while a successful probe has
We should never be busy performing transfers at suspend late, thus
there are no reason to check for it.
Cc: Alessandro Rubini rub...@unipv.it
Cc: Linus Walleij linus.wall...@linaro.org
Cc: Wolfram Sang w...@the-dreams.de
Signed-off-by: Ulf Hansson ulf.hans...@linaro.org
---
Changes in v2:
On Wed, 12 Feb 2014, Vince Weaver wrote:
On Tue, 11 Feb 2014, Peter Zijlstra wrote:
I'll see if I can run through the reproduction case by hand.
I've come up with an even simpler test case with all of the extraneous
settings removed. Included below.
It is triggered in this case
The amba bus are responsible for pm_runtime_enable|disable, remove the
redundant pm_runtime_disable at driver removal.
Cc: Alessandro Rubini rub...@unipv.it
Cc: Linus Walleij linus.wall...@linaro.org
Cc: Wolfram Sang w...@the-dreams.de
Signed-off-by: Ulf Hansson ulf.hans...@linaro.org
---
Use devm_* functions to simplify code and error handling.
Cc: Alessandro Rubini rub...@unipv.it
Cc: Linus Walleij linus.wall...@linaro.org
Cc: Wolfram Sang w...@the-dreams.de
Signed-off-by: Ulf Hansson ulf.hans...@linaro.org
---
Changes in v2:
Rebased on top of latest i2c-nomadik branch.
On 10 February 2014 11:14, Ulf Hansson ulf.hans...@linaro.org wrote:
On 5 February 2014 15:34, Linus Walleij linus.wall...@linaro.org wrote:
On Tue, Feb 4, 2014 at 4:58 PM, Ulf Hansson ulf.hans...@linaro.org wrote:
Since the device is active while a successful probe has been completed,
the
On Thursday 13 February 2014 07:17 PM, Heiko Schocher wrote:
commit:
From 0cd8f9cc0654c06adde353c6532114c5f53a18e8 Mon Sep 17 00:00:00 2001
From: Mugunthan V N mugunthan...@ti.com
Date: Thu, 23 Jan 2014 00:03:12 +0530
Subject: [PATCH] drivers: net: cpsw: enable promiscuous mode support
The new functions are special cases for pci_enable_msi_range() and
pci_enable_msix_range() when a particular number of MSI or MSI-X
is needed.
By contrast with pci_enable_msi_range() and pci_enable_msix_range()
functions, pci_enable_msi_exact() and pci_enable_msix_exact()
return zero in case of
On Wed 12-02-14 17:26:46, Hugh Dickins wrote:
Commit 0eef615665ed (memcg: fix css reference leak and endless loop in
mem_cgroup_iter) got the interaction with the commit a few before it
d8ad30559715 (mm/memcg: iteration skip memcgs not yet fully initialized)
slightly wrong, and we didn't
On Tue, 2014-02-11 at 21:09 +0100, Richard Cochran wrote:
-#define EXT_EVENT 1
Regarding this EXT_EVENT thing ...
@@ -430,12 +419,12 @@ static int ptp_dp83640_enable(struct ptp_clock_info
*ptp,
switch (rq-type) {
case PTP_CLK_REQ_EXTTS:
index =
On Tue, 2014-02-11 at 21:19 +0100, Richard Cochran wrote:
+- dp83640,slave: If present, this phy will be slave to another dp83640
+ on the same mdio bus.
Wouldn't it be more natural to have one dp83640,master property
rather than multiple slave properties?
I wanted to keep the common
On Fri, Feb 07, 2014 at 11:23:57AM -0500, Steven Rostedt wrote:
A while back ago, Wolfgang (and others) have asked about the ability to
add a trace event that recorder no data other than the fact that the
trace event was hit.
I've been reluctant to do so, but I noticed that one already
On Tue, Feb 11, 2014 at 02:22:43PM +0530, Viresh Kumar wrote:
On 28 January 2014 18:53, Frederic Weisbecker fweis...@gmail.com wrote:
No, when a single task is running on a full dynticks CPU, the tick is
supposed to run
every seconds. I'm actually suprised it doesn't happen in your traces,
Hi, testing 3.14-rc2 I noticed I could not adjust the brightness of the
screen any longer. This problem is already present in 3.14-rc1. 3.13 works fine.
My hardware is a netbook with intel atom and a 945GM graphics card.
I bisected the problem down to the next commit:
Periodic output triggers 0 and 1 of the dp83640 has a programmable
duty-cycle which is controlled by the Pulsewidth2 field of the trigger
data register. This field is not documented in the datasheet, but it
is described in the PHYTER Software Development Guide section
3.1.4.1. Failing to set the
The driver is currently limited to a single periodic output. This patch makes
the number of peridodic output dynamic by dropping the gpio_tab module
parameter and adding calibrate_pin, perout_pins, and extts_pins parameters.
Signed-off-by: Stefan Sørensen stefan.soren...@spectralink.com
---
This patch series add DT configuration to the DP83640 PHY driver and makes
the configuration of periodic output pins dynamic.
Changes since v2:
- Add patch to properly configure perout triggers 0+1
- Keep extts and perout numbers separate
- Shorten pr_err lines
Changes since v1:
- Add
This patch adds configuration of the periodic output and external timestamp
pins available on the dp83640 family of PHYs. It also configures the
master/slave relationship in a group of PHYs on the same MDIO bus and the pins
used for clock calibration in the group.
The configuration is retrieved
This patch adds configuration of the periodic output and external timestamp
pins available on the dp83640 family of PHYs. It also configures the
master/slave relationship in a group of PHYs on the same MDIO bus and the pins
used for clock calibration in the group.
The configuration is retrieved
This patch series add DT configuration to the DP83640 PHY driver and makes
the configuration of periodic output pins dynamic.
Changes since v2:
- Add patch to properly configure perout triggers 0+1
- Keep extts and perout numbers separate
- Shorten pr_err lines
Changes since v1:
- Add
Periodic output triggers 0 and 1 of the dp83640 has a programmable
duty-cycle which is controlled by the Pulsewidth2 field of the trigger
data register. This field is not documented in the datasheet, but it
is described in the PHYTER Software Development Guide section
3.1.4.1. Failing to set the
The driver is currently limited to a single periodic output. This patch makes
the number of peridodic output dynamic by dropping the gpio_tab module
parameter and adding calibrate_pin, perout_pins, and extts_pins parameters.
Signed-off-by: Stefan Sørensen stefan.soren...@spectralink.com
---
From: Ivan T. Ivanov iiva...@mm-sol.com
SPI transfer lenght should be a power-of-two multiple
of eight bits.
Signed-off-by: Ivan T. Ivanov iiva...@mm-sol.com
---
drivers/spi/spi.c | 17 +
1 file changed, 17 insertions(+)
diff --git a/drivers/spi/spi.c b/drivers/spi/spi.c
2014-02-13 2:40 GMT+01:00 Andy Lutomirski l...@amacapital.net:
This is a strawman proposal to simplify the idle implementation, eliminate
a race
Please describe the race in question.
Benefits over current code:
- ttwu_queue_remote doesn't use an IPI unless needed
- The diffstat should
On Wed 12-02-14 17:29:09, Hugh Dickins wrote:
Commit d8ad30559715 (mm/memcg: iteration skip memcgs not yet fully
initialized) is not bad, but Greg Thelen asks Are barriers needed?
Yes, I'm afraid so: this makes it a little heavier than the original,
but there's no point in guaranteeing that
Hi,
On 13.02.2014 10:14, Krzysztof Kozlowski wrote:
Add bindings documentation for S2MPS14 device to the s2mps11 driver.
Signed-off-by: Krzysztof Kozlowski k.kozlow...@samsung.com
Cc: Mark Brown broo...@kernel.org
Cc: Liam Girdwood lgirdw...@gmail.com
Cc: Tomasz Figa t.f...@samsung.com
Cc:
On Thu, 2014-02-13 at 11:17 +, Matt Fleming wrote:
On Wed, 05 Feb, at 05:03:54PM, Leif Lindholm wrote:
From: Mark Salter msal...@redhat.com
ARM and ARM64 architectures use the device tree to pass UEFI parameters
from stub to kernel. These parameters are things known to the stub but
On Wed, Feb 12, 2014 at 05:40:12PM -0800, Andy Lutomirski wrote:
This is a strawman proposal to simplify the idle implementation, eliminate
a race
Benefits over current code:
- ttwu_queue_remote doesn't use an IPI unless needed
- The diffstat should speak for itself :)
- Less racy.
-Original Message-
From: Jason Wang [mailto:jasow...@redhat.com]
Sent: Wednesday, February 12, 2014 10:52 PM
To: Haiyang Zhang; da...@davemloft.net; net...@vger.kernel.org
Cc: KY Srinivasan; o...@aepfle.de; linux-kernel@vger.kernel.org; driverdev-
de...@linuxdriverproject.org
On Wednesday 12 February 2014, Randy Dunlap wrote:
On 02/12/2014 11:08 AM, Gene Heskett wrote:
Greetings, not making any progress on newer kernel builds yet.
So I unpacked 3.13.2 this morning and copied its
arch/x86/i386_defconfig to .config.
Ran make oldconfig, then 3 or 4 sessions of
- Original Message -
From: Steven Rostedt rost...@goodmis.org
To: Ingo Molnar mi...@kernel.org
Cc: Mathieu Desnoyers mathieu.desnoy...@efficios.com,
linux-kernel@vger.kernel.org, Ingo Molnar
mi...@redhat.com, Thomas Gleixner t...@linutronix.de, Rusty Russell
ru...@rustcorp.com.au,
Hi David,
On Wed, Feb 12, 2014 at 5:13 AM, David Herrmann dh.herrm...@gmail.com wrote:
Hi
On Wed, Feb 5, 2014 at 10:33 PM, Benjamin Tissoires
benjamin.tissoi...@redhat.com wrote:
Hi guys,
well, here comes the promised v2 of the ll_transport cleanup.
As I said, I removed patches which
On Wed, Feb 12, 2014 at 5:30 AM, David Herrmann dh.herrm...@gmail.com wrote:
Hi
On Mon, Feb 10, 2014 at 6:58 PM, Benjamin Tissoires
benjamin.tissoi...@redhat.com wrote:
Having our own .request() implementation does not give anything,
so use the generic binding.
Signed-off-by: Benjamin
On Wed, Feb 12, 2014 at 5:49 AM, David Herrmann dh.herrm...@gmail.com wrote:
Hi
On Mon, Feb 10, 2014 at 6:58 PM, Benjamin Tissoires
benjamin.tissoi...@redhat.com wrote:
Remove hid_output_raw_report() call as it is not a ll_driver callbacj,
and switch to the hid_hw_* implementation. USB-HID
On 02/13/2014 04:45 AM, Fengguang Wu wrote:
Greetings,
I find that when running
qemu-system-x86_64 -cpu qemu64,+smep,+smap
Some kernels will 100% produce this error, where the error code
-13,-14 are -EACCES and -EFAULT:
Any ideas?
I notice this is a non-SMAP kernel:
#
Hello
Can you send us your full Product catalog, we want to buy and ship to Doha,
Qatar.
waiting
for your response
Jermaine Shannon
--
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
On Wed, Feb 12, 2014 at 5:25 AM, David Herrmann dh.herrm...@gmail.com wrote:
Hi
On Mon, Feb 10, 2014 at 6:58 PM, Benjamin Tissoires
benjamin.tissoi...@redhat.com wrote:
.request() can be emulated through .raw_request()
we can implement this emulation in hid-core, and make .request
not
On Thu, 13 Feb 2014, Luis Ortega luior...@upv.es wrote:
Hi, testing 3.14-rc2 I noticed I could not adjust the brightness of the
screen any longer. This problem is already present in 3.14-rc1. 3.13 works
fine.
My hardware is a netbook with intel atom and a 945GM graphics card.
I bisected
I dare say either your bisect went sour or you don't have 945GM. Please
verify your steps.
Well, what can I say? I was careful when testing and the last kernel I compiled
shows the problem. I can replay the bisection if needed but if I have to start
all over again it's gonna take some time. I'm
On Thu, 13 Feb 2014 15:26:42 +0100
Frederic Weisbecker fweis...@gmail.com wrote:
Is this worth doing?
It sounds worth yeah. I've run into this situation multiple times where I had
Is it?
to pass 0 instead of nothing on a tracepoint.
What tracepoints?
The problem I have with a tracepoint
On Wed 12-02-14 15:03:31, Hugh Dickins wrote:
From: Filipe Brandenburger filbran...@google.com
Sometimes the cleanup after memcg hierarchy testing gets stuck in
mem_cgroup_reparent_charges(), unable to bring non-kmem usage down to 0.
There may turn out to be several causes, but a major
On Thu, 13 Feb 2014 15:10:14 + (UTC)
Mathieu Desnoyers mathieu.desnoy...@efficios.com wrote:
- Original Message -
From: Steven Rostedt rost...@goodmis.org
To: Ingo Molnar mi...@kernel.org
Cc: Mathieu Desnoyers mathieu.desnoy...@efficios.com,
linux-kernel@vger.kernel.org,
2014-01-08 22:36 GMT+01:00 Pali Rohár pali.ro...@gmail.com:
On Monday 30 December 2013 15:52:51 Sebastian Reichel wrote:
+MODULE_DESCRIPTION(Bluetooth h4 driver with nokia
extensions); +MODULE_LICENSE(GPL);
+MODULE_AUTHOR(Ville Tervo);
+MODULE_FIRMWARE(FW_NAME_TI1271_PRELE);
Hello,
On Thu, Feb 13, 2014 at 04:27:45PM +0100, Michal Hocko wrote:
Further testing showed that an ordered workqueue for cgroup_destroy_wq
is not always good enough: percpu_ref_kill_and_confirm's call_rcu_sched
stage on the way can mess up the order before reaching the workqueue.
This
From: Heiko Stuebner heiko.stueb...@bqreaders.com
Commit 934624d6e9f0 (regulator: gpio-regulator: do not open-code counting
and access of dt array elements) forgot to convert the recently added
gpios-states property using the same pattern.
Convert this instance to use the of-helpers too,
On Thursday 13 February 2014, Gene Heskett wrote:
On Wednesday 12 February 2014, Randy Dunlap wrote:
On 02/12/2014 11:08 AM, Gene Heskett wrote:
Greetings, not making any progress on newer kernel builds yet.
So I unpacked 3.13.2 this morning and copied its
arch/x86/i386_defconfig to .config.
rostedt wrote:
[...]
Oh! You are saying that if the kernel only *supports* signed modules,
and you load a module that is not signed, it will taint the kernel?
Yes: this is the default for several distros.
- FChE
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the
On Wed, Feb 12, 2014 at 5:35 AM, David Herrmann dh.herrm...@gmail.com wrote:
Hi
On Mon, Feb 10, 2014 at 6:58 PM, Benjamin Tissoires
benjamin.tissoi...@redhat.com wrote:
hid_output_raw_report() is not a ll_driver callback and should not be used.
To keep the same code path than before, we are
- Original Message -
From: Steven Rostedt rost...@goodmis.org
To: Mathieu Desnoyers mathieu.desnoy...@efficios.com
Cc: Ingo Molnar mi...@kernel.org, linux-kernel@vger.kernel.org, Ingo
Molnar mi...@redhat.com, Thomas
Gleixner t...@linutronix.de, Rusty Russell ru...@rustcorp.com.au,
On Thu, 13 Feb 2014 10:36:35 -0500
f...@redhat.com (Frank Ch. Eigler) wrote:
rostedt wrote:
[...]
Oh! You are saying that if the kernel only *supports* signed modules,
and you load a module that is not signed, it will taint the kernel?
Yes: this is the default for several distros.
On Wed, Feb 12, 2014 at 5:47 AM, David Herrmann dh.herrm...@gmail.com wrote:
Hi
On Mon, Feb 10, 2014 at 6:58 PM, Benjamin Tissoires
benjamin.tissoi...@redhat.com wrote:
We can not directly change the underlying struct hid_ll_driver here
as we did for hdev-hid_output_raw_report.
So allocate
On 02/13/2014 06:55 AM, H. Peter Anvin wrote:
On 02/13/2014 04:45 AM, Fengguang Wu wrote:
Greetings,
I find that when running
qemu-system-x86_64 -cpu qemu64,+smep,+smap
Some kernels will 100% produce this error, where the error code
-13,-14 are -EACCES and -EFAULT:
Any ideas?
On 03/02/14 07:56, Suresh Siddha wrote:
Here is the second patch, which should fix the issue reported in this
thread. Maarten, Nate, George, please give this patch a try as is and
see if it helps address the issue you ran into.
I can confirm that your patch fixes the bug I reported (core dump
Preemption state on enter in finish_task_switch() is different
in cases of context_switch() and schedule_tail().
In the first case we have it twice disabled: at the start of
schedule() and during spin locking. In the second it is only
once: the value which was set in init_task_preempt_count().
On 02/13/2014 06:55 AM, H. Peter Anvin wrote:
On 02/13/2014 04:45 AM, Fengguang Wu wrote:
Greetings,
I find that when running
qemu-system-x86_64 -cpu qemu64,+smep,+smap
Some kernels will 100% produce this error, where the error code
-13,-14 are -EACCES and -EFAULT:
Any ideas?
On Thu, 2014-02-13 at 08:19 +0100, Michal Simek wrote:
On 02/13/2014 01:31 AM, Joe Perches wrote:
On Wed, 2014-02-12 at 16:55 +0100, Michal Simek wrote:
Hi again Michal.
+ netdev_warn(lp-ndev,
+ Could not find clock ethernet controller property.);
here too.
Hi Linus,
Second round of updates and fixes for 3.14-rc2. Most of this stuff has
been queued up for a while. The notable exception is the blk-mq changes,
which are naturally a bit more in flux still.
The pull request contains:
- Two bug fixes for the new immutable vecs, causing crashes with
If we're going to be adding a new rename inode op, can we make it take a flag
to white out the source for union type things? This would mean that
rename-and-white-out can be done atomically.
David
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message
Commit-ID: f27d7759ad1ff48673831e598d6df4c76b2bcd06
Gitweb: http://git.kernel.org/tip/f27d7759ad1ff48673831e598d6df4c76b2bcd06
Author: H. Peter Anvin h...@linux.intel.com
AuthorDate: Thu, 13 Feb 2014 07:46:04 -0800
Committer: H. Peter Anvin h...@linux.intel.com
CommitDate: Thu, 13 Feb
Commit-ID: 03bbd596ac04fef47ce93a730b8f086d797c3021
Gitweb: http://git.kernel.org/tip/03bbd596ac04fef47ce93a730b8f086d797c3021
Author: H. Peter Anvin h...@linux.intel.com
AuthorDate: Thu, 13 Feb 2014 07:34:30 -0800
Committer: H. Peter Anvin h...@linux.intel.com
CommitDate: Thu, 13 Feb
Hi Greg,
On 11/02/14 00:13, Greg Kroah-Hartman wrote:
On Mon, Feb 10, 2014 at 06:09:58PM +, Sudeep Holla wrote:
On 07/02/14 19:29, Greg Kroah-Hartman wrote:
On Fri, Feb 07, 2014 at 04:49:16PM +, Sudeep Holla wrote:
From: Sudeep Holla sudeep.ho...@arm.com
This patch adds initial
On Thu, Feb 13, 2014 at 6:42 PM, Mel Gorman mgor...@suse.de wrote:
According to the swapon documentation
Swap pages are allocated from areas in priority order,
highest priority first. For areas with different priorities, a
higher-priority area is exhausted
On Thu, Feb 13, 2014 at 07:51:56PM +0400, Kirill Tkhai wrote:
For archs without __ARCH_WANT_UNLOCKED_CTXSW set this means
that all newly created tasks execute finish_arch_post_lock_switch()
and post_schedule() with preemption enabled.
That's IA64 and MIPS; do they have a 'good' reason to use
To fix:
arch/sparc/kernel/leon_pci_grpci2.c: In function 'grpci2_of_probe':
arch/sparc/kernel/leon_pci_grpci2.c:720:2: error: implicit declaration of
function 'kzalloc' [-Werror=implicit-function-declaration]
arch/sparc/kernel/leon_pci_grpci2.c:720:20: error: assignment makes pointer
from
Alexander Gordeev agord...@redhat.com writes:
Signed-off-by: Alexander Gordeev agord...@redhat.com
Thanks, all three patches applied to my ath.git tree.
--
Kalle Valo
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
Rashika Kheria rashika.khe...@gmail.com wrote:
Remove unused function in afs/write.c.
This eliminates the following warning in afs/write.c:
fs/afs/write.c:749:5: warning: no previous prototype for ‘afs_page_mkwrite’
[-Wmissing-prototypes]
Signed-off-by: Rashika Kheria
On 02/12/2014 09:41 PM, Weijie Yang wrote:
We abort direct reclaim if find the zone is ready for compaction.
Sometimes the zone is just a promoted highmem zone to force scan
pinning highmem, which is not the intended zone the caller want to
alloc page from. In this situation, setting
On Wed 12-02-14 16:28:36, Roman Gushchin wrote:
Hi, Michal!
Sorry for a long reply.
At Wed, 29 Jan 2014 19:22:59 +0100,
Michal Hocko wrote:
As you can remember, I've proposed to introduce low limits about a year
ago.
We had a small discussion at that time:
On 02/13/2014 04:27 AM, Laszlo Papp wrote:
On Thu, Feb 13, 2014 at 11:33 AM, Lee Jones lee.jo...@linaro.org wrote:
-static int max6650_probe(struct i2c_client *client,
-const struct i2c_device_id *id);
-static int max6650_init_client(struct i2c_client *client);
-static int
Commit-ID: af0c23df96fbc16089e8eda4b94b7d69b845f81e
Gitweb: http://git.kernel.org/tip/af0c23df96fbc16089e8eda4b94b7d69b845f81e
Author: H. Peter Anvin h...@linux.intel.com
AuthorDate: Thu, 13 Feb 2014 07:46:04 -0800
Committer: H. Peter Anvin h...@linux.intel.com
CommitDate: Thu, 13 Feb
From: Ivan T. Ivanov iiva...@mm-sol.com
Hi,
Following two patches are adding initial support for SPI controller
available in Qualcomm SoC's.
Controller initialization is based on spi_qsd driver available in
CAF repository.
Controller supports SPI_CPOL | SPI_CPHA | SPI_CS_HIGH | SPI_LOOP
From: Ivan T. Ivanov iiva...@mm-sol.com
The Qualcomm Universal Peripheral (QUP) core is an
AHB slave that provides a common data path (an output
FIFO and an input FIFO) for serial peripheral interface
(SPI) mini-core.
Signed-off-by: Ivan T. Ivanov iiva...@mm-sol.com
---
On Thu, Feb 13, 2014 at 01:35:41PM +0100, Tomasz Figa wrote:
On 13.02.2014 13:07, Arend van Spriel wrote:
On 02/13/2014 10:13 AM, Tomasz Figa wrote:
The BCM43xx WLAN chips I used to work always have been controlled by a
simple power enable GPIO of the chip itself. Has this changed in newer
From: Ivan T. Ivanov iiva...@mm-sol.com
Qualcomm Universal Peripheral (QUP) core is an AHB slave that
provides a common data path (an output FIFO and an input FIFO)
for serial peripheral interface (SPI) mini-core. SPI in master
mode supports up to 50MHz, up to four chip selects, programmable
data
On Thu, Feb 13, 2014 at 03:54:14PM +, David Howells wrote:
If we're going to be adding a new rename inode op, can we make it take a flag
to white out the source for union type things? This would mean that
rename-and-white-out can be done atomically.
That is an option, yes.
Regarding
Hi,
Your patch does solve the file consumption problem on my test case.
We still open and do the ELF read 5 times.
Now, if on top of your patch, we also add the following, we save one
open().
diff --git a/tools/perf/util/dso.c b/tools/perf/util/dso.c
index 4045d08..87a0ecb 100644
---
Dear Sebastian Hesselbarth,
Thanks again for working on this! I have boot tested this successfully
on an Armada XP platform, and it seems to behave normally, the debugfs
pinctrl contents make sense.
I have a few comments below, though.
On Wed, 12 Feb 2014 16:59:23 +0100, Sebastian Hesselbarth
On 02/13/2014 03:58 AM, Jean Delvare wrote:
Hi Lee,
On Thu, 13 Feb 2014 11:16:07 +, Lee Jones wrote:
On Thu, 13 Feb 2014, Jean Delvare wrote:
Guenter just did:
http://lists.lm-sensors.org/pipermail/lm-sensors/2014-February/041224.html
Nice, FWIW:
Acked-by: Lee Jones
On 02/13/2014 02:31 AM, Paul Bolle wrote:
On Thu, 2014-02-13 at 10:57 +0100, Paul Bolle wrote:
This issue is still present in v3.14-rc2. Guenter's suggestion is the
easiest way out. Should I submit a trivial patch that just removes the
dead code depending on never defined CONFIG_ADT7310 and
On Tue, Feb 11, 2014 at 03:12:59PM -0500, Waiman Long wrote:
Using the same locktest program to repetitively take a single rwlock with
programmable number of threads and count their execution times. Each
thread takes the lock 5M times on a 4-socket 40-core Westmere-EX
system. I bound all the
On 02/13/2014 01:49 AM, Thierry Reding wrote:
On Thu, Feb 13, 2014 at 09:28:52AM +0100, Marc Dietrich wrote:
Am Mittwoch, 12. Februar 2014, 12:20:29 schrieb Stephen Warren:
On 02/10/2014 05:44 PM, Stefan Agner wrote:
When booting secondary CPU(s) which are not yet powergated, a wrong
check
On 02/13/2014 04:01 AM, Tomasz Figa wrote:
Hi Alexandre,
On 07.02.2014 05:35, Alexandre Courbot wrote:
Some firmwares do not put the CPU into idle mode themselves, but still
need to be informed that the CPU is about to enter idle mode before this
happens. Add a prepare_idle() operation to
901 - 1000 of 1502 matches
Mail list logo