On 7.12.2016 00:00, Sasikumar Chandrasekaran wrote:
> Update Linux driver to use new pdTargetId field for JBOD target ID
>
> This patch is depending on patch 9
>
> Signed-off-by: Sasikumar Chandrasekaran
Reviewed-by: Tomas Henzl
Tomas
On 7.12.2016 00:00, Sasikumar Chandrasekaran wrote:
> Upgrade driver version.
>
> This patch is depending on patch 10
>
> Signed-off-by: Sasikumar Chandrasekaran
> ---
> drivers/scsi/megaraid/megaraid_sas.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/scsi/
Error - Complex macro not in parentheses and trailing whitespace
Signed-off-by: Manoj Sawai
---
drivers/staging/ks7010/ks7010_sdio.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/ks7010/ks7010_sdio.h
b/drivers/staging/ks7010/ks7010_sdio.h
index 0f5fd848
On Fri, Dec 09, 2016 at 12:10:20AM +0530, Hari Bathini wrote:
> Hi Peter,
>
>
> Sorry for taking so long to respond...
>
>
> On Thursday 24 November 2016 08:40 PM, Peter Zijlstra wrote:
> >On Thu, Nov 24, 2016 at 08:14:29PM +0530, Hari Bathini wrote:
> >>@@ -862,6 +875,19 @@ enum perf_event_typ
version 6:
- rename stm32-gptimer in stm32-timers.
- change "st,stm32-gptimer" compatible to "st,stm32-timers".
- modify "st,breakinput" parameter in pwm part.
- split DT patch in 2
version 5:
- fix comments done on version 4
- rebased on kernel 4.9-rc8
- change nodes names and re-order then by ad
Add bindings information for STM32 Timers
version 6:
- rename stm32-gtimer to stm32-timers
- change compatible
- add description about the IPs
version 2:
- rename stm32-mfd-timer to stm32-gptimer
- only keep one compatible string
Signed-off-by: Benjamin Gaignard
---
.../devicetree/bindings/mfd
Define bindings for STM32 timer trigger
version 4:
- remove triggers enumeration from DT
- add reg parameter
version 3:
- change file name
- add cross reference with mfd bindings
version 2:
- only keep one compatible
- add DT parameters to set lists of the triggers:
one list describe the trigg
Add Timers and it sub-nodes into DT for stm32f429 family.
version 6:
- split patch in two: one for SoC family and one for stm32f469
discovery board.
version 5:
- rename gptimer node to timers
- re-order timers node par addresses
version 4:
- remove unwanted indexing in pwm@ and timer@ node nam
Define bindings for pwm-stm32
version 6:
- change st,breakinput parameter format to make it usuable on stm32f7 too.
version 2:
- use parameters instead of compatible of handle the hardware configuration
Signed-off-by: Benjamin Gaignard
---
.../devicetree/bindings/pwm/pwm-stm32.txt | 3
Define and enable pwm1 and pwm3 for stm32f469 discovery board
Signed-off-by: Benjamin Gaignard
---
arch/arm/boot/dts/stm32f469-disco.dts | 28
1 file changed, 28 insertions(+)
diff --git a/arch/arm/boot/dts/stm32f469-disco.dts
b/arch/arm/boot/dts/stm32f469-disco.dt
This driver adds support for PWM driver on STM32 platform.
The SoC have multiple instances of the hardware IP and each
of them could have small differences: number of channels,
complementary output, auto reload register size...
version 6:
- change "st,breakinput" parameter to make it usuable for s
From: Colin Ian King
kcontrol->private_value is being kfree'd after kcontrol has been freed
(in previous call to snd_ctl_remove). Instead, fix this by kfreeing
the private_value before kcontrol.
CoverityScan CID#1388311 "Read from pointer after free"
Fixes: eea3dd4f1247a ("ASoC: topology: Only
This hardware block could at used at same time for PWM generation
and IIO timers.
PWM and IIO timer configuration are mixed in the same registers
so we need a multi fonction driver to be able to share those registers.
version 6:
- rename files to stm32-timers
- rename functions to stm32_timers_xxx
Timers IPs can be used to generate triggers for other IPs like
DAC, ADC or other timers.
Each trigger may result of timer internals signals like counter enable,
reset or edge, this configuration could be done through "master_mode"
device attribute.
A timer device could be triggered by other timers
The number of probe hits is stored in a percpu variable and therefore
can't be read directly. Add a helper method trace_kprobe_nhit() that
performs the required calculation.
It will be used in a follow-up commit that changes kprobe selftests to
verify the number of probe hits.
Signed-off-by: Marc
Commit 265a5b7ee3eb ("kprobes/trace: Fix kprobe selftest for gcc 4.6")
has added __used attribute to kprobe_trace_selftest_target to ensure
that the method is listed in kallsyms table.
However, even though the method remains in the kernel image, the actual
call is optimised away as there are no si
Hello, Linus.
This is quite late but SCT Write Same support added during this cycle
is broken subtly but seriously and it'd be best to disable it before
v4.9 gets released.
This pull request contains two commits - one low impact sata_mv fix
and the mentioned disabling of SCT Write Same.
Thanks.
Hello there,
as this is a thread about ath9k and ARM64, i'm not sure if i should
answer here or not, but i have similar "stalls" with ath9k on x86_64
(starting with 4.9rc), stack trace is posted down below where the
original ARM64 stall traces are.
Greetings,
Tobias
On 08.12.2016 18:36, K
On Fri, Dec 9, 2016 at 6:17 AM, Jiri Kosina wrote:
> On Fri, 2 Dec 2016, Brian Norris wrote:
>
>> From: Caesar Wang
>>
>> Document a "vdd-supply" and an initialization delay. Can be used for
>> powering on/off a HID.
>>
>> Signed-off-by: Caesar Wang
>> Cc: Rob Herring
>> Cc: Jiri Kosina
>> Cc:
This patch fix the checkpatch warning "Please don't use multiple blank lines"
Signed-off-by: Corentin Labbe
---
drivers/char/hw_random/core.c | 5 -
1 file changed, 5 deletions(-)
diff --git a/drivers/char/hw_random/core.c b/drivers/char/hw_random/core.c
index d2d2c89..00cbb81 100644
--- a/
This patch move the define for hwrng's miscdev minor number to
include/linux/miscdevice.h.
It's better that all minor number are in the same place.
Rename it to HWRNG_MINOR (from RNG_MISCDEV_MINOR) in he process since
no other miscdev define have MISCDEV in their name.
Signed-off-by: Corentin Labb
linux/fs.h and linux/sched.h are useless for hw_random/core.c.
This patch remove them.
Signed-off-by: Corentin Labbe
---
drivers/char/hw_random/core.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/char/hw_random/core.c b/drivers/char/hw_random/core.c
index 5c654b5..85c9ab3 100644
This patch fix the checkpatch warning about asm/uaccess.h.
In the same time, we sort the headers in alphabetical order.
Signed-off-by: Corentin Labbe
---
drivers/char/hw_random/core.c | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/drivers/char/hw_random/core
This patch remove the unused PFX macro.
Signed-off-by: Corentin Labbe
---
drivers/char/hw_random/core.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/char/hw_random/core.c b/drivers/char/hw_random/core.c
index 1e1e385..5c654b5 100644
--- a/drivers/char/hw_random/core.c
+++ b/drivers
checkpatch have lot of complaint about header.
Furthermore, the header have some offtopic/useless information.
This patch rewrite a proper header.
Signed-off-by: Corentin Labbe
---
drivers/char/hw_random/core.c | 38 +-
1 file changed, 9 insertions(+), 29 del
Em Fri, Dec 09, 2016 at 11:36:18AM +0800, Wangnan (F) escreveu:
>
>
> On 2016/12/9 10:46, Joe Stringer wrote:
> > The map_flags argument to bpf_create_map() was previously not exposed.
> > By exposing it, users can access flags such as whether or not to
> > preallocate the map.
> >
> > Signed-of
This patch fix the checkpatch warning "Comparison to NULL could be written
"!ptr"
Signed-off-by: Corentin Labbe
---
drivers/char/hw_random/core.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/char/hw_random/core.c b/drivers/char/hw_random/core.c
index 00cbb81..70
On 12/7/2016 7:19 AM, Matt Fleming wrote:
> On Wed, 09 Nov, at 06:36:31PM, Tom Lendacky wrote:
>> Boot data (such as EFI related data) is not encrypted when the system is
>> booted and needs to be accessed unencrypted. Add support to apply the
>> proper attributes to the EFI page tables and to the
Fixes sparse warning:
fs/ecryptfs/inode.c:1142:28: warning: symbol 'ecryptfs_xattr_handler'
was not declared. Should it be static?
Signed-off-by: Geliang Tang
---
fs/ecryptfs/inode.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/ecryptfs/inode.c b/fs/ecryptfs/inode.c
i
Hi Andy,
I am hitting the following
[ 570.715345] BUG: using smp_processor_id() in preemptible [] code:
umount/6193
[ 570.716880] caller is debug_smp_processor_id+0x17/0x19
[ 570.717876] CPU: 2 PID: 6193 Comm: umount Tainted: GW
4.9.0-rc8-nofstest4-next-20161209-00012
From: "Steven Rostedt (Red Hat)"
If one of the events within a system fails to enable when "1" is written
to the system "enable" file, it should return an error. Note, some events
may still be enabled, but the user should know that something did go wrong.
Signed-off-by: Steven Rostedt
---
kern
From: "Steven Rostedt (Red Hat)"
Trace events are enabled very early on boot up via the boot command line
parameter. The benchmark tool creates a new thread to perform the trace
event benchmarking. But at start up, it is called before scheduling is set
up and because it creates a new thread befor
From: "Steven Rostedt (Red Hat)"
Instead of using get_user_pages_fast() and kmap_atomic() when writing
to the trace_marker file, just allocate enough space on the ring buffer
directly, and write into it via copy_from_user().
Writing into the trace_marker file use to allocate a temporary buffer
t
From: "Steven Rostedt (Red Hat)"
With new binutils, gcc may get smart with its optimization and change a jmp
from a 5 byte jump to a 2 byte one even though it was jumping to a global
function. But that global function existed within a 2 byte radius, and gcc
was able to optimize it. Unfortunately,
From: "Steven Rostedt (Red Hat)"
The trace event start up selftests fails when the trace benchmark is
enabled, because it is disabled during boot. It really only needs to be
disabled before scheduling is set up, as it creates a thread.
Signed-off-by: Steven Rostedt
---
kernel/trace/trace_bench
From: "Steven Rostedt (Red Hat)"
Some tracepoints have a registration function that gets enabled when the
tracepoint is enabled. There may be cases that the registraction function
must fail (for example, can't allocate enough memory). In this case, the
tracepoint should also fail to register, oth
From: "Steven Rostedt (Red Hat)"
Both the wakeup and irqsoff tracers can use the function graph tracer when
the display-graph option is set. The problem is that they ignore the notrace
file, and record the entry of functions that would be ignored by the
function_graph tracer. This causes the trac
There are two patches that are marked for stable. But since Linus will
hopefully open the merge window very soon, I figured I let those changes
sit in linux-next for a week before pushing to Linus. They are not that
critical as they are old bugs, and require root privilege to abuse.
git://git.ke
From: "Steven Rostedt (Red Hat)"
Currently both the wakeup and irqsoff traces do not handle set_graph_notrace
well. The ftrace infrastructure will ignore the return paths of all
functions leaving them hanging without an end:
# echo '*spin*' > set_graph_notrace
# cat trace
[...]
_
Use kobj_to_dev() instead of open-coding it.
Signed-off-by: Geliang Tang
---
drivers/scsi/qla2xxx/qla_attr.c | 42 ++---
drivers/scsi/qla4xxx/ql4_attr.c | 6 ++
2 files changed, 16 insertions(+), 32 deletions(-)
diff --git a/drivers/scsi/qla2xxx/qla_attr
On 12/08/2016 11:33 PM, Ingo Molnar wrote:
> * Boris Ostrovsky wrote:
>
>> The new Xen PVH entry point requires page tables to be setup by the
>> kernel since it is entered with paging disabled.
>>
>> Pull the common code out of head_32.S so that mk_early_pgtbl_32 can be
>> invoked from both the n
From: Markus Elfring
Date: Thu, 8 Dec 2016 18:25:13 +0100
The kfree() function was called in one case by the
gb_camera_configure_streams() function during error handling
even if the passed variable contained a null pointer.
This issue was detected by using the Coccinelle software.
Adjust a jump
Correcting Manohar Mail ID.
> Hello there,
>
> as this is a thread about ath9k and ARM64, i'm not sure if i should
> answer here or not, but i have similar "stalls" with ath9k on x86_64
> (starting with 4.9rc), stack trace is posted down below where the
> original ARM64 stall traces are.
>
> Gr
The question is how to provide a similar guarantee if a different way?
As a tool to aid distro reviewers, modversions has some value, but the
debug info parsing tools that have been mentioned in this thread seem
superior (not that I've tested them).
On the other hand the big advantage of modvers
From: Markus Elfring
Date: Fri, 9 Dec 2016 13:46:25 +0100
* Multiplications for the size determination of memory allocations
indicated that array data structures should be processed.
Thus use the corresponding function "kcalloc".
This issue was detected by using the Coccinelle software.
*
On Thu, 8 Dec 2016, Rob Herring wrote:
> > And if tomorrow there is Elan device that is drop-in compatible (same
> > connector, etc) with Wacom i2c-hid, will you ask for Elan-specific
> > binding? Atmel? Weida? They all need to be powered up ultimately.
>
> Yes, I will.
What advantage does th
On Thu, Dec 8, 2016 at 12:12 PM, Dmitry Torokhov
wrote:
> On Thu, Dec 08, 2016 at 10:26:41AM -0600, Rob Herring wrote:
>> On Thu, Dec 8, 2016 at 10:13 AM, Dmitry Torokhov
>> wrote:
>> > On December 8, 2016 8:03:06 AM PST, Rob Herring wrote:
>> >>On Thu, Dec 8, 2016 at 9:41 AM, Benjamin Tissoires
On Fri, 9 Dec 2016 14:37:47 +0800
Cao jin wrote:
> I am little confused too, even not sure if we are talking the same
> *fatal error*, I am talking the fatal error defined in PCI Express spec,
> chapter 6.2.2.2.1:
Therein lies my original discomfort with the change; it didn't seem to
make sense
From: Markus Elfring
Date: Fri, 9 Dec 2016 14:36:16 +0100
A return value was not checked after a call of the function "kstrndup".
This issue was detected by using the Coccinelle software.
Add a bit of exception handling.
Fixes: 2870b52bae4c81823ffcb3ed2b0626fb39d64f48 ("greybus: lights: add lig
From: Markus Elfring
Date: Fri, 9 Dec 2016 15:25:35 +0100
A few update suggestions were taken into account
from static source code analysis.
Markus Elfring (4):
One function call less in gb_camera_configure_streams() after error detection
light: Use kcalloc() in two functions
Check return
From: Markus Elfring
Date: Fri, 9 Dec 2016 15:04:24 +0100
* A multiplication for the size determination of a memory allocation
indicated that an array data structure should be processed.
Thus use the corresponding function "kcalloc".
This issue was detected by using the Coccinelle software
In early boot code level2_kernel_pgt is used to map kernel text. And its
size varies according to KERNEL_IMAGE_SIZE and fixed at compiling time.
In fact we can make it always take 512 entries of one whole page table,
because later function cleanup_highmap will clean up the unused entries.
With the
The current kernel sets KERNEL_IMAGE_SIZE as 1G as long as CONFIG_RANDOMIZE_BASE
is enabled, though people specify "nokaslr" into cmdline to disable kaslr
explicitly. This could be a wrong behaviour. CONFIG_RANDOMIZE_BASE should only
decide if KASLR code need be compiled in. If user specify "nokasl
X86 64 kernel takes KERNEL_IMAGE_SIZE as the kernel text mapping size,
and it's fixed as compiling time, changing from 512M to 1G as long as
CONFIG_RANDOMIZE_BASE is enabled, though people specify kernel option
"nokaslr" explicitly.
This could be a wrong behaviour. CONFIG_RANDOMIZE_BASE should onl
Hi Krzysztof,
On 12/09/2016 01:43 AM, Krzysztof Opasiak wrote:
> FYI to the list for next generations;)
>
>
> Forwarded Message
> Subject: Antwort: Re: vUDC
> Date: Fri, 9 Dec 2016 09:00:04 +0100
> From: Elen Niedermeyer
> To: Krzysztof Opasiak
>
>
> Hi,
>
> so your script
On 2016-12-08 00:29:29 [+0100], Rafael J. Wysocki wrote:
> Agreed, but the bug fixed by the first hunk is real too. I'd fix it a bit
> differently, though:
>
> Tentatively-signed-off-by: Rafael J. Wysocki
Is there anything you want me to do here? The hunk in
acpi_cppc_processor_exit() is unchan
On Fri, Dec 09, 2016 at 03:32:38PM +0100, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Fri, 9 Dec 2016 15:25:35 +0100
>
> A few update suggestions were taken into account
> from static source code analysis.
Again, nope, sorry, not going to even look at these...
On 09.12.16 21:15:12, Yisheng Xie wrote:
> For invalid pages, their zone and node information is not initialized, and it
> do have risk to trigger the BUG_ON, so I have a silly question,
> why not just change the BUG_ON:
We need to get the page handling correct. Modifying the BUG_ON() just
hides t
On 9 December 2016 at 06:54, Kefeng Wang wrote:
> Let's keep consistent when print dmi_ids_string between SMBIOS 2.x
> and SMBIOS 3.x, and always show the system identification string,
> like Vendor, Product/Board name and BIOS infos.
>
Are you saying the printk(KERN_DEBUG) was inconsistent with
On 09.12.16 20:14:24, Yisheng Xie wrote:
> We have merged your patch to 4.9.0-rc8, however we still meet the similar
> problem
> on our D05 board:
I assume you can reliable trigger the bug. Can you add some debug
messages that show the pfn number, node id, memory range. Also, add to
kernel parame
On Thu, Dec 08 2016, Arvind Yadav wrote:
> Here, f_acm,f_ecm and f_msg needs to be checked for being NULL
> in nokia_bind_config() before calling usb_add_function(),
> otherwise kernel can run into a NULL-pointer dereference.
>
> f_phonet, f_obex1 and f_obex2 need to be checked for NULL
> in nokia_
Em Thu, Dec 08, 2016 at 06:46:19PM -0800, Joe Stringer escreveu:
> This declaration was made in samples/bpf/libbpf.c for convenience, but
> there's already one in tools/perf/perf-sys.h. Reuse that one.
>
> Signed-off-by: Joe Stringer
> ---
> v3: First post.
> ---
> samples/bpf/Makefile
From: Colin Ian King
The check to see if ret is non-zero and return this rather than count
is redundant in two occassions. It is redundant because prior to this
check, the return code ret is already checked for a non-zero error
return value and we return from the function at that point.
Signed-
On Fri, Dec 9, 2016 at 8:36 AM, Jiri Kosina wrote:
> On Thu, 8 Dec 2016, Rob Herring wrote:
>
>> > And if tomorrow there is Elan device that is drop-in compatible (same
>> > connector, etc) with Wacom i2c-hid, will you ask for Elan-specific
>> > binding? Atmel? Weida? They all need to be powered u
On Fri, Dec 9, 2016 at 3:45 PM, Sebastian Andrzej Siewior
wrote:
> On 2016-12-08 00:29:29 [+0100], Rafael J. Wysocki wrote:
>> Agreed, but the bug fixed by the first hunk is real too. I'd fix it a bit
>> differently, though:
>>
>> Tentatively-signed-off-by: Rafael J. Wysocki
>
> Is there anythin
On 12/04/2016 08:03 PM, Jiancheng Xue wrote:
> Hi Arnd,
>
> On 2016/10/17 21:48, Arnd Bergmann wrote:
>> On Monday, October 17, 2016 8:07:03 PM CEST Pan Wen wrote:
>>> Add support for some HiSilicon SoCs which depend on ARCH_MULTI_V5.
>>>
>>> Signed-off-by: Pan Wen
>>>
>>
>> Looks ok. I've added
Em Thu, Dec 08, 2016 at 06:46:13PM -0800, Joe Stringer escreveu:
> (Was "libbpf: Synchronize implementations")
>
> Update tools/lib/bpf to provide the remaining bpf wrapper pieces needed by the
> samples/bpf/ code, then get rid of all of the duplicate BPF libraries in
> samples/bpf/libbpf.[ch].
>
From: Colin Ian King
Trivial fix to spelling mistake "doen't" to "doesn't" in pr_err message
Signed-off-by: Colin Ian King
---
drivers/firmware/efi/esrt.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/firmware/efi/esrt.c b/drivers/firmware/efi/esrt.c
index 1491407
[3.553354] Modules linked in:
[3.554032] CPU: 3 PID: 1568 Comm: modprobe Not tainted
4.9.0-rc8-nofstest5-next-20161209-00013-g3134766e941a #1018
[3.556099] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS
1.9.3-20161025_171302-gandalf 04/01/2014
[3.557330] Call Trace:
[3.557330
Em Wed, Dec 07, 2016 at 12:26:10PM +0900, Masami Hiramatsu escreveu:
> Hello Alexis,
>
> On Sat, 26 Nov 2016 01:58:03 +0100
> Alexis Berlemont wrote:
>
> > An sdt probe can be associated with arguments but they were not passed
> > to the user probe tracing interface (uprobe_events); this patch a
On 12/08/16 22:40, Madhani, Himanshu wrote:
> We’ll take a look and send patches to resolve these warnings.
Thanks!
Bart.
Hi Linus, please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm libnvdimm-fixes
...to receive several fixes to the DSM (ACPI device specific method)
marshaling implementation.
I consider these urgent enough to send for 4.9 consideration since they
fix the kernel's handl
Hi Jie,
I don't think we have the need to create the "dwc" subdirectory under
"synopsys".
Its preferable to have them directly under drivers/net/ethernet/synopsys.
Regards,
C.Palminha
On 07-12-2016 03:57, Jie Deng wrote:
> This series provides the support for 25/40/50/100 GbE
> devices using Sy
On Thu, Dec 08, 2016 at 05:56:54PM +0100, Vincent Guittot wrote:
> @@ -5449,14 +5456,32 @@ find_idlest_group(struct sched_domain *sd, struct
> task_struct *p,
> }
>
> /* Adjust by relative CPU capacity of the group */
> - avg_load = (avg_load * SCHED_CAPAC
Hi Wang,
On Fri, 9 Dec 2016 14:54:07 +0800, Kefeng Wang wrote:
> Let's keep consistent when print dmi_ids_string between SMBIOS 2.x
> and SMBIOS 3.x, and always show the system identification string,
> like Vendor, Product/Board name and BIOS infos.
>
> Signed-off-by: Kefeng Wang
> ---
> driver
Hi Arnaldo,
On 12/09/2016 04:09 PM, Arnaldo Carvalho de Melo wrote:
Em Thu, Dec 08, 2016 at 06:46:13PM -0800, Joe Stringer escreveu:
(Was "libbpf: Synchronize implementations")
Update tools/lib/bpf to provide the remaining bpf wrapper pieces needed by the
samples/bpf/ code, then get rid of all
+ Vladimir
2016-12-01 14:48 GMT+01:00 Benjamin Gaignard :
> commit ab6494f0c96f ("nommu: Add noMMU support to the DMA API") have
> add CONFIG_MMU compilation flag but that prohibit to use dma_mmap_wc()
> when the platform doesn't have MMU.
>
> This patch call vm_iomap_memory() in noMMU case to tes
On Thu, Dec 08, 2016 at 09:05:05PM +0100, Borislav Petkov wrote:
> On Thu, Dec 08, 2016 at 07:21:37PM +0300, Kirill A. Shutemov wrote:
> > 5-level paging support is required from hardware when compiled with
> > CONFIG_X86_5LEVEL=y. We may implement runtime switch support later.
> >
> > Signed-off-
On 09/12/16 15:27, Benjamin Gaignard wrote:
> + Vladimir
I'm not in DMA, but I can see that with your patch it deviates from
dma_common_mmap(), can you give more context, please?
Cheers
Vladimir
>
> 2016-12-01 14:48 GMT+01:00 Benjamin Gaignard :
>> commit ab6494f0c96f ("nommu: Add noMMU support
> I am able to reproduce it on AMD HW using kvm-unit-tests. Looking at
> test, the initial thought is "push mem" has two operands (the memory
> being pushed and the stack pointer). The provided GPA could be either
> one of those.
Aha, this makes sense---and it's easy to handle too, since you can
2016-12-09 16:36 GMT+01:00 Vladimir Murzin :
> On 09/12/16 15:27, Benjamin Gaignard wrote:
>> + Vladimir
>
> I'm not in DMA, but I can see that with your patch it deviates from
> dma_common_mmap(), can you give more context, please?
I'm working on ARM platform with MMU (stm32f4) to enable display
On Fri, 2016-12-09 at 13:33 +1000, Nicholas Piggin wrote:
>
> Well I simply tested the outcome. If you have:
>
> struct blah {
> int x;
> };
> int foo(struct blah *blah)
> {
> return blah->x;
> }
> EXPORT(foo);
>
> $ nm vmlinux | grep __crc_foo
> a0cf13a0 A __crc_foo
>
> Now change
Acked-by: Rob Herring
Signed-off-by: Olimpiu Dejeu
---
v1 => v2:
- Version updated to match other patch in set. No other changes.
.../bindings/leds/backlight/arcxcnn_bl.txt | 31 ++
1 file changed, 31 insertions(+)
create mode 100644
Documentation/devicetree/bindi
Signed-off-by: Olimpiu Dejeu
---
v1 => v2:
- Removed "magic numbers" to initialize registers
- Cleaned up device tree bindings
- Fixed code style to address comments and pass "checkpatch"
- Removed unneeded debug and testing code
drivers/video/backlight/Kconfig | 7 +
drivers/video/backl
On Thu, Dec 08, 2016 at 04:14:17PM -0800, Andi Kleen wrote:
> From: Andi Kleen
>
> An earlier patch allowed enabling PT and LBR at the same
> time on Goldmont. However it also allowed enabling BTS and LBR
> at the same time, which is still not supported. Fix this by
> bypassing the check only for
Joel,
A couple of minor nits below (none of them are real blockers), other
than that looks good.
On Thu, Dec 8, 2016 at 9:35 PM, Joel Holdsworth
wrote:
> The Lattice iCE40 is a family of FPGAs with a minimalistic architecture
> and very regular structure, designed for low-cost, high-volume consu
On 09.12.2016 14:40, Michal Hocko wrote:
On Fri 09-12-16 08:06:25, Gerhard Wiesinger wrote:
Hello,
same with latest kernel rc, dnf still killed with OOM (but sometimes
better).
./update.sh: line 40: 1591 Killed ${EXE} update ${PARAMS}
(does dnf clean all;dnf update)
Linux dat
On Fri, 9 Dec 2016 15:36:04 +0100
Stanislav Kozina wrote:
> The question is how to provide a similar guarantee if a different way?
> >>> As a tool to aid distro reviewers, modversions has some value, but the
> >>> debug info parsing tools that have been mentioned in this thread seem
> >>>
On 09.12.2016 16:52, Gerhard Wiesinger wrote:
On 09.12.2016 14:40, Michal Hocko wrote:
On Fri 09-12-16 08:06:25, Gerhard Wiesinger wrote:
Hello,
same with latest kernel rc, dnf still killed with OOM (but sometimes
better).
./update.sh: line 40: 1591 Killed ${EXE} update
${P
On Wed, Nov 23, 2016 at 4:25 AM, Sudeep Holla wrote:
>
>
> On 22/11/16 21:35, Rob Herring wrote:
>>
>> On Tue, Nov 22, 2016 at 12:44 PM, Frank Rowand
>> wrote:
>
>
> [...]
>
>>>
>>> This patch adds a function that leads to conflating the "model" property
>>> and the "compatible" property. This le
On Sat, Dec 10, 2016 at 01:56:53AM +1000, Nicholas Piggin wrote:
> On Fri, 9 Dec 2016 15:36:04 +0100
> Stanislav Kozina wrote:
>
> > The question is how to provide a similar guarantee if a different way?
> >
> > >>> As a tool to aid distro reviewers, modversions has some value, but t
On 9 December 2016 at 15:11, Colin King wrote:
> From: Colin Ian King
>
> Trivial fix to spelling mistake "doen't" to "doesn't" in pr_err message
>
> Signed-off-by: Colin Ian King
Applied, thanks.
> ---
> drivers/firmware/efi/esrt.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
>
Hi,
On Thu, Dec 8, 2016 at 8:01 AM, Rob Herring wrote:
>> Just my $0.02. Feel free to ignore.
>>
>> One thought is that I would say that the need to power on the device
>> explicitly seems more like a board level difference and less like a
>> difference associated with a particular digitizer. S
On Tue, Dec 06, 2016 at 02:14:42PM -0500, Waiman Long wrote:
> A number of cmpxchg calls in qspinlock_paravirt.h were replaced by more
> relaxed versions to improve performance on architectures that use LL/SC.
I would feel so much better if each change were to have some rationale
included. Either
On 09.12.2016 14:40, Michal Hocko wrote:
On Fri 09-12-16 08:06:25, Gerhard Wiesinger wrote:
Hello,
same with latest kernel rc, dnf still killed with OOM (but sometimes
better).
./update.sh: line 40: 1591 Killed ${EXE} update ${PARAMS}
(does dnf clean all;dnf update)
Linux dat
On Fri 09-12-16 16:52:07, Gerhard Wiesinger wrote:
> On 09.12.2016 14:40, Michal Hocko wrote:
> > On Fri 09-12-16 08:06:25, Gerhard Wiesinger wrote:
> > > Hello,
> > >
> > > same with latest kernel rc, dnf still killed with OOM (but sometimes
> > > better).
> > >
> > > ./update.sh: line 40: 1591
On 12/09/2016 11:05 AM, Peter Zijlstra wrote:
> On Tue, Dec 06, 2016 at 02:14:42PM -0500, Waiman Long wrote:
>> A number of cmpxchg calls in qspinlock_paravirt.h were replaced by more
>> relaxed versions to improve performance on architectures that use LL/SC.
> I would feel so much better if each c
[resending an plain test]
Hello,
While running syzkaller fuzzer I am getting tasks deadlocked at the
following stacks. Seems that they are waiting for each other:
# cat /proc/6715/task/*/stack
[] __synchronize_srcu+0x2f8/0x4a0 kernel/rcu/srcu.c:448
[] synchronize_srcu_expedited+0x13/0x20 kernel/
On Fri, 9 Dec 2016 14:44:25 +0800
Linas Vepstas wrote:
> On Fri, Dec 9, 2016 at 2:37 PM, Cao jin wrote:
> >
> >
> > On 12/09/2016 02:24 PM, Linas Vepstas wrote:
> >> I suppose I'm confused, but I recall that link resets are non-fatal.
> >> Fatal errors typically require that the the pci adapte
On Fri, 09 Dec 2016 15:21:33 +
Ian Campbell wrote:
> On Fri, 2016-12-09 at 13:33 +1000, Nicholas Piggin wrote:
> >
> > Well I simply tested the outcome. If you have:
> >
> > struct blah {
> > int x;
> > };
> > int foo(struct blah *blah)
> > {
> > return blah->x;
> > }
> > EXPORT(foo);
>
201 - 300 of 641 matches
Mail list logo
