vdso_standalone_test_x86 needs -lgcc_s to build succesfully on 32bit.
Signed-off-by: Peter Foley
---
Documentation/vDSO/Makefile | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/vDSO/Makefile b/Documentation/vDSO/Makefile
index 2b99e57..5e5ad9f 100644
---
On Wed, 8 Oct 2014 15:26:20 -0400
Jeff Layton wrote:
> The following changes since commit 66f09ca717e7905e0eebe000b86e27d0274b95ac:
>
> nfs: do not start the callback thread until we set rqstp->rq_task
> (2014-09-02 17:53:30 -0400)
>
> are available in the git repository at:
>
>
From: Hayes Wang
Date: Tue, 7 Oct 2014 13:36:30 +0800
> Use mutex to avoid that the serial hw settings would be interrupted
> by other settings. Although there is no problem now, it makes the
> driver more safe.
>
> Signed-off-by: Hayes Wang
I think a much simpler fix is to take rtnl_lock()
On Wed, Oct 8, 2014 at 3:16 PM, Andy Lutomirski wrote:
> It should build and work on 32-bit.
>
> Except that the makefile is totally bogus. vdso_standalone_test isn't
> a hostprog at all. It's a target prog. But kbuild doesn't understand
> that, so I have no idea what, if anything, that
>
> This sort of test is generally better where the
> individual tests are written on separate lines like:
>
> if ((data[idx] != pktdata[i]) ||
> (data[idx+1] != pktdata[i+1])) {
>
Thanks for all the suggestions, Joe. I'll upload a revised patch
On Wed, Oct 08, 2014 at 11:57:58AM -0400, Matthew Wilcox wrote:
> On Wed, Oct 08, 2014 at 06:21:24PM +0300, Kirill A. Shutemov wrote:
> > On Wed, Oct 08, 2014 at 09:25:24AM -0400, Matthew Wilcox wrote:
> > > From: Matthew Wilcox
> > >
> > > DAX wants to use the 'special' bit to mark PMD entries
On 10/08, Oleg Nesterov wrote:
>
> Another problem is that finish_task_switch() itself runs with preempt
> enabled after finish_lock_switch(). If nothing else this means that
> ->sched_in() notifier can't trust its "cpu" arg.
OOPS, this obviously can't happen, ->preempt_notifiers must be empty.
From: Rik van Riel
On systems with complex NUMA topologies, the node scoring is adjusted
to allow workloads to converge on nodes that are near each other.
The way a task group's preferred nid is determined needs to be adjusted,
in order for the preferred_nid to be consistent with group_weight
From: Rik van Riel
In order to do task placement on systems with complex NUMA topologies,
it is necessary to count the faults on nodes nearby the node that is
being examined for a potential move.
In case of a system with a backplane interconnect, we are dealing with
groups of NUMA nodes; each
From: Rik van Riel
Preparatory patch for adding NUMA placement on systems with
complex NUMA topology. Also fix a potential divide by zero
in group_weight()
Signed-off-by: Rik van Riel
---
include/linux/topology.h | 1 +
kernel/sched/core.c | 2 +-
kernel/sched/fair.c | 57
This patch set integrates two algorithms I have previously tested,
one for glueless mesh NUMA topologies, where NUMA nodes communicate
with far-away nodes through intermediary nodes, and backplane
topologies, where communication with far-away NUMA nodes happens
through backplane controllers (which
From: Rik van Riel
Smaller NUMA systems tend to have all NUMA nodes directly connected
to each other. This includes the degenerate case of a system with just
one node, ie. a non-NUMA system.
Larger systems can have two kinds of NUMA topology, which affects how
tasks and memory should be placed
From: Rik van Riel
In order to more efficiently figure out where to place workloads
that span multiple NUMA nodes, it makes sense to estimate how
many hops away nodes are from each other.
Also add some comments to sched_init_numa.
Signed-off-by: Rik van Riel
Suggested-by: Peter Zijlstra
---
Commit d127e9c5c5bc1ee22a7b1fe804397cddd132f756 ("ARM: tegra: make tegra_resume
can work with current and later chips") removed tegra_get_soc_id macro leaving
used cpu register unassigned and as result causing execution of unintended code
on tegra20. Fix it by re-adding macro.
Fixes: d127e9c
On Wed, Oct 8, 2014 at 12:23 PM, Eric W. Biederman
wrote:
> Andy Lutomirski writes:
>
>> On Wed, Oct 8, 2014 at 4:08 AM, Andrew Vagin wrote:
>>> On Tue, Oct 07, 2014 at 01:45:22PM -0700, Eric W. Biederman wrote:
Andrey Vagin writes:
> From: Andrey Vagin
>
> Currently
On Sunday 05 October 2014 23:59:12 Beniamino Galvani wrote:
>
> this patchset introduces support for Amlogic Meson8, which is a family
> of quad-core Cortex-A9 SoCs used in tablets and set-top boxes.
>
> Changes since v1:
> - reused the existing DT machine definition and renamed it to be more
>
On Wed, Oct 08, 2014 at 08:09:59AM -0700, H. Peter Anvin wrote:
> On 10/01/2014 06:52 AM, Vivek Goyal wrote:
> >
> > Hi Peter,
> >
> > I think there is some confusion. I will try to clarify.
> >
> > If we have 32bit signed overflow, we will not have a functional kernel.
> > And that's the
Commit f95499c3030f ("n_tty: Don't wait for buffer work in read() loop")
introduces a race window where a pty master can be signalled that the pty
slave was closed before all the data that the slave wrote is delivered.
Commit f8747d4a466a ("tty: Fix pty master read() after slave closes") fixed the
The following changes since commit 66f09ca717e7905e0eebe000b86e27d0274b95ac:
nfs: do not start the callback thread until we set rqstp->rq_task (2014-09-02
17:53:30 -0400)
are available in the git repository at:
git://git.samba.org/jlayton/linux.git linux-next
for you to fetch changes up
Hi,
Please consider pulling the following changes,
Steve.
-
The following changes since commit 37504a3be90b69438426d74ccf467a9fe192932b:
Merge tag 'gfs2-fixes' of
Andy Lutomirski writes:
> On Wed, Oct 8, 2014 at 4:08 AM, Andrew Vagin wrote:
>> On Tue, Oct 07, 2014 at 01:45:22PM -0700, Eric W. Biederman wrote:
>>> Andrey Vagin writes:
>>>
>>> > From: Andrey Vagin
>>> >
>>> > Currently when we create a new container with a separate root,
>>> > we need to
Georgi,
On Tue, Sep 2, 2014 at 5:40 PM, Georgi Djakov wrote:
> Enable support for the two SD host controllers on the APQ8084 platform
> by adding the required nodes to the DT files.
> On the IFC6540 board, the first controller is connected to the onboard
> eMMC and the second is connected to a
On Wed, Oct 8, 2014 at 11:52 AM, Josh Boyer wrote:
> I'm seeing the following build failure on a 32-bit x86 build in Fedora
> based on Linux v3.17-2860-gef0625b70dac:
>
> Documentation/vDSO/vdso_standalone_test_x86.o: In function `to_base10':
> vdso_standalone_test_x86.c:(.text+0xcc): undefined
Hey everyone,
I've run into a some frustrating behavior from the khugepaged thread,
that I'm hoping to get sorted out. It appears that if you pin
khugepaged to a cpuset (i.e. node 0), and it begins scanning/collapsing
pages for a process on a cpuset that doesn't have any memory nodes in
common
On Wed, Oct 08, 2014 at 02:01:47PM -0500, Felipe Balbi wrote:
> Hi,
>
> On Wed, Oct 08, 2014 at 10:54:10PM +0400, Dmitry Osipenko wrote:
> > Commit d127e9c5c5bc1ee22a7b1fe804397cddd132f756 ("ARM: tegra: make
> > tegra_resume
> > can work with current and later chips") removed tegra_get_soc_id
On Wed, 8 Oct 2014, Peter Zijlstra wrote:
> On Wed, Sep 24, 2014 at 03:04:15PM +0100, Matt Fleming wrote:
> > + preempt_disable();
< SNIP lng code >
> > + preempt_enable();
>
> Why is all that under preempt_disable()?
To make life harder for people who care about latencies and
Hi,
On Wed, Oct 08, 2014 at 10:54:10PM +0400, Dmitry Osipenko wrote:
> Commit d127e9c5c5bc1ee22a7b1fe804397cddd132f756 ("ARM: tegra: make
> tegra_resume
> can work with current and later chips") removed tegra_get_soc_id macro leaving
> used cpu register unassigned and as result causing execution
Commit d127e9c5c5bc1ee22a7b1fe804397cddd132f756 ("ARM: tegra: make tegra_resume
can work with current and later chips") removed tegra_get_soc_id macro leaving
used cpu register unassigned and as result causing execution of unintended code
on tegra20. Fix it by re-adding macro.
Signed-off-by:
I'm seeing the following build failure on a 32-bit x86 build in Fedora
based on Linux v3.17-2860-gef0625b70dac:
Documentation/vDSO/vdso_standalone_test_x86.o: In function `to_base10':
vdso_standalone_test_x86.c:(.text+0xcc): undefined reference to `__umoddi3'
Am Montag 06 Oktober 2014, 22:28:31 schrieb Guenter Roeck:
> Register with kernel poweroff handler instead of setting pm_power_off
> directly. Register with default priority value of 128 since we don't know
> any better.
I just tested this change and it seems to break power off. What the driver
On 14-10-08 11:12 AM, Arnd Bergmann wrote:
On Wednesday 08 October 2014 09:27:08 Scott Branden wrote:
On 14-10-08 06:28 AM, Arnd Bergmann wrote:
On Wednesday 08 October 2014 05:27:24 Scott Branden wrote:
I don't think you need per-board config options. The main option
above should be enough.
On Wed, 2014-10-08 at 18:46 +0200, leroy christophe wrote:
> Le 07/10/2014 02:19, Scott Wood a écrit :
> > On Sat, 2014-10-04 at 12:15 +0200, christophe leroy wrote:
> >> Le 03/10/2014 22:24, Scott Wood a écrit :
> >>> On Fri, 2014-10-03 at 22:15 +0200, christophe leroy wrote:
> Le 03/10/2014
task_preempt_count() is pointless if preemption counter is per-cpu,
currently this is x86 only. It is only valid if the task is not
running, and even in this case the only info it can provide is the
state of PREEMPT_ACTIVE bit.
Change its single caller to check p->on_rq instead, this should be
finish_task_switch() enables preemption, so post_schedule(rq) can be
called on the wrong (and even dead) CPU. Afaics, nothing really bad
can happen, but in this case we can wrongly clear rq->post_schedule
on that CPU. And this simply looks wrong in any case.
Another problem is that
No need to store netlbl_unlabel_genl_init result and test it before returning.
Signed-off-by: Fabian Frederick
---
net/netlabel/netlabel_user.c | 6 +-
1 file changed, 1 insertion(+), 5 deletions(-)
diff --git a/net/netlabel/netlabel_user.c b/net/netlabel/netlabel_user.c
index
On 10/08, Peter Zijlstra wrote:
>
> On Tue, Oct 07, 2014 at 09:50:46PM +0200, Oleg Nesterov wrote:
> > And note that another caller of task_preempt_count(), set_cpu(), is
> > fine but it doesn't really need this helper.
> >
> > And afaics we do not need ->saved_preempt_count at all, the trivial
>
Wrapping two too long lines in two files of the imx-drm driver.
Signed-off-by: Rene Kolarik
---
drivers/staging/imx-drm/imx-drm-core.c | 3 ++-
drivers/staging/imx-drm/imx-tve.c | 3 ++-
2 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/imx-drm/imx-drm-core.c
On Wed, Oct 08, 2014 at 12:04:41PM +0530, Pramod Gurav wrote:
> This change switches to using devm_* managed resources APIs to
> request the resources in probe to simplify probe error path and
> module unloading.
>
> Cc: Dmitry Torokhov
> Cc: linux-in...@vger.kernel.org
> Signed-off-by: Pramod
On 10/8/2014 11:21 AM, Mark Brown wrote:
On Wed, Oct 08, 2014 at 09:14:35AM -0700, Ray Jui wrote:
Thanks for the reply. It looks like you are also the maintainer of spidev.
In this case, could you please help to confirm that you expect spidev to use
separate buffers for TX and RX? If so, I
Em Wed, 08 Oct 2014 10:13:39 -0700
Randy Dunlap escreveu:
> On 10/07/14 23:49, Stephen Rothwell wrote:
> > Hi all,
> >
> > Please do not add any material intended for v3.19 to you linux-next
> > included trees until after v3.18-rc1 has been released.
> >
> > Changes since 20141007:
> >
>
> I
On Mon, Oct 6, 2014 at 7:46 PM, Minchan Kim wrote:
> On Tue, Oct 07, 2014 at 08:36:08AM +0900, Minchan Kim wrote:
>> Hello Dan,
>>
>> Sorry for the delay. I had internal works which should be handled
>> urgent. I hope you don't lose your interest due to my bad response
>> latency.
>>
>> On Thu,
Linus,
please pull the latest irq-core-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git irq-core-for-linus
The irq departement delivers:
- A cleanup series to get rid of mindlessly copied code.
- Another bunch of new pointlessly different interrupt chip
Repeated connect/disconnect cycles under GNOME can trigger an occasional
OOPS from within e.g. wacom_led_select_store, presumably due to a timing
issue where userspace begins setting a value immediately before the
device disconnects and our shared data is whisked away.
Signed-off-by: Jason
On Wed, Oct 08, 2014 at 04:20:11PM +0530, Pramod Gurav wrote:
> This change switches to using devm_* APIs to allocate resources.
> This helps to simplify failure path in probe function and module
> unloading and does away with remove function.
>
> Cc: Dmitry Torokhov
> Cc:
On Wed, Oct 08, 2014 at 09:14:35AM -0700, Ray Jui wrote:
> Thanks for the reply. It looks like you are also the maintainer of spidev.
> In this case, could you please help to confirm that you expect spidev to use
> separate buffers for TX and RX? If so, I can go ahead and make the change in
>
Adding Mark and Srini
On 10/08/2014 11:13 AM, Dmitry Torokhov wrote:
On Wed, Oct 08, 2014 at 11:00:07AM -0700, Stephen Boyd wrote:
On 10/08/2014 02:30 AM, Ivan T. Ivanov wrote:
On Wed, 2014-10-08 at 12:13 +0300, Ivan T. Ivanov wrote:
On Tue, 2014-10-07 at 10:26 -0700, Dmitry Torokhov wrote:
On Wed, Oct 08, 2014 at 09:12:59AM -0700, Doug Anderson wrote:
> On Wed, Oct 8, 2014 at 5:49 AM, Mark Brown wrote:
> > No, this is not the case. The suspend mode settings are a completely
> > different set of settings activated when the system goes into suspend
> > with explicit hardware
On 10/08/2014 01:58 PM, Jisheng Zhang wrote:
Hi Sebastian,
On Wed, 8 Oct 2014 04:50:53 -0700
Jisheng Zhang wrote:
Hi Sebastian,
On Wed, 8 Oct 2014 04:44:49 -0700
Sebastian Hesselbarth wrote:
On 10/08/2014 01:31 PM, Jisheng Zhang wrote:
Hi Thomas, Sebastian,
On Tue, 30 Sep 2014 14:52:54
On Wed, Oct 08, 2014 at 12:18:31PM +0530, Pramod Gurav wrote:
> This change switches to using devm_* managed resources APIs to
> request the resources in probe to simplify probe error path and
> module unloading and does away with remove function.
>
> Cc: Dmitry Torokhov
> Cc:
On Wed, Sep 24, 2014 at 03:04:15PM +0100, Matt Fleming wrote:
> + preempt_disable();
> + list_for_each_entry(entry, _rmid_limbo_lru, list) {
> + for_each_cpu(cpu, _cpumask) {
> + unsigned long *map;
> +
> + map = _bitmap[cpu *
On Wednesday 08 October 2014 09:27:08 Scott Branden wrote:
> On 14-10-08 06:28 AM, Arnd Bergmann wrote:
> > On Wednesday 08 October 2014 05:27:24 Scott Branden wrote:
> >>>
> >>> I don't think you need per-board config options. The main option
> >>> above should be enough.
> >> This is not a
On Wed, Oct 08, 2014 at 11:00:07AM -0700, Stephen Boyd wrote:
> On 10/08/2014 02:30 AM, Ivan T. Ivanov wrote:
> >On Wed, 2014-10-08 at 12:13 +0300, Ivan T. Ivanov wrote:
> >>On Tue, 2014-10-07 at 10:26 -0700, Dmitry Torokhov wrote:
> >>>Hi Ivan,
> >>>
> >>>On Tue, Oct 07, 2014 at 12:50:46PM +0300,
From: Masami Hiramatsu
Add two selftest scripts which tests kprobe-tracer as the startup
selftest does.
These test cases are testing that the kprobe_event can accept a
kprobe event with $stack related arguments and a kretprobe event
with $retval argument.
Link:
From: Masami Hiramatsu
ftracetest is a collection of testcase shell-scripts for ftrace.
To avoid regressions of ftrace, these testcases check correct
ftrace behaviors. If someone would like to add any features on
ftrace, the patch series should have at least one testcase for
checking the new
Linus,
This patch series starts a new selftests section in the
tools/testing/selftest directory called "ftrace" that holds tests
aimed at testing ftrace and subsystems that use ftrace (like kprobes).
So far only a few tests were written (by Masami Hiramatsu), but more will
be added in the near
Linus,
please pull the latest timers-core-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
timers-core-for-linus
Nothing really exciting this time:
- A few fixlets in the NOHZ code
- A new ARM SoC timer abomination. One should expect that we have
* He YunLei [141007 18:43]:
>
> Thanks for your review and I am really appreciated it, but in our arm
> platform, we haven't custom initcall levels for other drivers. Although
> deferred probe helps other drivers to register well, we are also confused
> for the issues of lots of pin request
On Wed, Sep 24, 2014 at 03:04:15PM +0100, Matt Fleming wrote:
> + limbo_bitmap = kmalloc(sizeof(long) * BITS_TO_LONGS(nr_bits) *
> +nr_cpumask_bits, GFP_KERNEL);
That's going to be a _huge_ amount of memory on SGI class systems. Do we
really need per-cpu storage
From: Masami Hiramatsu
Add basic testcases for kprobe dynamic events.
This also shows that the ftracetest accepts sub-directory
for new testcases.
Link:
http://lkml.kernel.org/p/20140922234254.23415.46964.stgit@kbuild-f20.novalocal
Acked-by: Namhyung Kim
Signed-off-by: Masami Hiramatsu
From: Masami Hiramatsu
Add ftrace basic testcases. This just checks ftrace debugfs
interface works as it is designed.
Link:
http://lkml.kernel.org/p/20140922234252.23415.62897.stgit@kbuild-f20.novalocal
Acked-by: Namhyung Kim
Signed-off-by: Masami Hiramatsu
Signed-off-by: Steven Rostedt
From: Masami Hiramatsu
Add XFAIL and POSIX 1003.3 standard codes (UNRESOLVED/
UNTESTED/UNSUPPORTED) as result codes. These are used for the
results that test case is expected to fail or unsupported
feature (by config).
To return these result code, this introduces exit_unresolved,
exit_untested,
On 10/08/2014 02:30 AM, Ivan T. Ivanov wrote:
On Wed, 2014-10-08 at 12:13 +0300, Ivan T. Ivanov wrote:
On Tue, 2014-10-07 at 10:26 -0700, Dmitry Torokhov wrote:
Hi Ivan,
On Tue, Oct 07, 2014 at 12:50:46PM +0300, Ivan T. Ivanov wrote:
@@ -527,10 +538,55 @@ static int pmic8xxx_kp_probe(struct
On Wed, 2014-10-08 at 13:04 -0400, Linus Torvalds wrote:
> On Wed, Oct 8, 2014 at 11:37 AM, Mike Galbraith
> wrote:
> >
> > 11d4616bd07f38d496bd489ed8fad1dc4d928823 is the first bad commit
> > commit 11d4616bd07f38d496bd489ed8fad1dc4d928823
> > Author: Linus Torvalds
> > Date: Thu Mar 20
Hi,
On Wed, Oct 08, 2014 at 12:13:22PM -0500, Felipe Balbi wrote:
> On Fri, Sep 05, 2014 at 02:32:16PM -0700, Paul E. McKenney wrote:
> > On Thu, Sep 04, 2014 at 03:04:03PM -0500, Felipe Balbi wrote:
> > > Hi,
> > >
> > > On Thu, Sep 04, 2014 at 02:25:35PM -0500, Felipe Balbi wrote:
> > > > On
Serge Hallyn writes:
> Quoting Chen Hanxiao (chenhanx...@cn.fujitsu.com):
>> We could use setns to join the current ns,
>> which did a lot of unnecessary work.
>> This patch will check this senario and
>> return 0 directly.
>>
>> Signed-off-by: Chen Hanxiao
>
> Plus it's just asking for
On Tue, Oct 07, 2014 at 07:32:56PM -0500, Felipe Balbi wrote:
> Hi again,
>
> On Tue, Oct 07, 2014 at 05:18:06PM -0700, David Cohen wrote:
> > The commit '2e4c7553cd usb: gadget: f_fs: add aio support' broke the
> > quirk implemented to align buffer size to maxpacketsize on out endpoint.
> > As
On Tue, Oct 07, 2014 at 07:31:44PM -0500, Felipe Balbi wrote:
> Hi,
Hi Felipe,
>
> On Tue, Oct 07, 2014 at 05:18:06PM -0700, David Cohen wrote:
> > The commit '2e4c7553cd usb: gadget: f_fs: add aio support' broke the
>
> did that commit non-aio or is only aio broken ?
That commit broke the
On Wed, 2014-10-08 at 18:45 +0200, Steinar H. Gunderson wrote:
> On Wed, Oct 08, 2014 at 06:14:18PM +0200, Thomas Gleixner wrote:
> > It looks far more like an issue with the stocking fish code, but hell
> > with futexes one can never be sure.
>
> OK, maybe we should move to a more recent
On Wed, 8 Oct 2014 18:51:10 +0200
Peter Zijlstra wrote:
> On Wed, Oct 08, 2014 at 06:36:57PM +0200, Peter Zijlstra wrote:
> >
> > Right, I'll send the patch.
>
>
I'll see if I can get this in this merge window before I leave to
Dusseldorf.
BTW, what do you think of this solution? Feel free
On Wed, Oct 08, 2014 at 05:33:29PM +0200, Michal Hocko wrote:
> [I do not have time to get over all points here and will be offline
> until Monday - will get back to the rest then]
>
> On Tue 07-10-14 21:11:06, Johannes Weiner wrote:
> > On Tue, Oct 07, 2014 at 03:59:50PM +0200, Michal Hocko
On Wed, Oct 8, 2014 at 7:04 AM, Rafael J. Wysocki wrote:
> On Tuesday, October 07, 2014 02:18:45 AM Rafael J. Wysocki wrote:
>> From: Rafael J. Wysocki
>>
>> Make use of device property API in this driver so that both OF and ACPI
>> based system can use the same driver.
>>
>> This change
On Wed, 8 Oct 2014 10:03:36 +0100
Chris Wilson wrote:
> and adding that back into the current build, e.g.
>
> diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
> index 3632743..48a8a69 100644
> --- a/arch/x86/Kconfig
> +++ b/arch/x86/Kconfig
> @@ -87,6 +87,7 @@ config X86
> select
Hi Linus,
The interesting things here are:
- Turn on Config Request Retry Status Software Visibility. This caused
hangs last time, but we included a fix this time.
- Rework PCI device configuration to use _HPP/_HPX more aggressively
- Allow PCI devices to be put into D3cold during
Anshuman Khandual [khand...@linux.vnet.ibm.com] wrote:
| On 08/28/2014 03:05 AM, Sukadev Bhattiprolu wrote:
| >
| > I see these in arch/powerpc/include/asm/processor.h
| >
| > #ifdef CONFIG_PPC64
| > unsigned long dscr;
| > int dscr_inherit;
| > unsigned
Hi,
On Fri, Sep 05, 2014 at 02:32:16PM -0700, Paul E. McKenney wrote:
> On Thu, Sep 04, 2014 at 03:04:03PM -0500, Felipe Balbi wrote:
> > Hi,
> >
> > On Thu, Sep 04, 2014 at 02:25:35PM -0500, Felipe Balbi wrote:
> > > On Thu, Sep 04, 2014 at 12:16:42PM -0700, Paul E. McKenney wrote:
> > > > On
On 10/07/14 23:49, Stephen Rothwell wrote:
> Hi all,
>
> Please do not add any material intended for v3.19 to you linux-next
> included trees until after v3.18-rc1 has been released.
>
> Changes since 20141007:
>
I saw these build errors in gspca when CONFIG_INPUT=m but the gspca
sub-drivers
Hi
On Wed, Oct 8, 2014 at 6:54 PM, Dmitry Torokhov
wrote:
> Let's automatically set EV_ABS bit in device's event type list when calling
> input_set_abs_params() so that drivers do not have to do it explicitly.
>
> These calls are never in a hot paths so we won't lose much time by setting
> the
On Wed, Oct 08, 2014 at 01:04:01PM -0400, Linus Torvalds wrote:
> So like Thomas, I would suspect a race condition in the futex use, and
> then the exact futex implementation details are just exposing it
> incidentally.
FWIW, Stockfish does not use futex directly; it uses pthreads (or Win32
On Wed, Oct 8, 2014 at 11:37 AM, Mike Galbraith
wrote:
>
> 11d4616bd07f38d496bd489ed8fad1dc4d928823 is the first bad commit
> commit 11d4616bd07f38d496bd489ed8fad1dc4d928823
> Author: Linus Torvalds
> Date: Thu Mar 20 22:11:17 2014 -0700
>
> futex: revert back to the explicit waiter
On 07/10/14 13:13, Vincent Guittot wrote:
> Add new statistics which reflect the average time a task is running on the CPU
> and the sum of these running time of the tasks on a runqueue. The latter is
> named utilization_avg_contrib.
>
> This patch is based on the usage metric that was proposed
On Tue, 2014-10-07 at 20:42 -0700, Serguey Parkhomovsky wrote:
> This patch fixes two unnecessary else conditions that were found by
> checkpatch.pl.
[]
> diff --git a/drivers/staging/rtl8712/rtl8712_efuse.c
> b/drivers/staging/rtl8712/rtl8712_efuse.c
[]
> @@ -541,15 +540,16 @@ u8
Let's automatically set EV_ABS bit in device's event type list when calling
input_set_abs_params() so that drivers do not have to do it explicitly.
These calls are never in a hot paths so we won't lose much time by setting
the same bit several times.
Signed-off-by: Dmitry Torokhov
---
On Wed, Oct 08, 2014 at 12:42:24PM -0400, Rik van Riel wrote:
> On 10/08/2014 02:43 AM, Yasuaki Ishimatsu wrote:
>
> > The divide error is rare case because the trigger is node offline.
> > By this patch, when both of private and shared are set to 0, diff
> > is just set to 0, not
On Wed, Oct 08, 2014 at 06:36:57PM +0200, Peter Zijlstra wrote:
>
> Right, I'll send the patch.
---
Subject: trace: Robustify wait loop
From: Peter Zijlstra (Intel)
Date: Wed Oct 8 18:44:26 CEST 2014
The pending nested sleep debugging triggered on the potential stale
TASK_INTERRUPTIBLE in
Le 07/10/2014 02:19, Scott Wood a écrit :
On Sat, 2014-10-04 at 12:15 +0200, christophe leroy wrote:
Le 03/10/2014 22:24, Scott Wood a écrit :
On Fri, 2014-10-03 at 22:15 +0200, christophe leroy wrote:
Le 03/10/2014 16:44, Mark Brown a écrit :
On Fri, Oct 03, 2014 at 02:56:09PM +0200,
On Wed, Oct 08, 2014 at 06:14:18PM +0200, Thomas Gleixner wrote:
> It looks far more like an issue with the stocking fish code, but hell
> with futexes one can never be sure.
OK, maybe we should move to a more recent Stockfish version first of all;
the specific benchmark was about that specific
On 10/08/2014 02:43 AM, Yasuaki Ishimatsu wrote:
> The divide error is rare case because the trigger is node offline.
> By this patch, when both of private and shared are set to 0, diff
> is just set to 0, not calculating the division.
How about a simple
if (private + shared) == 0)
On Wed, Oct 08, 2014 at 09:49:27AM +0100, Robert Richter wrote:
> On 07.10.14 16:01:49, Liviu Dudau wrote:
> > On Tue, Oct 07, 2014 at 03:27:44PM +0100, Robert Richter wrote:
> > > On 24.09.14 18:06:04, Arnd Bergmann wrote:
> > > > > + compatible = "cavium,thunder-pcie";
> > > > > +
On 10/07/2014 06:16 PM, Dave Hansen wrote:
> On 10/02/2014 07:58 AM, Sasha Levin wrote:
What does this add on top of slab poisoning? Some checks in some
mm places while the object is active, I guess: why not base those
on slab poisoning? And add them in as appropriate to the
On Wed, Oct 08, 2014 at 12:17:18PM -0400, Steven Rostedt wrote:
> On Wed, 8 Oct 2014 17:48:38 +0200
> Peter Zijlstra wrote:
>
>
> > > Wow, what a blast from the past. That code hasn't been touched since
> > > 2009!
> > >
> > > Anyway, all that thread did was call test work on each cpu, and
On Wed, Oct 08, 2014 at 08:49:47AM -0700, Guenter Roeck wrote:
> On Wed, Oct 08, 2014 at 06:32:52AM -0700, Greg Kroah-Hartman wrote:
> > On Wed, Oct 08, 2014 at 09:39:50PM +0900, Satoru Takeuchi wrote:
> > > At Tue, 7 Oct 2014 21:48:04 -0700,
> > > Greg Kroah-Hartman wrote:
> > > >
> > > > On
Thanks for comments - inline.
On 14-10-08 06:10 AM, Rob Herring wrote:
On Wed, Oct 8, 2014 at 12:27 AM, Scott Branden wrote:
From: Jonathan Richardson
Adds initial support for the Cygnus SoC based on Broadcom’s iProc series.
Reviewed-by: Ray Jui
Reviewed-by: Desmond Liu
Reviewed-by: JD
On 10/08/2014 03:14 AM, Bart Tanghe wrote:
> Add pwm driver for Broadcom BCM2835 processor (Raspberry Pi)
Acked-by: Stephen Warren
--
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
Javier,
On Wed, Oct 8, 2014 at 1:46 AM, Javier Martinez Canillas
wrote:
> Yes, you will need Chanwoo's series in order to use this. If also the
> driver needs to set a default initial regulator operating mode, it will
> need the series I'll post today but in that case also a .set_mode handler
>
On Wed, 2014-10-08 at 18:21 +0200, leroy christophe wrote:
> Le 07/10/2014 02:15, Scott Wood a écrit :
> > On Sat, 2014-10-04 at 14:02 +0200, christophe leroy wrote:
> >> What should it look like if that offset had to be in the device tree ?
> > If the offset is not relocatable or discoverable, it
On 10/08/2014 05:12 PM, Mark Brown wrote:
> On Wed, Oct 08, 2014 at 04:38:53PM +0200, Javier Martinez Canillas wrote:
>> On 10/08/2014 04:25 PM, Mark Brown wrote:
>
>> > That doesn't mean that the definition of those modes is something we can
>> > sensibly provide in generic code, especially in a
On 14-10-08 06:28 AM, Arnd Bergmann wrote:
On Wednesday 08 October 2014 05:27:24 Scott Branden wrote:
diff --git a/arch/arm/mach-bcm/Kconfig b/arch/arm/mach-bcm/Kconfig
index fc93800..2dd3f78 100644
--- a/arch/arm/mach-bcm/Kconfig
+++ b/arch/arm/mach-bcm/Kconfig
@@ -5,6 +5,37 @@ menuconfig
Hello,
A lot of activities on percpu front. Notable changes are...
* percpu allocator now can take @gfp. If @gfp doesn't contain
GFP_KERNEL, it tries to allocate from what's already available to
the allocator and a work item tries to keep the reserve around
certain level so that these
On 10/08/2014 04:56 PM, Mark Brown wrote:
> On Wed, Oct 08, 2014 at 03:44:07PM +0200, Javier Martinez Canillas wrote:
>
>> The regulator core now has support to choose a default initial
>> operating mode for regulators from DT. Set the initial opmode
>> for the max77802 PMIC regulators with the
On Wed, Oct 08, 2014 at 05:37:44PM +0200, Mike Galbraith wrote:
> Seems you opened a can of futex worms...
Awesome.
> I don't see that on the 2 x E5-2697 box I borrowed to take a peek. Once
> I got stockfish to actually run to completion by hunting down and brute
> force reverting the below, I
201 - 300 of 1426 matches
Mail list logo
