Hi Olliver,
On Wed, Jan 07, 2015 at 08:31:06AM +0100, Olliver Schinagl wrote:
> From: Olliver Schinagl
>
> Almost all of the speaker drivers under input manipulate the ev bits
> directly, which is not needed, as there is a helper available.
>
> This patch makes use of the helper for the
Rockchip RK3288 hdmi is compatible with dw_hdmi
Signed-off-by: Andy Yan
---
Changes in v18:
- fix two compile errors when build as module
Changes in v17:
- parse resource and irq in platform driver
Changes in v16: None
Changes in v15:
- remove THIS_MODULE in platform driver
Changes in v14:
On Mon, Jan 05, 2015 at 05:04:55PM -0500, Benjamin Tissoires wrote:
> On Mon, Jan 5, 2015 at 5:00 PM, Gabriele Mazzotta
> wrote:
> > On Monday 05 January 2015 14:24:30 Benjamin Tissoires wrote:
> >> Hi Gabriele,
> >>
> >> [Adding Peter and Hans as this change will impact both
> >>
On Sun, Jan 04, 2015 at 07:26:56PM +0100, Jiri Olsa wrote:
> On Sat, Dec 27, 2014 at 02:06:33PM +0900, Namhyung Kim wrote:
>
> SNIP
>
> > + return 0;
> > +
> > + fmt = zalloc(sizeof(*fmt));
> > + if (fmt == NULL) {
> > + pr_err("Memory allocation failed\n");
> > +
Enable early kprobes in Kconfig.
Signed-off-by: Wang Nan
---
arch/Kconfig | 12
1 file changed, 12 insertions(+)
diff --git a/arch/Kconfig b/arch/Kconfig
index 05d7a8a..06dff4b 100644
--- a/arch/Kconfig
+++ b/arch/Kconfig
@@ -46,6 +46,18 @@ config KPROBES
for kernel
From: Zidan Wang
When we want to use wm8960 codec, we should enable its MCLK in machine driver.
It's reasonable for wm8960 codec driver to manage its own MCLK.
When current bias_level is SND_SOC_BIAS_ON, it is preparing for a transition
away from ON. In this case, disable the codec mclk. When
Hi Jiri,
On Sun, Jan 04, 2015 at 07:16:40PM +0100, Jiri Olsa wrote:
> On Sat, Dec 27, 2014 at 02:06:32PM +0900, Namhyung Kim wrote:
>
> SNIP
>
> > if (!pairs_left || !pairs_right)
> > return pairs_left ? -1 : 1;
> >
> > - p_left = get_pair_data(left,
From: Olliver Schinagl
I probably have forgotten to use this macro for the of_match pointer, so
this patch adds the of_match_ptr macro.
Signed-off-by: Olliver Schinagl
---
drivers/misc/eeprom/sunxi_sid.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git
If kprobe is optimized before kprobe is initialized, there should
be only one core, the probed instruction is not armed with breakpoint,
so simply patch text is okay.
Signed-off-by: Wang Nan
---
arch/arm/probes/kprobes/opt-arm.c | 11 ++-
1 file changed, 10 insertions(+), 1 deletion(-)
Following patches will enable kprobe registering very early, before
kprobe system initialized. Arch code can use it to do special treatments
for such kprobes.
Signed-off-by: Wang Nan
---
include/linux/kprobes.h | 2 ++
kernel/kprobes.c| 2 +-
2 files changed, 3 insertions(+), 1
Introduces macros to genearte common early kprobe related resource
allocator.
All early kprobe related resources are statically allocated during
linking for each early kprobe slot. For each type of resource, a bitmap
is used to track allocation. __DEFINE_EKPROBE_ALLOC_OPS defines alloc
and free
This patch is the main logic of early kprobe.
If register_kprobe() is called before kprobes_initialized, an early
kprobe is allocated. Try to utilize existing OPTPROBE mechanism to
replace the target instruction by a branch instead of breakpoint,
because interrupt handlers may not been
On Mon, 2015-01-05 at 09:06 -0500, Aristeu Rozanski wrote:
> Hi,
> On Fri, Dec 19, 2014 at 01:26:59PM +0800, Huang Ying wrote:
> > In fact, I am not complaining :-), just FYI. As I said, this may be a
> > expected behavior because this is a Haswell machine and the Haswell
> > support was added in
This patch introduces EARLY_KPROBES_CODES_AREA in x86 vmlinux for early
kprobes.
Signed-off-by: Wang Nan
---
arch/x86/include/asm/insn.h| 7 ---
arch/x86/include/asm/kprobes.h | 45 ++
arch/x86/kernel/vmlinux.lds.S | 2 ++
3 files changed, 43
Enable early kprobes in Kconfig.
Signed-off-by: Wang Nan
---
arch/Kconfig | 12
1 file changed, 12 insertions(+)
diff --git a/arch/Kconfig b/arch/Kconfig
index 05d7a8a..06dff4b 100644
--- a/arch/Kconfig
+++ b/arch/Kconfig
@@ -46,6 +46,18 @@ config KPROBES
for kernel
Introduces early_slots_start/end and bitmap for struct kprobe_insn_cache
then uses previous introduced macro to generate allocator. This patch
makes get/free_insn_slot() and get/free_optinsn_slot() transparent to
early kprobes.
Signed-off-by: Wang Nan
---
include/linux/kprobes.h | 33
This patch shows the basic idea of usage of early kprobes. By adding
kernel cmdline options such as 'ekprobe=__alloc_pages_nodemask' or
'ekprobe=0xc00f3c2c', early kprobes are installed. When the probed
instructions get hit, a message is printed.
Signed-off-by: Wang Nan
---
kernel/kprobes.c |
When registering early kprobes, SMP should has not been enabled, so
doesn't require synchronization in text_poke_bp(). Simply memcpy is
enough.
Signed-off-by: Wang Nan
---
arch/x86/kernel/kprobes/opt.c | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git
In arm's vmlinux.lds, introduces code area inside text section.
Executable area used by early kprobes will be allocated from there.
Signed-off-by: Wang Nan
---
arch/arm/include/asm/kprobes.h | 29 +++--
arch/arm/kernel/vmlinux.lds.S | 2 ++
2 files changed, 29
Introduce a KPROBE_FLAG_EARLY for futher expansion. KPROBE_FLAG_EARLY
indicates a kprobe is installed at very early stage, its resources
should be allocated statically.
Signed-off-by: Wang Nan
---
include/linux/kprobes.h | 1 +
1 file changed, 1 insertion(+)
diff --git
This patch series shows early kprobe, a mechanism allows users to track
events at very early. It should be useful for optimization of system
booting. This can also be used by BSP developers to hook their platform
specific procedures at kernel booting stages after setup_arch().
This patch series
On Tuesday 06 January 2015 08:43 PM, Arnaldo Carvalho de Melo wrote:
Em Tue, Jan 06, 2015 at 07:22:10PM +0530, Vineet Gupta escreveu:
> Hi,
>
> This series based off linux-next of 20150105 allows us to build/use perf
> for ARC with uClibc based userland.
Do you have some ready made ARC VM
To be future-proof and for better readability the time comparisons are
modified to use time_before() instead of plain, error-prone math.
Signed-off-by: Asaf Vertz
---
drivers/block/rsxx/core.c |9 +
1 files changed, 5 insertions(+), 4 deletions(-)
diff --git
On Wed, Jan 7, 2015 at 5:16 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20150106:
>
> *crickets*
>
> Non-merge commits (relative to Linus' tree): 1350
> 1543 files changed, 41856 insertions(+), 24250 deletions(-)
>
Happy new year,
this release is a
From: Thomas Gleixner
No reason anymore to do GFP_ATOMIC allocations which are not harmful
in the normal bootup case, but matter in the physical hotplug
scenario.
Signed-off-by: Thomas Gleixner
Tested-by: Borislav Petkov
Acked-by: Joerg Roedel
Cc: Jiang Liu
Cc: x...@kernel.org
Link:
Refine enable_IR_x2apic() and related functions for better readability.
It also changes the way to handle IR in XAPIC mode when enabling X2APIC.
Previously it just skips X2APIC initialization without checking max CPU
APIC ID in system, which may cause problem if system has CPU with APIC
ID bigger
From: Joerg Roedel
IRQ remapping is only supported when all IOMMUs in the
system support it. So check if all IOMMUs in the system
support IRQ remapping before doing the allocations.
[Jiang]
1) Rebased onto v3.19.
2) Remove redundant check of ecap_ir_support(iommu->ecap) in function
When interrupt remapping hardware is not in X2APIC, CPU X2APIC mode
will be disabled if:
1) Maximum CPU APIC ID is bigger than 255
2) hypervisior doesn't support x2apic mode.
But we should only check whether hypervisor supports X2APIC mode when
hypervisor(CONFIG_HYPERVISOR_GUEST) is enabled,
From: Olliver Schinagl
Almost all of the speaker drivers under input manipulate the ev bits
directly, which is not needed, as there is a helper available.
This patch makes use of the helper for the speaker drivers.
Signed-off-by: Olliver Schinagl
---
drivers/input/misc/cm109.c | 4
Change variable disable_irq_remap to be static and simplify the code.
Signed-off-by: Jiang Liu
---
drivers/iommu/amd_iommu_init.c |6 +-
drivers/iommu/intel_irq_remapping.c |5 -
drivers/iommu/irq_remapping.c |3 +--
drivers/iommu/irq_remapping.h |2 --
Hi Arnaldo,
On Mon, Jan 05, 2015 at 09:49:24AM -0300, Arnaldo Carvalho de Melo wrote:
> Em Sun, Jan 04, 2015 at 12:01:26AM +0900, Namhyung Kim escreveu:
> > On Sat, Jan 3, 2015 at 11:25 AM, Arnaldo Carvalho de Melo
> > wrote:
> > > Em Mon, Dec 22, 2014 at 01:44:14PM +0900, Namhyung Kim escreveu:
Refine code by normailizing the way to detect whether IR is enabled.
Signed-off-by: Jiang Liu
---
drivers/iommu/irq_remapping.c | 38 ++
1 file changed, 14 insertions(+), 24 deletions(-)
diff --git a/drivers/iommu/irq_remapping.c
From: Joerg Roedel
This allows to get rid of the irq_remapping_supported()
function and all its call-backs into the Intel and AMD
IOMMU drivers.
Signed-off-by: Joerg Roedel
Signed-off-by: Jiang Liu
---
drivers/iommu/amd_iommu_init.c |3 +++
1 file changed, 3 insertions(+)
diff --git
Assign intel_irq_remap_ops to remap_ops only if
intel_irq_remap_ops.prepare() succeeds.
Signed-off-by: Jiang Liu
---
drivers/iommu/irq_remapping.c | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/drivers/iommu/irq_remapping.c b/drivers/iommu/irq_remapping.c
Simplify irq_remapping code by killing irq_remapping_supported() and
related interfaces.
Joerg posted a similar patch at https://lkml.org/lkml/2014/12/15/490,
so assume an signed-off from Joerg.
Signed-off-by: Jiang Liu
Signed-off-by: Joerg Roedel
---
arch/x86/include/asm/irq_remapping.h |
X2APIC will be disabled if user specifies "nox2apic" on kernel command
line, even when x2apic_preenabled is true. So correctly detect X2APIC
status by using x2apic_enabled() instead of x2apic_preenabled.
Signed-off-by: Jiang Liu
---
arch/x86/kernel/apic/apic.c |2 +-
1 file changed, 1
Local variable x2apic_enabled has been assigned to but never referred,
so kill it.
Signed-off-by: Jiang Liu
---
arch/x86/kernel/apic/apic.c |4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/arch/x86/kernel/apic/apic.c b/arch/x86/kernel/apic/apic.c
index
Currently if CPU supports X2APIC, IR hardware must work in X2APIC mode
or disabled. Change the code to support IR working in XAPIC mode when
CPU supports X2APIC. Then the CPU APIC driver will decide how to handle
such as configuration by:
1) Disabling X2APIC mode
2) Forcing X2APIC physical mode
Prepare for killing function irq_remapping_supported() by moving code
from intel_irq_remapping_supported() into intel_prepare_irq_remapping().
Combined with patch from Joerg at https://lkml.org/lkml/2014/12/15/487,
so assume an signed-off from Joerg.
Signed-off-by: Jiang Liu
Signed-off-by:
When kernel doesn't support X2APIC but BIOS has enabled X2APIC, system
may panic or hang without useful messages. On the other hand, it's
hard to dynamically disable X2APIC when CONFIG_X86_X2APIC is disabled.
So panic with a clear message in such a case.
System panics as below when X2APIC is
From: Thomas Gleixner
The whole iommu setup for irq remapping is a convoluted mess. The
iommu detect function gets called from mem_init() and the prepare
callback gets called from enable_IR_x2apic() for unknown reasons.
Of course AMD and Intel setup differs in nonsensical ways. Intels
prepare
From: Thomas Gleixner
enable_IR_x2apic() calls setup_irq_remapping_ops() which by default
installs the intel dmar remapping ops and then calls the amd iommu irq
remapping prepare callback to figure out whether we are running on an
AMD machine with irq remapping hardware.
Right after that it
When converting x86 to new hierarchy irqdoamin framework, Thomas noticed
that the interrupt remapping initialization flow is a little complex and
has troubles in memory allocation. Then there is a joint force to
simplify IR initialization flow, please refer to related threads at:
Remove unnecessary braces from single statement blocks.
Signed-off-by: Arjun AK
---
drivers/staging/ft1000/ft1000-pcmcia/ft1000_hw.c | 101 ---
1 file changed, 35 insertions(+), 66 deletions(-)
diff --git a/drivers/staging/ft1000/ft1000-pcmcia/ft1000_hw.c
On Tue, Jan 6, 2015 at 9:38 PM, Paolo Bonzini wrote:
>
>
> On 06/01/2015 17:56, Andy Lutomirski wrote:
>> Still no good. We can migrate a bunch of times so we see the same CPU
>> all three times
>
> There are no three times. The CPU you see here:
>
>>>
>>>
>>> // ... compute nanoseconds
Hi Liu Ying , Philipp:
On 2015年01月07日 10:39, Liu Ying wrote:
On 12/05/2014 02:22 PM, Andy Yan wrote:
We found Freescale imx6 and Rockchip rk3288 and Ingenic JZ4780
(Xburst/MIPS)
use the interface compatible Designware HDMI IP, but they also have some
lightly differences, such as phy pll
Hi Stephane,
On Tue, Jan 06, 2015 at 10:50:44AM -0500, Stephane Eranian wrote:
> On Mon, Jan 5, 2015 at 1:48 PM, Andi Kleen wrote:
> > > This also requires to handle multiple files and to find a
> > > corresponding machine state when processing samples. On a large
> > > profiling session, many
Add device tree node for the Secure Non-Volatile Storage
(SNVS) on the VF610 platform. The SNVS block also has a
Real Time Counter (RTC).
Signed-off-by: Sanchayan Maity
---
arch/arm/boot/dts/vf500.dtsi |4
arch/arm/boot/dts/vfxxx.dtsi | 14 ++
2 files changed, 18
Add support for clock gating of the SNVS peripheral.
Signed-off-by: Sanchayan Maity
---
arch/arm/mach-imx/clk-vf610.c |2 ++
include/dt-bindings/clock/vf610-clock.h |3 ++-
2 files changed, 4 insertions(+), 1 deletion(-)
diff --git a/arch/arm/mach-imx/clk-vf610.c
The following patch set adds support for clock gating
of the SNVS peripheral required on the Vybrid platform.
Also adds a device tree node for this peripheral.
This patchset was send before along with the patch which
had clock changes to the rtc-snvs driver. Since these could
not be merged then,
Hi Kirill,
On Tue, 06 Jan 2015 02:07:21 +0300
Kirill Tkhai wrote:
> On Пн, 2015-01-05 at 16:21 +0100, Luca Abeni wrote:
[...]
> > For reference, I attach the patch I am using locally (based on what
> > I suggested in my previous mail) and seems to work fine here.
> >
> > Based on your
At Tue, 6 Jan 2015 13:40:14 -0800,
Aaron Plattner wrote:
>
> Vendor ID 0x10de0072 is used by a yet-to-be-named GPU chip.
>
> Signed-off-by: Aaron Plattner
> ---
> Do you think it would make sense to add some kind of wildcard match for
> 0x10de* -> patch_nvhdmi?
Looking at the situation until
Hi Andi,
On Mon, Jan 05, 2015 at 07:48:11PM +0100, Andi Kleen wrote:
>
> Thanks for working on this. Haven't read any code, just
> some high level comments on the design.
Really appreciate it!
> >
> > So my approach is like this:
> >
> > Partially do stage 1 first - but only for meta events
Around Tue 06 Jan 2015 17:45:18 +0200 or thereabout, Michael S. Tsirkin wrote:
> While working on arch/avr32/include/asm/uaccess.h, I noticed
> that some macros within this header are made harder to read because they
> violate a coding style rule: space is missing after comma.
>
> Fix it up.
Around Tue 06 Jan 2015 17:44:50 +0200 or thereabout, Michael S. Tsirkin wrote:
> Align using tabs to make code prettier.
>
It is already aligned using tabs, but there is one too much. Thanks for
cleaning.
> Signed-off-by: Michael S. Tsirkin
>
Acked-by: Hans-Christian Egtvedt
> ---
>
Dear Gregory CLEMENT,
On Tue, 06 Jan 2015 23:00:54 +0100, Gregory CLEMENT wrote:
> On 06/01/2015 22:30, Ken Wilson wrote:
> > Create a new dt binding for the Armada 375 that supports up to
> > 3 chip selects but uses the same prescaler values and algorithm
> > as the basic orion binding.
>
>
On Tue, 6 Jan 2015, Catalin Marinas wrote:
> I think that's where the misunderstanding is. We don't have any idea
> how many times we go through the delay loop. We just go through the
> delay loop until the counter (driven by an independent frequency)
> changes X times. From arch/arm/lib/delay.c:
On Tue, Jan 06, 2015 at 10:17:32PM +0100, Bruno Prémont wrote:
>
> One big issue I see here is that you start dropping all events at a random
> point in time.
> You may end up within a gesture or just while a button is down and remain
> so until that same button gets pressed again on unmute.
>
>
On Tuesday 06 January 2015 08:08 PM, Rob Herring wrote:
> On Tue, Jan 6, 2015 at 7:59 AM, Vineet Gupta
> wrote:
>> 8250 earlycon is broken on multi-platform ARC because the UART clk
>> value (BASE_BAUD) is fixed at build time.
> Note that it should only be broken if you rely on the kernel to
On Mon, Jan 05, 2015 at 02:24:30PM -0500, Benjamin Tissoires wrote:
> Hi Gabriele,
>
> [Adding Peter and Hans as this change will impact both
> xf86-input-synaptics and libinput]
>
> On Sat, Dec 27, 2014 at 6:31 AM, Gabriele Mazzotta
> wrote:
> > Despite claiming to be able to report
On Wed, 7 Jan 2015, Rickard Strandqvist wrote:
> 2015-01-05 12:06 GMT+01:00 Arend van Spriel :
> > On 01/05/15 11:49, Kalle Valo wrote:
> >>
> >> Rickard Strandqvist writes:
> >>
> >>> As I hope you can see I have made some changes regarding the
> >>> subject-line. Thought it was an advantage
On Wed, Jan 07, 2015 at 12:10:18AM +0200, Michael S. Tsirkin wrote:
> Sam Ravnborg suggested packing single-lines cases in switch statements
> in nocheck uaccess macros makes for easier to read code.
>
> Suggested-by: Sam Ravnborg
> Signed-off-by: Michael S. Tsirkin
Acked-by: Sam Ravnborg
--
On Tue, Jan 06, 2015 at 11:39:59PM +0200, Michael S. Tsirkin wrote:
> Sam Ravnborg suggested packing single-line cases
> in nocheck switch statements makes for easier to
> read code.
>
> This is on top of arch/sparc: uaccess_64 macro whitespace fixes
> that I sent earlier.
>
> Suggested-by: Sam
Commit b81975eade8c ("x86, irq: Clean up irqdomain transition code")
breaks xen IRQ allocation because xen_smp_prepare_cpus() doesn't invoke
setup_IO_APIC(), so no irqdomains created for IOAPICs and
mp_map_pin_to_irq() fails at the very beginning.
Enhance xen_smp_prepare_cpus() to call
On Mon, Jan 05, 2015 at 05:04:55PM -0500, Benjamin Tissoires wrote:
> On Mon, Jan 5, 2015 at 5:00 PM, Gabriele Mazzotta
> wrote:
> > On Monday 05 January 2015 14:24:30 Benjamin Tissoires wrote:
> >> Hi Gabriele,
> >>
> >> [Adding Peter and Hans as this change will impact both
> >>
From: Brad Griffis
This patch makes the initial changes required to workaround TSC-false
pen-up interrupts. It is required to implement these changes in order to
remove udelay in the TSC interrupt handler and false pen-up events.
The charge step is to be executed immediately after sampling X+.
From: Brad Griffis
TSC interrupt handler had udelay to avoid reporting of false pen-up
interrupt to user space. This patch implements workaround suggesting in
Advisory 1.0.31 of silicon errata for am335x, thus eliminating udelay
and touchscreen lag. This also improves performance of touchscreen
This patch reads charge delay from tsc DT node and writes to
REG_CHARGEDELAY register. If the charge delay is not specified in DT
then default value of 0x400(CHARGEDLY_OPENDLY) is used.
Signed-off-by: Vignesh R
---
v6:
- Move Documentation from DT patch to driver code.
v5:
- print out a
In one shot mode, sequencer automatically disables all enabled steps at
the end of each cycle. (both ADC steps and TSC steps) Hence these steps
need not be saved in reg_se_cache for clearing these steps at a later
stage.
Also, when ADC wakes up Sequencer should not be busy executing any of the
Previously, delta filtering was applied TSC co-ordinate readouts before
reporting a single value to user space. This patch replaces delta filtering
with median filtering. Median filtering sorts co-ordinate readouts, drops min
and max values, and reports the average of remaining values. This method
The charge delay value is by default 0x400. But it can be set to lower
values on some boards, as long as false pen-ups are avoided. Lowering the
value increases the sampling rate (though current sampling rate is
sufficient for TSC operation). In some boards, the value has to be
increased to avoid
Currently kernel has set the bit SCTLR_EL1.SED, so the SETEND
instruction will be treated as UNALLOCATED; this error can be
reproduced when ARMv8 cpu runs with EL1/aarch64 and EL0/aarch32
mode, finally kernel will trap the exception if the userspace
libs use SETEND instruction.
So this patch
This series is rebase of v4 onto v3.19-rc1. It also fixes concerns
expressed on v4 wrt simultaneous use of IIO and TSC.
I have tested this patch series on am335x-evm and Beaglebone black
with lcd7-cape.
Note that, these patches do not work as expected on Beaglebone Black
with BB-View 4.3 Cape
> > +
> > +for (( BSIZE = 1024; BSIZE <= 4096; BSIZE *= 2 )); do
> > +
> > + length=$(($BLOCKS * $BSIZE))
> > + case $FSTYP in
> > + xfs)
> > + _scratch_mkfs -b size=$BSIZE >> $seqres.full 2>&1
> > + ;;
> > + ext4)
> > + _scratch_mkfs -b $BSIZE >> $seqres.full 2>&1
> > + ;;
> > +
> > }
> > break;
> > + case OP_INSERT_RANGE:
> > + if (!insert_range_calls) {
> > + log4(OP_SKIPPED, OP_INSERT_RANGE, offset, size);
> > + goto out;
> > + }
> > + break;
> > }
> >
> > switch (op) {
On Friday 02 January 2015 10:39 PM, Tony Lindgren wrote:
> * Vignesh R [141223 23:07]:
>> The charge delay value is by default 0x400. But it can be set to lower
>> values on some boards, as long as false pen-ups are avoided. Lowering the
>> value increases the sampling rate (though current
> On Fri, Jan 02, 2015 at 06:40:33PM +0900, Namjae Jeon wrote:
> > FALLOC_FL_INSERT_RANGE command is the opposite command of
> > FALLOC_FL_COLLAPSE_RANGE that is needed for advertisers or someone who want
> > to
> > add some data in the middle of file. FALLOC_FL_INSERT_RANGE will create
> >
>
> On Fri, Jan 02, 2015 at 06:42:51PM +0900, Namjae Jeon wrote:
> > This commit adds insert operation support for fsstress, which is
> > meant to exercise fallocate FALLOC_FL_INSERT_RANGE support.
> >
> > Signed-off-by: Namjae Jeon
> > Signed-off-by: Ashish Sangwan
> > ---
>
> It might be
>
> On Fri, Jan 02, 2015 at 06:40:54PM +0900, Namjae Jeon wrote:
> > This patch implements fallocate's FALLOC_FL_INSERT_RANGE for XFS.
> >
> > 1) Make sure that both offset and len are block size aligned.
> > 2) Update the i_size of inode by len bytes.
> > 3) Compute the file's logical block
Hi,
On Wed, Jan 07, 2015 at 10:53:52AM +0800, Wang Nan wrote:
> Ping...
Sorry for long delay.
>
> On 2014/12/29 16:14, Wang Nan wrote:
> > On 2014/12/29 15:56, Namhyung Kim wrote:
> >> Hi Wang,
> >>
> >> (Adding Arnaldo and Jiri to CC)
> >>
> >> On Sat, Dec 27, 2014 at 09:26:11AM +0800, Wang
From: Ryan Grimm
When unbinding and rebinding the driver on a system with a card in PHB0, this
error condition is reached after a few attempts:
ERROR: Bad of_node_put() on /pciex@3fffe4000
CPU: 0 PID: 3040 Comm: bash Not tainted 3.18.0-rc3-12545-g3627ffe #152
Call Trace:
[c00721acb5c0]
On 06/01/2015 19:26, Andy Lutomirski wrote:
> Don't you stil need:
>
> version++;
> write the rest;
> version++;
>
> with possible smp_wmb() in there to keep the compiler from messing around?
No, see my other reply.
Separating the version write is a real bug, but that should be all that
it's
Hi Pablo,
On Wed, Jan 7, 2015 at 4:17 AM, Pablo Neira Ayuso wrote:
> On Wed, Jan 07, 2015 at 03:03:20AM +0530, Rahul Sharma wrote:
>> ipv6_find_hdr() currently assumes that the next-header field in the
>> fragment header of the non-first fragment is the "protocol number of
>> the last header"
From: Amit Daniel Kachhap
Moving Exynos PMU specific header file into "include/linux/soc/samsung"
thus updated affected files under "mach-exynos" to use new location of
these header files.
Signed-off-by: Pankaj Dubey
Signed-off-by: Amit Daniel Kachhap
---
arch/arm/mach-exynos/exynos.c
This patch splits up mach-exynos/pmu.c file, and moves exynos4210,
exynos4412 and exynos4212 PMU configuration data and functions handing
data into a common exynos4 SoC specific PMU file mach-exynos/exynos4-pmu.c.
Signed-off-by: Pankaj Dubey
---
arch/arm/mach-exynos/Makefile | 2 +-
This patch splits up mach-exynos/pmu.c file, and moves exynos5420,
PMU configuration data and functions handing data into exynos5420
SoC specific PMU file mach-exynos/exynos5420-pmu.c.
Signed-off-by: Pankaj Dubey
---
arch/arm/mach-exynos/Makefile | 2 +-
This patch series is a part of continuation work from following series
[1] and [2].
1: exynos: Move pmu driver to driver/soc folder and add exynos7 support
http://www.spinics.net/lists/linux-samsung-soc/msg39797.html from Amit
Daniel Kacchap
2: soc: samsung: pmu: split up SoC specific PMU
This patch splits up mach-exynos/pmu.c file, and moves exynos5250,
PMU configuration data and functions handing data into exynos5250
SoC specific PMU file mach-exynos/exynos5250-pmu.c.
Signed-off-by: Pankaj Dubey
---
arch/arm/mach-exynos/Makefile | 4 +-
This patch moves Exynos PMU driver implementation from "arm/mach-exynos"
to "drivers/soc/samsung". This driver is mainly used for setting misc
bits of register from PMU IP of Exynos SoC which will be required to
configure before Suspend/Resume. Currently all these settings are done
in
This patch splits up mach-exynos/pmu.c file, and moves exynos3250 PMU
configuration data and functions handing those data into exynos3250
SoC specific PMU file mach-exynos/exynos3250-pmu.c.
Signed-off-by: Pankaj Dubey
---
arch/arm/mach-exynos/Makefile | 2 +-
On 06/01/2015 17:56, Andy Lutomirski wrote:
> Still no good. We can migrate a bunch of times so we see the same CPU
> all three times
There are no three times. The CPU you see here:
>>
>>
>> // ... compute nanoseconds from pvti and tsc ...
>> rmb();
>> } while(v !=
continue is not needed at the end of a for loop, also removed the
braces which were no longer required.
Signed-off-by: Sudip Mukherjee
---
v2: removed braces
drivers/video/fbdev/vt8500lcdfb.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git
From: Ian Munsie
An issue was introduced with "cxl: Unmap MMIO regions when detaching a
context" (b123429e6a9e8d03aacf888d23262835f0081448) where closing a
context normally could also unmap the problem state area of other
contexts currently using the AFU.
It was also discovered that after a
It is same as the last one I send to you yesterday.
The continuous memory that needed for data in this patchset:
RE: PAGE_SIZE, 4096 Bytes;
IRTE: 65536 * 16 ; 1M Bytes;
It should use same memory as the old versions of this patchset. The
changes for the last version do not need more memory.
On Tuesday 06 January 2015 08:43 PM, Arnaldo Carvalho de Melo wrote:
Em Tue, Jan 06, 2015 at 07:22:10PM +0530, Vineet Gupta escreveu:
> Hi,
>
> This series based off linux-next of 20150105 allows us to build/use perf
> for ARC with uClibc based userland.
Do you have some ready made ARC VM
On 01/07/15 at 12:11pm, Li, ZhenHua wrote:
> Many thanks to Takao Indoh and Baoquan He, for your testing on more
> different systems.
>
> The calling of flush functions are added to this version.
>
> The usage of __iommu_flush_cache function :
> 1. Fixes a dump on Takao's system.
> 2. Reduces
x86 maintainers, could you please consider taking my patch?
There have been several reports now regarding this issue, all could be
fixed using my patch.
Juergen
On 12/17/2014 05:57 AM, Alok Kataria wrote:
Hi,
On Tue, 2014-12-16 at 10:58 +0100, Juergen Gross wrote:
VMWare seems not to
On 01/06/2015 05:06 PM, Jon Masters wrote:
> Hi Arnd,
>
> Happy New Year!
>
> On 01/06/2015 02:21 PM, Arnd Bergmann wrote:
>> On Tuesday 06 January 2015 11:24:43 Jon Masters wrote:
>>> On 01/06/2015 06:20 AM, Catalin Marinas wrote:
>>>
Now, what's preventing a vendor firmware from providing
On Mon, Jan 5, 2015 at 11:41 PM, Sasha Levin wrote:
> If we failed loading the firmware we have to make sure it leaves the pending
> list if abort wasn't executed for it.
>
> Otherwise we'd free an object still on the pending list and corrupt it.
>
> Signed-off-by: Sasha Levin
> ---
>
On Mon, Jan 5, 2015 at 8:01 AM, Vlastimil Babka wrote:
>
> Hm, nope. The !CONFIG_COMPACTION variant of try_to_compact_pages() is static
> inline that returns COMPACT_CONTINUE, which is defined in compaction.h.
> Another solution is to add a "forward" declaration (not actually followed
> later
>
1 - 100 of 2488 matches
Mail list logo
