On Mon, 06 Jul 2015 03:34:59 +0100, jon said:
> I remember "virtual memory" and even "virtual addressing" but I think
> the term "virtual machine" is modern, maybe someone else knows, google
> did not help me much trying to prove it one way or the other.
Hardly. IBM was working with virtual
Hm. Piddling with pgbench, which doesn't seem to collapse into a
quivering heap when load exceeds cores these days, deltas weren't all
that impressive, but it does appreciate the extra effort a bit, and a
bit more when clients receive it as well.
If you test, and have time to piddle, you could
2015-07-06 13:03 GMT+09:00 Krzysztof Kozlowski :
> 2015-06-12 14:46 GMT+09:00 Javier Martinez Canillas :
>> Hello Krzysztof,
>>
>> On Fri, Jun 12, 2015 at 3:53 AM, Krzysztof Kozlowski
>> wrote:
>>> The TSADC gate clock was used in Exynos4x12 DTSI for exynos-adc driver.
>>> However TSADC is
Entry symbols are not kprobe safe. So blacklist them for kprobing.
Signed-off-by: Pratyush Anand
---
arch/arm64/kernel/entry.S | 3 +++
arch/arm64/kernel/kprobes.c | 9 +
arch/arm64/kernel/vmlinux.lds.S | 1 +
3 files changed, 13 insertions(+)
diff --git
Add all function symbols which are called from do_debug_exception under
NOKPROBE_SYMBOL, as they can not kprobed.
Signed-off-by: Pratyush Anand
---
arch/arm64/kernel/debug-monitors.c | 18 ++
arch/arm64/kernel/hw_breakpoint.c | 8
arch/arm64/kernel/kgdb.c |
Functions which are called from do_debug_execptions and all entry routines
must not allow to insert kprobe in it, otherwise we may witness a system hang.
This patch set blacklist such symbols.
Patches should be applied on top of arm64 kprobe patches [1].
[1] https://lkml.org/lkml/2015/6/15/514
Enable SG support for Zynq SOC family devices.
Signed-off-by: Punnaiah Choudary Kalluri
---
drivers/net/ethernet/cadence/macb.c |6 ++
1 files changed, 2 insertions(+), 4 deletions(-)
diff --git a/drivers/net/ethernet/cadence/macb.c
b/drivers/net/ethernet/cadence/macb.c
index
Hi Geert,
On Sat, Jul 4, 2015 at 2:02 AM, Geert Uytterhoeven wrote:
> Hi Wolfram,
>
> On Fri, Jul 3, 2015 at 4:37 PM, Wolfram Sang wrote:
>>> So this is a single core machine and uses the em_sti timer w/o the
>>> broadcast nonsense. In Simons case it looks like em_sti is used as
>>> broadcast
Hi Wolfram,
Thanks for investigating this.
On Sat, Jul 4, 2015 at 12:09 AM, Wolfram Sang wrote:
>
>> Ok. So it's unrelated to deep idle states. Any chance of poking with
>> JTAG at the frozen box? If not, are there GPIOs which you could use to
>> monitor certain state?
>
> No JTAGger here at
>
> What are the symptoms of this bug?
>
In the cases where we hit this race and the core enters fastsleep,
code mistakes an idle thread as running. Because of this, the first
thread waking up from fastsleep which is supposed to resync timebase
skips it. So we can end up having a core with
This patch allows passing perf's own PID to '--filter' by using
'@PERFPID'. This should be useful when system-widely capturing
tracepoints events.
Before this patch, when doing something like:
# perf record -a -e syscalls:sys_enter_write
One could easily get result like this:
# /tmp/perf
On Marvell Berlin SoCs, the cpu's local timer is shutdown when the cpu
goes to a deep idle state, then the timer framework will be notified to
use a broadcast timer instead. In our case, the broadcast timer uses
dw-apb-ictl as interrupt chip. This patch adds irq_set_affinity support
so that the
On Marvell Berlin SoCs, the cpu's local timer is shutdown when the cpu
goes to a deep idle state, then the timer framework will be notified to
use a broadcast timer instead. In our case, the broadcast timer uses
dw-apb-ictl as the interrupt chip. These patches try to add irq_set_affinity
support
This patch adds struct dw_apb_ictl_priv definition, now it only has one
member: the irq domain. Then make the generic irq chip gc->private to point
to the struct. This is to prepare for the next patch which will implement
irq_set_affinity.
Signed-off-by: Jisheng Zhang
---
Hi Morten,
On Fri, Jul 03, 2015 at 10:34:41AM +0100, Morten Rasmussen wrote:
> > > IOW, since task groups include blocked load in the load_avg_contrib (see
> > > __update_group_entity_contrib() and __update_cfs_rq_tg_load_contrib()) the
> > > imbalance includes blocked load and hence
2015-06-12 14:46 GMT+09:00 Javier Martinez Canillas :
> Hello Krzysztof,
>
> On Fri, Jun 12, 2015 at 3:53 AM, Krzysztof Kozlowski
> wrote:
>> The TSADC gate clock was used in Exynos4x12 DTSI for exynos-adc driver.
>> However TSADC is present only on Exynos4210 so on Trats2 board (with
>>
On Wed, 2015-01-07 at 06:34:10 UTC, "Shreyas B. Prabhu" wrote:
> core_idle_state is maintained for each core. It uses 0-7 bits to track
> whether a thread in the core has entered fastsleep or winkle. 8th bit is
> used as a lock bit.
> The lock bit is set in these 2 scenarios-
> - The thread is
continguos -> contiguous
Signed-off-by: Masahiro Yamada
---
Changes in v2:
- Remove '.' from the end of the subject
mm/nommu.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/mm/nommu.c b/mm/nommu.c
index 58ea364..0b34f40 100644
--- a/mm/nommu.c
+++
continguos -> contiguous
Signed-off-by: Masahiro Yamada
---
mm/nommu.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/mm/nommu.c b/mm/nommu.c
index 58ea364..0b34f40 100644
--- a/mm/nommu.c
+++ b/mm/nommu.c
@@ -324,12 +324,12 @@ long vwrite(char *buf, char *addr,
2015-06-09 1:14 GMT+09:00 Lukasz Majewski :
> Hi Krzysztof,
>
>> During probe the regulator (if present) was enabled but not disabled
>> in case of failure. So an unsuccessful probe lead to enabling the
>> regulator which was actually not needed because the device was not
>> enabled.
>>
>>
Hi all,
Now that -rc1 is out, please clean up your trees if necessary.
Changes since 20150703:
I have started doing a build of tools/perf between each merge.
My fixes tree contains:
staging: board: Kconfig: Let STAGING_BOARD depend on CLKDEV_LOOKUP
tools/perf, rbtree: Add RCU wrappers to
The basic support for UniPhier SoC family (arch/arm/mach-uniphier)
was mainlined at Linux 4.1-rc1.
I am now tackling some drivers to support them in the mainline.
I've got UART and EHCI done, so I'd like to enable them from
the ARM-SOC subsystem.
Masahiro Yamada (3):
ARM:
The UniPhier on-chip UART driver was merged into the mainline by
commit 1a8d2903cb6a (serial: 8250_uniphier: add UniPhier serial
driver).
Enable it from multi_v7_defconfig.
Signed-off-by: Masahiro Yamada
---
arch/arm/configs/multi_v7_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git
The UniPhier on-chip UART driver was merged into the mainline by
commit 1a8d2903cb6a (serial: 8250_uniphier: add UniPhier serial
driver).
Add device nodes to make it really available.
We no longer have to depend on the on-board UART device (16550A),
so let's change the chosen and aliases to
Get USB 2.0 host controllers available with generic-ehci bindings.
Signed-off-by: Masahiro Yamada
---
arch/arm/boot/dts/uniphier-ph1-ld4-ref.dts | 8
arch/arm/boot/dts/uniphier-ph1-ld4.dtsi | 21 +
arch/arm/boot/dts/uniphier-ph1-pro4-ref.dts | 8
The following was seen in branch[0] build.
arch/arm/mach-rockchip/platsmp.c:154:23: error:
'rockchip_secondary_startup' undeclared (first use in this function)
branch[0]:
git://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git
v4.3-armsoc/soc
The broken build is caused by the
LTC2945 is replaced by INA220 in rev2.0.
Please note it as "Superseded" in patchworks.
Thanks.
---
Best Regards,
Hongtao
> -Original Message-
> From: Alison Wang [mailto:b18...@freescale.com]
> Sent: Monday, July 06, 2015 10:38 AM
> To: shawn@linaro.org; Jin Zhengxiong-R64188;
On Mon, Jul 06, 2015 at 03:34:59AM +0100, jon wrote:
> > It is true if and only if clone(2) gets CLONE_FILES in its arguments.
> > Sharing address space is controlled by CLONE_VM and these can be used
> > independently; pthreads set both at the same time, but you can have shared
> > descriptor
From: Wang Dongsheng
Add ftm0 node, cause of ftm0 can be set as a alarm before system
going to deep sleep.
Signed-off-by: Wang Dongsheng
---
arch/arm/boot/dts/ls1021a-qds.dts | 4
arch/arm/boot/dts/ls1021a.dtsi| 8
2 files changed, 12 insertions(+)
diff --git
scaled down weight 'fact' would not be > u32 rather than unlikely as the
values being passed for delta is either NICE_O_LOAD or the weight of the
'se' which would be a value that can be accomodated in a u32. Remove the
initial > u32 handling on 'fact'.
9dbdb15553239 ("sched/fair: Rework
From: Jia Hongtao
This patch adds LTC2945 node for LS1021A TWR board.
Signed-off-by: Jia Hongtao
---
arch/arm/boot/dts/ls1021a-twr.dts | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/arm/boot/dts/ls1021a-twr.dts
b/arch/arm/boot/dts/ls1021a-twr.dts
index a0d9ad6..938b16a
On Mon, 2015-07-06 at 02:08 +0100, Al Viro wrote:
> On Mon, Jul 06, 2015 at 12:35:48AM +0100, jon wrote:
> > > Anyway, the underlying model hasn't changed much since _way_ back; each
> > > thread of execution is a virtual machine of its own, with actual CPUs
> > > switched between those.
> > Ok,
On 07/06/2015 06:48 AM, Stephen Rothwell wrote:
> Hi all,
>
> On Sun, 5 Jul 2015 18:57:51 +0200 Geert Uytterhoeven
> wrote:
>>
>> On Sat, Jul 4, 2015 at 11:35 PM, Chen Gang
>> wrote:
>>> It needs clk_add_alias() from clk drivers, which is implemented in
>>> "drivers/clk/clkdev.c" which
On Sun, Jul 05, 2015 at 09:09:04PM -0400, Nicholas Krause wrote:
> This makes the function ext4_ext_tree_init have a return type of
> void due to this function always completed its intended work of
> intialzing a ext4_extent_header structue pointer off its passed
> arguments of a inode and
This commit implements the switchdev operations to add, delete and dump
VLANs for the Marvell 88E6352 and compatible switch chips.
This allows to access the switch VLAN Table Unit from standard userspace
commands such as "bridge vlan".
A configuration like "1t 2t 3t 4u" for VLAN 10 is achieved
Implement the Get Next and Load Purge operations for the VLAN Table
Unit, and a "vtu" debugfs file to read and write the hardware VLANs.
A populated VTU look like this:
# cat /sys/kernel/debug/dsa0/vtu
VID FID SID 0 1 2 3 4 5 6
550 5620 x x x u x t x
1000
Hi all,
This patchset brings full support for hardware VLANs in DSA, and the Marvell
88E6xxx compatible switch chips.
The first patch adds the VTU operations to the mv88e6xxx code, as well as a
"vtu" debugfs file to read and modify the hardware VLAN table.
The second patch adds the glue between
This patch adds the glue between DSA and switchdev operations to add,
delete and dump SWITCHDEV_OBJ_PORT_VLAN objects.
This is a first step to link the "bridge vlan" command with hardware
entries for DSA compatible switch chips.
Signed-off-by: Vivien Didelot
---
include/net/dsa.h | 9
In dpcm_get_be(), it looks for a BE rtd that has the DAI widget
according to current stream type. Only playback_widgets are searched
in the case of playback stream and vice versa. However, the DAI widget
itself can be playback or capture.
If the DAI widget is capture, but current stream type is
Acked-by: Anish Bhatt --
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 FAQ at http://www.tux.org/lkml/
ATK4001 is an ACPI device for wireless hotkey, similar to how Dell and
HP are doing it. It is just ASUS who decides LED should be controlled
by software unlike HP whose LED is driven by hardware pins on mini
card.
On Fri, Jul 3, 2015 at 3:25 PM, Pali Rohár wrote:
> On Thursday 02 July 2015
From: Sanchayan Maity Sent: Wednesday, June 24, 2015
4:34 PM
> To: ji...@kernel.org
> Cc: shawn@linaro.org; ker...@pengutronix.de; robh...@kernel.org;
> pawel.m...@arm.com; mark.rutl...@arm.com; ijc+devicet...@hellion.org.uk;
> ga...@codeaurora.org; Duan Fugang-B38611;
On Mon, Jul 06, 2015 at 12:35:48AM +0100, jon wrote:
> > Anyway, the underlying model hasn't changed much since _way_ back; each
> > thread of execution is a virtual machine of its own, with actual CPUs
> > switched between those.
> Ok, not sure I quite follow. What do you mean virtual machine ?
> > Change-Id: Ic5c93eb5d1e6e23503dabd28d41c30a7f02e9c18
>
> Please delete the change-id.
> > + uart0: serial@11005000 {
> > + compatible = "mediatek,mt6580-uart",
> > +"mediatek,mt6577-uart";
>
> Please update the dts documentation about the compatible
On 2015/7/3 19:23, Paolo Bonzini wrote:
On 03/07/2015 10:56, Tiejun Chen wrote:
After commit 1cde2930e154 ("sched/preempt: Add static_key() to
preempt_notifiers") is introduced, preempt_notifier_{register, unregister}
always hold a mutex, jump_label_mutex. So in current case this shouldn't
work
There are two duplicated xenvif_zerocopy_callback() definitions.
Remove one of them.
Signed-off-by: Liang Li
---
drivers/net/xen-netback/common.h | 3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/net/xen-netback/common.h b/drivers/net/xen-netback/common.h
index 8a495b3..c6cb85a
Commit 0e1cc95b4cc7
("mm: meminit: finish initialisation of struct pages before basic setup")
introduced a rwsem to signal completion of the initialization workers.
Lockdep complains about possible recursive locking:
=
[ INFO: possible recursive
Hi all,
Today's linux-next merge of the tip tree got a conflict in:
kernel/sched/core.c
between commit:
2ecd9d29abb1 ("sched, preempt_notifier: separate notifier registration from
static_key inc/dec")
from Linus' tree and commit:
6efde1d3716b ("sched/preempt, kvm: Fix KVM
On Sat, Jul 04, 2015 at 03:03:46AM +0200, Rafael J. Wysocki wrote:
> On Friday, July 03, 2015 11:42:50 AM Dave Chinner wrote:
> > On Wed, Jul 01, 2015 at 11:07:29PM -0400, Len Brown wrote:
> > > >> The _vast_ majority of systems using Linux suspend today are under
> > > >> an Android user-space.
Hi,
I have to load linux from a multiboot boot loader. The last work I saw
in this regard is a patch for 2.4.14. Does anyone have a current proof
of concept multiboot patch?
if not, what are the steps involved to make a bootable multiboot elf
kernel? Is there any way I can get the final file
On Sun, 2015-07-05 at 18:39 +0100, Al Viro wrote:
> On Sun, Jul 05, 2015 at 04:46:50PM +0100, jon wrote:
>
> > I should have titled it "Feature request from a simple minded user"
> >
> > I have not the slightest idea what you are talking about.
> >
> > When I learnt *nix it did not have "name
Hi all,
After merging the device-mapper tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/md/dm-thin.c: In function '__pool_destroy':
drivers/md/dm-thin.c:2780:2: error: implicit declaration of function 'vfree'
[-Werror=implicit-function-declaration]
On Sunday, July 05, 2015 07:37:27 PM Daniel Machon wrote:
> Fixed coding style issue.
>
> Signed-off-by: Daniel Machon
So had I though that these things were worth "fixing", I'd have done it myself
already.
I'm not going to apply patches like this one unless you can explain to me
what *real*
On Saturday, July 04, 2015 10:37:55 AM Alan Stern wrote:
> On Sat, 4 Jul 2015, Rafael J. Wysocki wrote:
>
> > > >> > Perhaps the pm_runtime_suspended_if_enabled() test should be changed
> > > >> > to
> > > >> > pm_runtime_status_suspended(). Then it won't matter whether the
> > > >> >
On Sun, Jul 05, 2015 at 01:22:48PM -0700, Linus Torvalds wrote:
> It's Sunday, two weeks have passed, and the merge window is closed. I
> just pushed out the tag to the git trees, and tar-balls and patches
> should be mirroring out too.
>
Testing doesn't look bad for -rc1.
Build results:
On Saturday, July 04, 2015 10:19:55 AM Alan Stern wrote:
> On Sat, 4 Jul 2015, Rafael J. Wysocki wrote:
>
> > The only argument against dropping sys_sync() from the suspend code path
> > I've seen in this thread that I entirely agree with is that it may lead to
> > regressions, because we've done
On Saturday, July 04, 2015 10:50:36 AM Geert Uytterhoeven wrote:
> On Sat, Jul 4, 2015 at 3:03 AM, Rafael J. Wysocki wrote:
> > [The argument that the user can pull removable storage devices out of the
> > system while suspended doesn't hold any water to me, because the user can
> > pull them out
Hi all,
On Sun, 5 Jul 2015 18:57:51 +0200 Geert Uytterhoeven
wrote:
>
> On Sat, Jul 4, 2015 at 11:35 PM, Chen Gang
> wrote:
> > It needs clk_add_alias() from clk drivers, which is implemented in
> > "drivers/clk/clkdev.c" which depends on CLKDEV_LOOKUP.
> >
> > Normally, archs and clk driver
The following changes since commit a2fd66d069d86d793e9d39d4079b96f46d13f237:
ext4: set lazytime on remount if MS_LAZYTIME is set by mount (2015-06-23
11:03:54 -0400)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git
On Fri, 3 Jul 2015, David Dueck wrote:
> Deactivating the use of interrupts here fixes a crash on early boot with
> RT-Preempt.
Again, you completely fail to explain WHAT the problem is and WHY you
think that your patch is a proper solution.
Thanks,
tglx
--
To unsubscribe from this
On Fri, 3 Jul 2015, David Dueck wrote:
> This fixes a warning when using RT-Preempt.
That's not a proper explanation for the patch and by all means it
cannot fix anything because free_irq() is just a different wrapper
around __free_irq() than remove_irq(). So how on earth fixes that the
problem
On Wed, 24 Jun 2015, Steven Rostedt wrote:
> > +
> > +#define show_chip_name(irq)\
> > + (irq_get_irq_data(irq) \
> > +? irq_get_irq_data(irq)->chip->name\
> > +: "NULL")
> > +
>
Anotherpattern that occurred to me is, eg
info->MS_Status = *(struct MS_STATUS *)[0];
where buf is an array. I find this in 11 files.
julia
--
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 Tue, Jun 23, 2015 at 11:50:37AM +0200, Michal Hocko wrote:
> ext4_free_blocks is looping around the allocation request and mimics
> __GFP_NOFAIL behavior without any allocation fallback strategy. Let's
> remove the open coded loop and replace it with __GFP_NOFAIL. Without
> the flag the
If no broadcast device is installed and the cpu local timers stop in
deeper idle states, then there is currently nothing telling the idle
code that it should not go into deep idle states, so the timers stop
and nothing wakes up the cpus.
Make the broadcast_enter/exit() functions independent of
The following two patches address shortcomings in the tick broadcast
code, which were reported and analyzed by Sudeep Holla and Andriy
Gapon.
Thanks,
tglx
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
Andriy reported that on a virtual machine the warning about negative
expiry time in the clock events programming code triggered:
hpet: hpet0 irq 40 for MSI
hpet: hpet1 irq 41 for MSI
Switching to clocksource hpet
WARNING: at kernel/time/clockevents.c:239
[] clockevents_program_event+0xdb/0xf0
[]
From: Markus Elfring
Date: Sun, 5 Jul 2015 22:45:23 +0200
The drm_fbdev_cma_restore_mode() function tests whether its argument
is NULL and then returns immediately.
Thus the test around the call is not needed.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus
It's Sunday, two weeks have passed, and the merge window is closed. I
just pushed out the tag to the git trees, and tar-balls and patches
should be mirroring out too.
I thought this release would be one of the biggest ones ever, but it
turns out that it will depend on how you count. Just counting
As per https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53383, GCC only
allows -mpreferred-stack-boundary=3 on x86_64 if -mno-sse is set.
That means that cc-option will not detect
-mpreferred-stack-boundary=3 support, because we test for it before
setting -mno-sse.
Fix it by reordering the Makefile
On 07/03/2015 02:40 PM, Linus Torvalds wrote:
> On Fri, Jul 3, 2015 at 8:23 AM, Jan Kara wrote:
>>
>> Because the address isn't 32-byte aligned (which I assume is the
>> requirement from looking into the code). So clearly my gcc messed up and
>> miscompiled the thing by ignoring the alignment
From: Markus Elfring
Date: Sun, 5 Jul 2015 21:55:10 +0200
The drm_property_unreference_blob() function tests whether its argument
is NULL and then returns immediately.
Thus the test around the call is not needed.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus
On Sat, Jul 04, 2015 at 03:33:00AM +0800, Liang Li wrote:
> There are two duplicated xenvif_zerocopy_callback() definitions.
> Remove one of them.
>
> Signed-off-by: Liang Li
Acked-by: Wei Liu
Please fix the time of your computer and resend.
Wei.
> ---
> drivers/net/xen-netback/common.h |
On Mon, Jun 29, 2015 at 05:37:10PM +0200, Eric Auger wrote:
> With the advent of GICv3 ITS in-kernel emulation, KVM GSI routing
> appears to be requested. More specifically MSI routing is needed.
> irqchip routing does not sound to be really useful on arm but usage of
> MSI routing also mandates
On this machine, a single core Athlon 64 with a 32 bit current Linus'
git head kernel, I get a lock-up early in the boot process. (A dmesg
output of a successful boot-up of kernel 4.1.0 up to and slightly passed
the point where the git head kernel locks up is attached).
A photo of the lock-up
From: Robert Jarzmik
In preparation for dmaengine conversion, move the camera interrupt
handling into a tasklet. This won't change the global flow, as this
interrupt is only used to detect the end of frame and activate DMA fifos
handling.
Signed-off-by: Robert Jarzmik
---
Convert pxa_camera to dmaengine. This removes all DMA registers
manipulation in favor of the more generic dmaengine API.
The functional level should be the same as before. The biggest change is
in the videobuf_sg_splice() function, which splits a videobuf-dma into
several scatterlists for 3
From: Robert Jarzmik
Fix the error path where the video buffer wasn't allocated nor
mapped. In this case, in the driver free path don't try to unmap memory
which was not mapped in the first place.
Signed-off-by: Robert Jarzmik
---
drivers/media/platform/soc_camera/pxa_camera.c | 6 --
1
Hi Guennadi,
This is the next round.
Most of your comments are addressed or answered, the one big thing left apart is
the videobuf_sg_cut() implementation and complexity. If you have a better idea,
I'm all ears.
One thing that changed since v1 is that pxa_dma driver was accepted into
dmaengine
From: Robert Jarzmik
This moves the dma irq handling functions up in the source file, so that
they are available before DMA preparation functions. It prepares the
conversion to DMA engine, where the descriptors are populated with these
functions as callbacks.
Signed-off-by: Robert Jarzmik
---
On Sun, 05 Jul 2015 06:07:54 +0800, Chen Gang said:
> For upstream cris toolchain (gcc is 6.0
typo?
pgpqUqjfv2xqt.pgp
Description: PGP signature
From: Markus Elfring
Date: Sun, 5 Jul 2015 20:15:12 +0200
The functions nvkm_namedb_put() and pci_dev_put() test whether their
argument is NULL and then return immediately.
Thus the test around the calls is not needed.
This issue was detected by using the Coccinelle software.
Signed-off-by:
This patch fixes the checkpatch.pl warning:
WARNING: Macros with flow control statements should be avoided
Replace the macro with a function doing the exact same task as the
macro.
Signed-off-by: Arjun Krishna Babu
---
drivers/staging/dgnc/dgnc_sysfs.c | 22 ++
1 file
Fixed coding style issues.
Signed-off-by: Daniel Machon
---
drivers/acpi/custom_method.c | 2 +-
drivers/acpi/osl.c | 32
2 files changed, 17 insertions(+), 17 deletions(-)
diff --git a/drivers/acpi/custom_method.c b/drivers/acpi/custom_method.c
IIO_EV_TYPE_THRESH in rising direction describes an event where the
threshold is crossed in rising direction, positive or negative values
being possible. This is not the case here.
Since the threshold is no signed value and only the magnitude is compared,
IIO_EV_TYPE_MAG is what describes the
On Thu, 26 Mar 2015, Scot Doyle wrote:
> Add a Console Private CSI sequence to specify the current console's
> cursor blink interval. The interval is specified as a number of
> milliseconds until the next cursor display state toggle, from 50 to
> 65535.
>
> Signed-off-by: Scot Doyle
> ---
>
On Sun, Jul 05, 2015 at 04:46:50PM +0100, jon wrote:
> I should have titled it "Feature request from a simple minded user"
>
> I have not the slightest idea what you are talking about.
>
> When I learnt *nix it did not have "name spaces" in reference to process
> tables. I understand the
Fixed coding style issue.
Signed-off-by: Daniel Machon
---
drivers/acpi/battery.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/acpi/battery.c b/drivers/acpi/battery.c
index b3628cc..0447c6a 100644
--- a/drivers/acpi/battery.c
+++ b/drivers/acpi/battery.c
@@
Fixed coding style issue.
Signed-off-by: Daniel Machon
---
drivers/acpi/acpi_memhotplug.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/acpi/acpi_memhotplug.c b/drivers/acpi/acpi_memhotplug.c
index ee28f4d..5faf598 100644
--- a/drivers/acpi/acpi_memhotplug.c
+++
On UML builds, of_address.c fails to compile:
../drivers/of/address.c:873:2: error: implicit declaration of function
‘ioremap’ [-Werror=implicit-function-declaration]
This is due to CONFIG_OF now being user selectable. Add a dependency on
HAS_IOMEM to OF_ADDRESS in order to fix this.
Allow a nested hypervisor to single step its guests.
Signed-off-by: Mihai Donțu
---
This patch applies on top of current linux-next.
---
arch/x86/include/asm/vmx.h | 1 +
arch/x86/include/uapi/asm/vmx.h | 2 ++
arch/x86/kvm/vmx.c | 10 +-
3 files changed, 12
Jin debugged a nasty cpu hotplug race which results in leaking a irq
vector on the newly hotplugged cpu.
cpu N cpu M
native_cpu_up device_shutdown
do_boot_cpu free_msi_irqs
start_secondary arch_teardown_msi_irqs
Jin debugged a subtle race in the cpu hotplug code which caused my to
look deeper into this. So I unearthed quite a few racy constructs.
Aside of the x86 specific problems I discovered a generic issue which
needs to be addressed in the cpu hotplug code.
Thanks,
tglx
--
To unsubscribe
irq_data is protected by irq_desc->lock, so retrieving the irq chip
from irq_data outside the lock is racy vs. an concurrent update. Move
it into the lock held region.
While at it add a comment why the vector walk does not require
vector_lock.
Signed-off-by: Thomas Gleixner
---
It's unsafe to examine fields in the irq descriptor w/o holding the
descriptor lock. Add proper locking.
While at it add a comment why the vector check can run lock less
Signed-off-by: Thomas Gleixner
---
arch/x86/kernel/irq.c | 13 -
1 file changed, 12 insertions(+), 1
When a cpu goes up some architectures (e.g. x86) have to walk the irq
space to set up the vector space for the cpu. While this needs extra
protection at the architecture level we can avoid a few race
conditions by preventing the concurrent allocation/free of irq
descriptors and the associated
On Sat, Jul 4, 2015 at 11:35 PM, Chen Gang wrote:
> It needs clk_add_alias() from clk drivers, which is implemented in
> "drivers/clk/clkdev.c" which depends on CLKDEV_LOOKUP.
>
> Normally, archs and clk driver its own will decide whether select
> CLKDEV_LOOKUP, and common drivers will decide
Hi,
On Mon, Jun 29, 2015 at 3:04 PM, Leilk Liu wrote:
> Signed-off-by: Leilk Liu
> ---
> .../devicetree/bindings/spi/spi-mt65xx.txt | 32
> ++
> 1 file changed, 32 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/spi/spi-mt65xx.txt
>
> diff
- Original Message -
I NEED YOUR HELP
=
--
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 FAQ at
On 07/05/2015 06:44 PM, Kirill A. Shutemov wrote:
>> Again that could mean a theoretical regression for some in-tree driver,
>> do you know of any such driver?
>
> I did very little testing with the patch: boot kvm with Fedora and run
> trinity there for a while. More testing is required.
>
It
1 - 100 of 574 matches
Mail list logo
