On Wed, Apr 09, 2014 at 04:03:14PM +0200, Alexander Stein wrote:
> On Wednesday 09 April 2014 14:58:48, One Thousand Gnomes wrote:
> > > I'm getting curious: How can I use device-tree on x86(_64)?
> > > Reading the dependencies from CONFIG_OF it can only be used on 32bit
> > > systems with some sp
On Tue, Apr 08, 2014 at 12:54:47PM -0700, Stephen Boyd wrote:
> > and also, this message looks a bit cryptic for issuing it at ALERT
> > level. I'm ssuming people won't come to you and ask you what it
> > means...? :)
>
> Ok. I can lower it to error level?
I'm just trying to put you in the user's
On Wed, Apr 09, 2014 at 11:14:50AM +0200, Jan Kara wrote:
> On Tue 08-04-14 16:21:02, Matthew Wilcox wrote:
> > On Tue, Apr 08, 2014 at 07:56:00PM +0200, Jan Kara wrote:
> > > > +static void dax_new_buf(void *addr, unsigned size, unsigned first,
> > > > + loff_
On Wed, 09 Apr 2014 11:12:33 -0400
Boris Ostrovsky wrote:
> Commit 198d208df4371734ac4728f69cb585c284d20a15 made 32-bit kernels use
> kernel_stack to point to thread_info. That change missed a couple of
> updates needed by Xen's PV guests:
>
> 1. kernel_stack needs to be initialized for secondar
On Wed, Apr 09, 2014 at 10:06:12AM +0100, Jan Beulich wrote:
> >>> On 08.04.14 at 19:25, wrote:
> > --- a/xen/arch/x86/hvm/hvm.c
> > +++ b/xen/arch/x86/hvm/hvm.c
> > @@ -3470,6 +3470,9 @@ static long hvm_vcpu_op(
> > case VCPUOP_stop_singleshot_timer:
> > case VCPUOP_register_vcpu_info:
On Wed, Apr 09, 2014 at 05:13:26PM +0200, Uwe Kleine-König wrote:
> Hello Russell,
>
> On Wed, Apr 09, 2014 at 04:06:40PM +0100, Russell King - ARM Linux wrote:
> > On Wed, Apr 09, 2014 at 04:54:16PM +0200, Jonas Jensen wrote:
> > > On 13 December 2013 12:39, Russell King - ARM Linux
> > > wrote:
On Thu, Apr 03, 2014 at 06:17:10PM +0200, Frederic Weisbecker wrote:
> Ingo, Thomas,
>
> Please pull the timers/nohz-ipi-for-tip-v3 branch that can be found at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git
> timers/nohz-ipi-for-tip-v3
Ping?
--
To unsubscrib
On Wed, 9 Apr 2014 20:50:59 +0530
Viresh Kumar wrote:
> On 9 April 2014 20:01, Steven Rostedt wrote:
> > Ouch! You are correct, this part of the patch makes no sense. That's
> > what I get for reviewing a patch and not looking at all the code around
> > the changes. (another kernel developer han
On Wed, 9 Apr 2014 11:29:50 -0400
Steven Rostedt wrote:
> On Wed, 9 Apr 2014 20:50:59 +0530
> Viresh Kumar wrote:
>
> > On 9 April 2014 20:01, Steven Rostedt wrote:
> > > Ouch! You are correct, this part of the patch makes no sense. That's
> > > what I get for reviewing a patch and not looking
On 04/09/2014 04:01 AM, Heikki Krogerus wrote:
> Hi,
>
> On Tue, Apr 08, 2014 at 10:37:55AM +0200, Johannes Berg wrote:
>> On Tue, 2014-04-01 at 17:02 +0300, Heikki Krogerus wrote:
>>> I hope this one is OK with everyone.
>>
>> It's fine with me. Are you expecting me to pick up any of these patche
On 9 April 2014 21:01, Steven Rostedt wrote:
>> Do we? This is only called by tick_check_oneshot_change() which has the
>> following:
>>
>> int tick_check_oneshot_change(int allow_nohz)
>> {
>> struct tick_sched *ts = &__get_cpu_var(tick_cpu_sched);
>>
>> if (!test_and_clear_bit(0, &ts
On 04/09/2014 11:01 AM, Jan Beulich wrote:
On 09.04.14 at 16:41, wrote:
The latter load however can easy fault; The arguments for %ds in
XSA-42/ CVE-2013-0228 applies to %{e,f,g}s as well.
And it was only that latter operation that I pointed at.
We don't seem to reference %fs after the pop s
On Wed, Apr 09, 2014 at 03:51:15PM +0200, Boris BREZILLON wrote:
> Retrieve and enable the clock gate related to PL pins.
>
> Signed-off-by: Boris BREZILLON
> ---
> drivers/pinctrl/pinctrl-sunxi.c | 7 +++
> 1 file changed, 7 insertions(+)
>
> diff --git a/drivers/pinctrl/pinctrl-sunxi.c b/
On Wed, Apr 09, 2014 at 09:37:01AM +0200, Roger Pau Monné wrote:
> On 08/04/14 20:53, Konrad Rzeszutek Wilk wrote:
> > On Tue, Apr 08, 2014 at 08:18:48PM +0200, Roger Pau Monné wrote:
> >> On 08/04/14 19:25, kon...@kernel.org wrote:
> >>> From: Konrad Rzeszutek Wilk
> >>>
> >>> When we migrate an
On Wed, Apr 09, 2014 at 10:46:13AM +0400, Vladimir Nikulichev wrote:
> Hi,
>
> On Apr 8, 2014, at 7:41 PM, Jiri Olsa wrote:
>
> > hi,
> > could you please put explanation from first email
> > into the patch changelog?
> >
> > cc-ing lkml
> >
> > thanks,
> > jirka
>
>
> OK, pasting it togethe
On Wed, 2014-03-19 at 07:47 +0100, Peter Zijlstra wrote:
> c6x doesn't have a barrier.h and completely relies on
> asm-generic/barrier.h. Therefore its smp_mb() is barrier() and we can
> use the default versions that are smp_mb().
>
> Signed-off-by: Peter Zijlstra
> ---
Acked-by: Mark Salter
>>> On 09.04.14 at 17:27, wrote:
> On Wed, Apr 09, 2014 at 10:06:12AM +0100, Jan Beulich wrote:
>> >>> On 08.04.14 at 19:25, wrote:
>> > --- a/xen/arch/x86/hvm/hvm.c
>> > +++ b/xen/arch/x86/hvm/hvm.c
>> > @@ -3470,6 +3470,9 @@ static long hvm_vcpu_op(
>> > case VCPUOP_stop_singleshot_timer:
On Wed, Apr 09, 2014 at 03:51:16PM +0200, Boris BREZILLON wrote:
> Retrieve and deassert the reset line related to PL pins.
>
> Signed-off-by: Boris BREZILLON
> ---
> drivers/pinctrl/pinctrl-sunxi.c | 10 ++
> 1 file changed, 10 insertions(+)
>
> diff --git a/drivers/pinctrl/pinctrl-sun
On 09/04/14 16:34, Konrad Rzeszutek Wilk wrote:
> On Wed, Apr 09, 2014 at 09:37:01AM +0200, Roger Pau Monné wrote:
>> On 08/04/14 20:53, Konrad Rzeszutek Wilk wrote:
>>> On Tue, Apr 08, 2014 at 08:18:48PM +0200, Roger Pau Monné wrote:
On 08/04/14 19:25, kon...@kernel.org wrote:
> From: Kon
On Wed, Apr 09, 2014 at 11:18:27AM -0400, Konrad Rzeszutek Wilk wrote:
> On Tue, Apr 08, 2014 at 05:51:23PM +0100, Mel Gorman wrote:
> > On Tue, Apr 08, 2014 at 12:02:50PM -0400, Konrad Rzeszutek Wilk wrote:
> > > .snip..
> > > > >>> David Vrabel has a patchset which I presumed would be pulled thro
On Wed, Apr 09, 2014 at 03:51:17PM +0200, Boris BREZILLON wrote:
> Define PL0/PL1 pins available on the A31 SoC.
>
> Signed-off-by: Boris BREZILLON
> ---
> drivers/pinctrl/pinctrl-sunxi-pins.h | 8
> 1 file changed, 8 insertions(+)
>
> diff --git a/drivers/pinctrl/pinctrl-sunxi-pins.h
On Wed, 9 Apr 2014 11:31:43 -0400
Steven Rostedt wrote:
>
> Hmm, looking at the code, I see it probably should still do the check.
>
> OK, nevermind ;-)
Reading even more of the code, now I'm totally confused :-)
When tick_setup_sched_timer() is called, if tick_nohz_enabled is set,
then we se
>>> On 09.04.14 at 17:38, wrote:
> On 04/09/2014 11:01 AM, Jan Beulich wrote:
> On 09.04.14 at 16:41, wrote:
>>> The latter load however can easy fault; The arguments for %ds in
>>> XSA-42/ CVE-2013-0228 applies to %{e,f,g}s as well.
>> And it was only that latter operation that I pointed at.
On Wed, Apr 09, 2014 at 05:19:11PM +0200, Henrik Austad wrote:
> > The following "real-time" policies are also supported, for
>
> why the "'s?
I borrowed those from SCHED_SETSCHEDULER(2).
> > sched_attr::sched_flags additional flags that can influence
> > scheduling behaviour. Curren
> 1) There was very little if any measurable LTO runtime speedup,
> despite agressive GCC options and despite user-space generally
> offering more optimizations opportunities than kernel space.
See Honza's email. There are lots of benefits in various
large projects.
Also BTW compile
On 04/08, Jim Keniston wrote:
>
> On Sun, 2014-04-06 at 22:16 +0200, Oleg Nesterov wrote:
> > 0xe8. Anything else?
>
> No, I think e8 is the only call instruction uprobes will see.
Good.
> The following couple of paragraphs should be included in the code,
> perhaps merged with some of the related
Move the list of shared fences to a struct, and return it in
reservation_object_get_list().
Add reservation_object_reserve_shared(), which reserves space
in the reservation_object for 1 more shared fence.
reservation_object_add_shared_fence() and
reservation_object_add_excl_fence() are used to as
On Wed, Apr 09, 2014 at 05:17:47PM +0200, Maxime Ripard wrote:
> > I have started to document the PRCM block: http://linux-sunxi.org/PRCM
>
> It's quite different on the A31 and on the A23 actually :(
>
> You don't have any of the audio thing for example, but you have the
> CPUs power clamp contr
On 04/08/2014 06:32 PM, Madhavan Srinivasan wrote:
>> > In mm/Kconfig, put
>> >
>> >config FAULT_AROUND_ORDER
>> >int
>> >default 1234 if POWERPC
>> >default 4
>> >
>> > The way you have it now, every single architecture that needs to enable
>> > this has t
On 04/09/2014 02:20 AM, Li Zhong wrote:
> Or do you mean we don't need to expose any information related to
> SECTION to userspace?
Right, we don't need to expose sections themselves to userspace. Do we?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
On Wednesday 09 April 2014 16:27:11 Russell King - ARM Linux wrote:
> On Wed, Apr 09, 2014 at 05:13:26PM +0200, Uwe Kleine-König wrote:
> > On Wed, Apr 09, 2014 at 04:06:40PM +0100, Russell King - ARM Linux wrote:
> > > On Wed, Apr 09, 2014 at 04:54:16PM +0200, Jonas Jensen wrote:
> > > > On 13 Dec
On 04/09/2014 01:20 AM, Peter Zijlstra wrote:
> This still misses out on Ben's objection that its impossible to get this
> right at compile time for many kernels, since they can boot and run on
> many different subarchs.
Completely agree. The Kconfig-time stuff should probably just be a knob
to t
On Wed, Apr 9, 2014 at 8:18 AM, Mark Lord wrote:
> On 14-04-09 10:12 AM, Mark Lord wrote:
>> On 14-04-09 09:08 AM, Mark Lord wrote:
>>> On 14-04-08 10:51 PM, Benjamin Herrenschmidt wrote:
On Tue, 2014-04-08 at 17:18 -0400, Mark Lord wrote:
>> I assume you're talking about the one added by
On Wed, Apr 09, 2014 at 04:38:37PM +0100, David Vrabel wrote:
> On 09/04/14 16:34, Konrad Rzeszutek Wilk wrote:
> > On Wed, Apr 09, 2014 at 09:37:01AM +0200, Roger Pau Monné wrote:
> >> On 08/04/14 20:53, Konrad Rzeszutek Wilk wrote:
> >>> On Tue, Apr 08, 2014 at 08:18:48PM +0200, Roger Pau Monné w
Hi Levin,
Could you share dump code info like following one which can be generated
by 'objdump -Dl f2fs.ko > obj'.
It may help us to get a clue for this problem.
verify_block_addr()
segment.h:543 (discriminator 3)
2f35: 39 55 eccmp%edx,-0x14(%ebp)
segment.h:542 (disc
On 04/09/2014 11:51 AM, Chao Yu wrote:
> Hi Levin,
>
> Could you share dump code info like following one which can be generated
> by 'objdump -Dl f2fs.ko > obj'.
> It may help us to get a clue for this problem.
>
> verify_block_addr()
> segment.h:543 (discriminator 3)
> 2f35: 39 55 ec
On 9 April 2014 21:11, Steven Rostedt wrote:
> But tick_nohz_active also gets set by tick_setup_sched_timer() which
> looks to be where it should get set. What is the case that this would
> set that variable and tick_setup_sched_timer() would not?
These two are in parallel and only one of these w
Hi Linus,
here is the non-critical part of kbuild:
- One bogus coccinelle check removed, one check fixed not to suggest
the obsolete PTR_RET macro
- scripts/tags.sh does not index the generated *.mod.c files
- new objdiff tool to list differences between two versions of an object
file
- A fix
On Tue, Apr 8, 2014 at 6:27 PM, Stephen Warren wrote:
> On 04/08/2014 05:02 PM, Tim Kryger wrote:
>> On Thu, Apr 3, 2014 at 6:44 AM, Bart Tanghe
>> wrote:
>>> need some recommendation
>>> the memory mapped io registers of the bcm2835 pwm hardware are spreaded
>>> over the memory mapped io
>>> gp
On Fri, Apr 04, 2014 at 05:12:10PM -0700, Arun Shamanna Lakshmi wrote:
> 1. Modify soc_enum struct to handle pointers for reg and mask
> 2. Add dapm get and put APIs for multi register one hot encoded mux
> 3. Update snd_soc_dapm_update struct to support multiple reg update
If you've got several c
On 9 April 2014 21:09, Steven Rostedt wrote:
> Reading even more of the code, now I'm totally confused :-)
:)
> When tick_setup_sched_timer() is called, if tick_nohz_enabled is set,
> then we set tick_nohz_active.
correct.
> This gets called by hrtimer_switch_to_hres(), and before that is
> ca
On Wed, Apr 09, 2014 at 05:50:57PM +0200, Arnd Bergmann wrote:
> On Wednesday 09 April 2014 16:27:11 Russell King - ARM Linux wrote:
> > If it's called from ARM code, then \reg will contain a 4-byte aligned
> > address. If it's called from Thumb code, \reg will contain a 2-byte
> > aligned address
On 04/08/2014 05:36 PM, Greg Kroah-Hartman wrote:
>> > Looks like this just changed the detection order so my device went from
>> > ttyS2 to ttyS4:
>> >
>> > # cat /proc/tty/driver/serial
>> > serinfo:1.0 driver revision:
>> > 0: uart:16550A port:03F8 irq:4 tx:0 rx:0 CTS|DSR|CD
>> > 1: uart:16
From: Russell King - ARM Linux
Date: Wed, 9 Apr 2014 11:01:50 +0100
> What has been proposed for uprobes is a uprobe specific function -
> flush_uprobe_xol_access() which is used after uprobes writes via the
> kmap_atomic() mapping of the page:
>
> + xol_page_kaddr = kmap_atomic(area->page
do_each_thread/while_each_thread iterators are deprecated by
for_each_thread/for_each_process_thread() APIs.
Lets convert the callers in the cputime code accounting. The ultimate
goal is to remove the struct task_struct::thread_group field and
the corresponding do_each_thread/while_each_thread ite
do_each_thread/while_each_thread iterators are deprecated by
for_each_thread/for_each_process_thread() APIs.
Lets convert the callers in the sched subsystem. The ultimate
goal is to remove the struct task_struct::thread_group field and
the corresponding do_each_thread/while_each_thread iterators t
On Wednesday 09 April 2014 08:18:22, Guenter Roeck wrote:
> On Wed, Apr 09, 2014 at 04:03:14PM +0200, Alexander Stein wrote:
> > On Wednesday 09 April 2014 14:58:48, One Thousand Gnomes wrote:
> > > > I'm getting curious: How can I use device-tree on x86(_64)?
> > > > Reading the dependencies from
On Wed, Apr 9, 2014 at 2:02 AM, Steve Capper wrote:
> Hi Kees,
>
> On Mon, Apr 07, 2014 at 08:15:10PM -0700, Kees Cook wrote:
>> This introduces CONFIG_DEBUG_RODATA, making kernel text and rodata
>> read-only. Additionally, this splits rodata from text so that rodata can
>> also be NX, which may l
do_each_thread/while_each_thread iterators are deprecated by
for_each_thread/for_each_process_thread() APIs.
Lets convert the callers in procfs. The ultimate goal is to remove the
struct task_struct::thread_group field and the corresponding
do_each_thread/while_each_thread iterators that are RCU u
On 04/09/2014 11:25 AM, Steven Rostedt wrote:
On Wed, 09 Apr 2014 11:12:33 -0400
Boris Ostrovsky wrote:
Commit 198d208df4371734ac4728f69cb585c284d20a15 made 32-bit kernels use
kernel_stack to point to thread_info. That change missed a couple of
updates needed by Xen's PV guests:
1. kernel_sta
On Wed, Apr 09, 2014 at 05:35:46PM +0200, Jiri Olsa wrote:
> On Wed, Apr 09, 2014 at 10:46:13AM +0400, Vladimir Nikulichev wrote:
> > Hi,
> >
> > On Apr 8, 2014, at 7:41 PM, Jiri Olsa wrote:
> >
> > > hi,
> > > could you please put explanation from first email
> > > into the patch changelog?
> >
On 09/04/2014 16:53, Chen-Yu Tsai wrote:
> Hi Boris,
>
> On Wed, Apr 9, 2014 at 9:51 PM, Boris BREZILLON
> wrote:
>> Hello,
>>
>> This series rework the sunxi pinctrl driver to support the PLx pins
>> available on the A31 SoC.
> Thanks for working on this. I mentioned to Maxime on IRC yesterday t
On Wed, 9 Apr 2014 21:26:51 +0530
Viresh Kumar wrote:
> When HRES isn't enabled and NOHZ isn't enabled as well, in that
> case we should stick to the periodic code from tick-common.c and
> the oneshot options of tick_nohz_switch_to_nohz() or
> hrtimer_switch_to_hres() shouldn't be used. And so,
do_each_thread/while_each_thread iterators are deprecated by
for_each_thread/for_each_process_thread() APIs.
Lets convert the callers in the hung task detector code. The ultimate
goal is to remove the struct task_struct::thread_group field and
the corresponding do_each_thread/while_each_thread ite
Hi,
This is the first pile of a longer series that convert deprecated and
RCU-unsafe thread group iterators (do_each_thread, while_each_thread)
to use for_each_thread/for_each_process_thread RCU-safe iterators that
have been introduced by Oleg.
for_each[_process]_thread() is already upstream so t
do_each_thread/while_each_thread iterators are deprecated by
for_each_thread/for_each_process_thread() APIs.
Lets convert the callers in the tracepoint code. The ultimate
goal is to remove the struct task_struct::thread_group field and
the corresponding do_each_thread/while_each_thread iterators t
On 03/26/2014 02:01 PM, paulmcquad wrote:
>>From 9c385609591c5ed87989a127c95da95aa8845162 Mon Sep 17 00:00:00 2001
> From: Paul McQuade
> Date: Tue, 25 Mar 2014 20:16:47 +
> Subject: [PATCH] Doc: email-clients.txt:added thunderbird settings
>
> Added setting to email-clients that is easier to
On 04/09/2014 10:49 AM, Dave Hansen wrote:
> On 04/09/2014 02:20 AM, Li Zhong wrote:
>> Or do you mean we don't need to expose any information related to
>> SECTION to userspace?
>
> Right, we don't need to expose sections themselves to userspace. Do we?
>
No. the layout in sysfs is based in bl
On Wed, Apr 09, 2014 at 12:09:26PM -0400, David Miller wrote:
> From: Russell King - ARM Linux
> Date: Wed, 9 Apr 2014 11:01:50 +0100
>
> > What has been proposed for uprobes is a uprobe specific function -
> > flush_uprobe_xol_access() which is used after uprobes writes via the
> > kmap_atomic()
On 04/08/2014 02:47 PM, Dave Hansen wrote:
> On 04/08/2014 11:23 AM, Nathan Fontenot wrote:
>> On 04/08/2014 11:13 AM, Dave Hansen wrote:
>>> On 04/08/2014 01:27 AM, Li Zhong wrote:
If Dave and others don't have further objections, it seems this small
userspace incompatibility could be ac
On Wed, Apr 09, 2014 at 08:11:29AM +0200, Willy Tarreau wrote:
> OK I just got it by adding two printk() in pci-mvebu.c. Both functions
> mvebu_pcie_handle_iobase_change() and mvebu_pcie_handle_membase_change()
> do pass a size which is in fact a mask (size - 1) and not the real size.
> So the mbu
Hey Linus,
Here is the pull request for this merge window. Please pull to receive:
- New driver for Qcom bam dma
- New driver for RCAR peri-peri
- New driver for FSL eDMA
- Various odd fixes and updates thru the subsystem
The following changes since commit b28a960c42fcd9cfc987441fa6d1c1a471f0f9e
On 03/30/2014 08:47 PM, Jonathan Callen wrote:
> The sample wrapper currently fails on some Java 7 .class files. This
> updates the wrapper to properly handle those files.
>
> Signed-off-by: Jonathan Callen
Applied. Thanks.
How would I test this?
> ---
> Documentation/java.txt | 8
Hi,
On 09/04/14 18:01, Randy Dunlap wrote:
> On 04/09/2014 12:22 AM, Stephen Rothwell wrote:
>> > Hi all,
>> >
>> > Please do not add material intended for v3.16 to your linux-next included
>> > branches until after v3.15-rc1 is released.
>> >
>> > This tree still fails (more than usual) the pow
Add support for the six-channel Kona PWM controller found on Broadcom
mobile SoCs like bcm281xx.
Signed-off-by: Tim Kryger
Reviewed-by: Alex Elder
Reviewed-by: Markus Mayer
---
drivers/pwm/Kconfig|9 ++
drivers/pwm/Makefile |1 +
drivers/pwm/pwm-bcm-kona.c | 319
Enable PWM drivers and the PWM-based backlight driver.
Signed-off-by: Tim Kryger
Reviewed-by: Alex Elder
Reviewed-by: Markus Mayer
---
arch/arm/configs/bcm_defconfig |3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/arm/configs/bcm_defconfig b/arch/arm/configs/bcm_defconfig
index
Hi Ezequiel,
On Thursday 28 November 2013 21:00:43 Ezequiel Garcia wrote:
> In order to remove the following ugly message:
>
> BUG: mapping for 0x at 0xff00 out of vmalloc space
>
> the iotable mappings should be re-located inside the vmalloc
> region. Such move was introduced at c
Mark the PWM as enabled on the bcm28155 AP board.
Signed-off-by: Tim Kryger
Reviewed-by: Alex Elder
Reviewed-by: Markus Mayer
---
arch/arm/boot/dts/bcm28155-ap.dts |4
1 file changed, 4 insertions(+)
diff --git a/arch/arm/boot/dts/bcm28155-ap.dts
b/arch/arm/boot/dts/bcm28155-ap.dts
On 03/31/2014 08:46 AM, Christoph Hellwig wrote:
diff --git a/block/blk-mq.h b/block/blk-mq.h
index 238379a..eca3a47 100644
--- a/block/blk-mq.h
+++ b/block/blk-mq.h
@@ -1,6 +1,24 @@
#ifndef INT_BLK_MQ_H
#define INT_BLK_MQ_H
+#include
+
+/*
+ * Tag address space map.
+ */
+struct blk_mq_tag
Add the binding description for the Kona PWM controller found on Broadcom's
mobile SoCs.
Signed-off-by: Tim Kryger
Reviewed-by: Alex Elder
Reviewed-by: Markus Mayer
---
.../devicetree/bindings/pwm/bcm-kona-pwm.txt | 21
1 file changed, 21 insertions(+)
create mode
This series introduces the driver for the Kona PWM controller found in
Broadcom mobile SoCs like bcm281xx and updates the device tree and the
defconfig to enable use of this hardware on the bcm28155 AP board.
Changes since v4:
- Added in real polarity support
- Labeled trigger bits as such rat
Add the device tree node for the PWM on bcm11351 SoCs.
Signed-off-by: Tim Kryger
Reviewed-by: Alex Elder
Reviewed-by: Markus Mayer
---
arch/arm/boot/dts/bcm11351.dtsi |8
1 file changed, 8 insertions(+)
diff --git a/arch/arm/boot/dts/bcm11351.dtsi b/arch/arm/boot/dts/bcm11351.dts
Removed not needed spaces and fixed too long lines
Signed-off-by: Richard Leitner
---
drivers/staging/comedi/drivers/adl_pci9118.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/staging/comedi/drivers/adl_pci9118.c
b/drivers/staging/comedi/drivers/adl_pci9118.
Hi,
On Wed, Apr 9, 2014 at 11:17 PM, Maxime Ripard
wrote:
> On Wed, Apr 09, 2014 at 10:53:13PM +0800, Chen-Yu Tsai wrote:
>> Hi Boris,
>>
>> On Wed, Apr 9, 2014 at 9:51 PM, Boris BREZILLON
>> wrote:
>> > Hello,
>> >
>> > This series rework the sunxi pinctrl driver to support the PLx pins
>> > av
- Original Message -
> From: "Frederic Weisbecker"
> To: "LKML"
> Cc: "Frederic Weisbecker" , "Andrew Morton"
> , "Ingo Molnar"
> , "Mathieu Desnoyers" ,
> "Oleg Nesterov" , "Steven
> Rostedt"
> Sent: Wednesday, April 9, 2014 12:11:19 PM
> Subject: [PATCH 2/5] tracepoint: Convert proce
ERROR: that open brace { should be on the previous line
ERROR: else should follow close brace '}
ERROR: space required before the open parenthesis '(
ERROR: trailing whitespace
ERROR: open brace '{' following function declarations go on the next line
ERROR: space required after that ',' (ctx:VxV)
E
On Wed, Apr 09, 2014 at 09:53:50AM +0200, Thomas Petazzoni wrote:
> Maybe this is something that Jason can confirm/infirm. I remember
> having a quick look at the core Linux PCI core to see if it was
> somehow checking whether the bridge BAR has been properly configured,
> but I think I concluded
On Apr 09, Laurent Pinchart wrote:
> Hi Ezequiel,
>
> On Thursday 28 November 2013 21:00:43 Ezequiel Garcia wrote:
> > In order to remove the following ugly message:
> >
> > BUG: mapping for 0x at 0xff00 out of vmalloc space
> >
> > the iotable mappings should be re-located inside
From: Russell King - ARM Linux
Date: Wed, 9 Apr 2014 17:15:55 +0100
> On Wed, Apr 09, 2014 at 12:09:26PM -0400, David Miller wrote:
>> From: Russell King - ARM Linux
>> Date: Wed, 9 Apr 2014 11:01:50 +0100
>>
>> > What has been proposed for uprobes is a uprobe specific function -
>> > flush_upr
On Wed, Apr 09, 2014 at 12:33:58PM -0400, David Miller wrote:
> From: Russell King - ARM Linux
> Date: Wed, 9 Apr 2014 17:15:55 +0100
>
> > On Wed, Apr 09, 2014 at 12:09:26PM -0400, David Miller wrote:
> >> From: Russell King - ARM Linux
> >> Date: Wed, 9 Apr 2014 11:01:50 +0100
> >>
> >> > Wha
PCF8523 uses 1-12 to represent month according to datasheet.
link: www.nxp.com/documents/data_sheet/PCF8523.pdf
Signed-off-by: Chris Cui
---
drivers/rtc/rtc-pcf8523.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/rtc/rtc-pcf8523.c b/drivers/rtc/rtc-pcf8523.c
in
On Wed, Apr 09, 2014 at 04:28:35PM +, Mathieu Desnoyers wrote:
> - Original Message -
> > From: "Frederic Weisbecker"
> > To: "LKML"
> > Cc: "Frederic Weisbecker" , "Andrew Morton"
> > , "Ingo Molnar"
> > , "Mathieu Desnoyers" ,
> > "Oleg Nesterov" , "Steven
> > Rostedt"
> > Sent:
On Tue, Apr 8, 2014 at 3:47 PM, Theodore Ts'o wrote:
> On Mon, Apr 07, 2014 at 10:25:30PM +0200, Geert Uytterhoeven wrote:
>> > maintainers would have no idea that a new syscall has been added.
>>
>> If i386 has the new syscall, scripts/checksyscalls.sh will catch it and
>> inform us about it duri
On 14-04-09 11:52 AM, Bjorn Helgaas wrote:
> On Wed, Apr 9, 2014 at 8:18 AM, Mark Lord wrote:
>> On 14-04-09 10:12 AM, Mark Lord wrote:
>>> On 14-04-09 09:08 AM, Mark Lord wrote:
On 14-04-08 10:51 PM, Benjamin Herrenschmidt wrote:
> On Tue, 2014-04-08 at 17:18 -0400, Mark Lord wrote:
On 04/08, Jim Keniston wrote:
>
> On Mon, 2014-04-07 at 16:27 +0200, Oleg Nesterov wrote:
> >
> > +#define CASE_COND \
> > + COND(70, 71, XF(OF))\
> > + COND(72, 73, XF(CF))\
> > + COND(74, 75, XF(ZF))
On Wed, 9 Apr 2014 16:28:35 + (UTC)
Mathieu Desnoyers wrote:
> - Original Message -
> > From: "Frederic Weisbecker"
> > To: "LKML"
> > Cc: "Frederic Weisbecker" , "Andrew Morton"
> > , "Ingo Molnar"
> > , "Mathieu Desnoyers" ,
> > "Oleg Nesterov" , "Steven
> > Rostedt"
> > Sent:
On 04/09/2014 01:28 PM, Fengguang Wu wrote:
> On Wed, Apr 09, 2014 at 07:08:43AM +0200, Alessandro Rubini wrote:
>> Hello.
>> Thank you for the report.
>>
>> I'm at a conference and I fear I won't be able to test myself in the
>> next days, but I think this is already fixed (it is part of
>> the "m
On Wed, Apr 09, 2014 at 01:48:57PM +0200, Peter Zijlstra wrote:
> On Wed, Feb 26, 2014 at 12:26:43PM -0800, Andy Lutomirski wrote:
> > Speed. FPO saves one register (a big deal on x86_32; not so important
> > on x86_64) but also saves a few cycles on function entry and exit,
> > which is a bigger
On 04/09/2014 01:08 PM, Alessandro Rubini wrote:
> Hello.
> Thank you for the report.
>
> I'm at a conference and I fear I won't be able to test myself in the
> next days, but I think this is already fixed (it is part of
> the "misc_register" call path, so it's the same problem).
>
> The fix is c
On 04/08, Jim Keniston wrote:
>
> On Mon, 2014-04-07 at 16:28 +0200, Oleg Nesterov wrote:
> >
> > It seems that 16bit condi jmp is just 0x0f + short_jump_opc_plus_0x10.
>
> Yes, but the code could use a comment to that effect. See below.
OK, will do.
> Searching for "jump" in the AMD manual, I s
+ if (jl < 4*HZ) {
That was lazy ... should be something like:
+ if (jl < (u64)UINT_MAX * HZ / NSEC_PER_SEC)
-Tony
--
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.kern
On 04/09, Masami Hiramatsu wrote:
>
> Reviewed-by: Masami Hiramatsu
Thanks!
Does this mean that I can add the same into 6-8 you didn't ack
explicitely ?
Oleg.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More m
On 04/09/2014 09:40 AM, Geert Uytterhoeven wrote:
> On Tue, Apr 8, 2014 at 3:47 PM, Theodore Ts'o wrote:
>> On Mon, Apr 07, 2014 at 10:25:30PM +0200, Geert Uytterhoeven wrote:
maintainers would have no idea that a new syscall has been added.
>>>
>>> If i386 has the new syscall, scripts/checks
From: "K. Y. Srinivasan"
Date: Tue, 8 Apr 2014 12:46:11 -0700
> } else if (net_trans_info & INFO_UDP) {
> - csum_info->transmit.udp_checksum = 1;
> + /* UDP checksum offload is not supported on ws2008r2.
> + * Furthermore, on ws2012 and ws2012r2, there
Static values are automatically initialized to NULL.
Acked-by: Anton Altaparmakov
Cc: Andrew Morton
Cc: Anton Altaparmakov
Signed-off-by: Fabian Frederick
---
fs/ntfs/compress.c | 2 +-
fs/ntfs/super.c| 4 ++--
fs/ntfs/sysctl.c | 2 +-
3 files changed, 4 insertions(+), 4 deletions(-)
d
On 04/09, Steven Rostedt wrote:
>
> The tasklist_lock is all that is needed.
Yes, but not _irq. Plus this code is buggy ;)
Steven, I sent these patches twice (at least!). This time I didn't
bother to recheck this code, but the patches still apply so perhaps
you can take a look?
Last attempt, I p
syscall_regfunc() and syscall_unregfunc() should set/clear
TIF_SYSCALL_TRACEPOINT system-wide, but do_each_thread() can race
with copy_process() and miss the new child which was not added to
init_task.tasks list yet.
Change copy_process() to update the child's TIF_SYSCALL_TRACEPOINT
under tasklist
syscall_regfunc() ignores the kernel thread because "it has
no effect", see cc3b13c1 "Don't trace kernel thread syscalls".
However, this means that a user-space task spawned by
call_usermodehelper() won't report the system calls if
kernel_execve() is called when sys_tracepoint_refcount != 0.
Remo
From: Lasse Collin
Signed-off-by: Lasse Collin
---
lib/xz/xz_dec_lzma2.c |4
1 file changed, 4 insertions(+)
diff -Narup linux-3.14.orig/lib/xz/xz_dec_lzma2.c
linux-3.14/lib/xz/xz_dec_lzma2.c
--- linux-3.14.orig/lib/xz/xz_dec_lzma2.c 2014-03-31 06:40:15.0
+0300
+++ li
This is the correct patch.
PCF8523 uses 1-12 to represent month according to datasheet.
link: www.nxp.com/documents/data_sheet/PCF8523.pdf.
Signed-off-by: Chris Cui
---
drivers/rtc/rtc-pcf8523.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/rtc/rtc-pcf8523.c b
301 - 400 of 788 matches
Mail list logo
