From: Sathish Kumar Balasubramaniam b-sathishku...@hcl.com
This patch fixes a bug in the list of peripheral functions for the IPSR5 pin
mux configuration of the PFC (Pin Function Controller) of the Renesas R-Car H2
SoC (R8A7790). There should be exactly 8 values listed for the IP5_23_21
On 06/08/2014 02:42 PM, George Spelvin wrote:
Note, when you talk about efficiency here, this is called once every
40+ secs ... ;)
Agreed, in this case the code size saving (avoid a function call) is the
main benefit. And I prefer to avoid inefficiency on general priinciples,
if it's not
On 06/08/2014 07:34 PM, Hannes Frederic Sowa wrote:
...
Please check this as it makes the code more complicated and I doubt it is worth
it.
Agreed.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo
On Sat, Jun 07, 2014 at 09:47:01PM +0100, Fabio Baltieri wrote:
All devices supported by the ina2xx driver are bidirectional and reports
the measured value as a signed 16 bit, but the current driver
implementation caches the number as an u16, leading to an incorrect sign
extension when
On Sun, Jun 8, 2014, at 5:40, George Spelvin wrote:
Seems fine by me, since it's random anyway archs might not care
about the *_le32, though this might yield additional work in some
cases I presume.
If you think that's okay, sure. I kept it consistent to get byte-for-byte
identical
On Sun, Jun 08, 2014 at 01:16:00PM -0700, Guenter Roeck wrote:
On Sat, Jun 07, 2014 at 09:47:01PM +0100, Fabio Baltieri wrote:
All devices supported by the ina2xx driver are bidirectional and reports
the measured value as a signed 16 bit, but the current driver
implementation caches the
On Sun, 8 Jun 2014, Rickard Strandqvist wrote:
I find a logical error in an if statement '(X 0xfc) == 0x3' is always false
Where is the 0xfc that your converting?
After pointing this out, Larry Finger informed what would be the correct one.
'(X 0x3) == 0x3'
This is already what it is,
On Sun, 8 Jun 2014, Rickard Strandqvist wrote:
I find a logical error in an if statement '(X 0xfc) == 0x3' is always false
The test you're changing is '(X ~0xfc) == 0x3' which is not always
false, so is (bt_msr MSR_AP) == MSR_AP or (bt_msr ~MSR_AP) == MSR_AP
correct? Either way, your
Hi
Quite right!
I found this error in some of the files. And after discussion with
Larry Finger and Peter Wu, it was decided that all files with this if
statement should change.
But of course I should update the comment to something more suitable.
Kind regards
Rickard Strandqvist
2014-06-08
Thank you for your comments!
Have you checked assembler output if this helps anything at all? Constant
propagation in the compiler should be able to figure that out all by
itself. The only places I use __builtin_constant_p today are where I
also make use of inline assembler.
Yes, I did.
On Sun, Jun 8, 2014 at 9:30 PM, Guenter Roeck li...@roeck-us.net wrote:
On Sun, Jun 08, 2014 at 01:16:00PM -0700, Guenter Roeck wrote:
On Sat, Jun 07, 2014 at 09:47:01PM +0100, Fabio Baltieri wrote:
All devices supported by the ina2xx driver are bidirectional and reports
the measured value
This function is supposed to return true if the new load imbalance
is worse than the old one. It didn't. I can only hope brown paper
bags are in style.
Now things converge much better on both the 4 node and 8 node systems.
I am not sure why this did not seem to impact specjbb performance on
the
(Please do not top-post.)
On Sunday 08 June 2014 22:47:31 Rickard Strandqvist wrote:
I found this error in some of the files. And after discussion with
Larry Finger and Peter Wu, it was decided that all files with this if
statement should change.
But of course I should update the comment to
All devices supported by ina2xx are bidirectional and reports the
measured shunt voltage and power values as a signed 16 bit, but the
current driver implementation caches all registers as u16, leading to an
incorrect sign extension when reporting to the userspace in
ina2xx_get_value().
This patch
From: John W. Linville linvi...@tuxdriver.com
Date: Fri, 6 Jun 2014 12:05:58 -0400
Please accept this batch of fixes intended for the 3.16 stream.
Pulled, thanks John.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
With a tree that is close to 3.15 final I'm regularly seeing the
following on my EeePC 900 when starting ioquake3:
[drm:intel_pipe_config_compare] *ERROR* mismatch in gmch_pfit.lvds_border_bits
(expected 32768, found 0)
[ cut here ]
WARNING: CPU: 0 PID: 1594 at
On Sat, Jun 7, 2014 at 11:24 AM, Linus Torvalds
torva...@linux-foundation.org wrote:
Comments? Mel, this code is mostly attributed to you, I'd like to hear
what you think in particular.
In the meantime, I've removed the nr_unqueued_dirty == nr_taken
check for congestion_wait(), since I can't
Hi
I think someone missed the count sizeof type in memcpy.
I'm no expert on this code.
But I wonder if also the the next for loop wrong?
It will fill with 0XFF00 but it is
not a complete 0X you're looking for?
So something like:
memset(Buff[sigOffset], 0xFF,
Array 'SigBuff' is filled incompletely.
Someone forget to multiply for the sizeof type.
This was partly found using a static code analysis program called cppcheck.
Signed-off-by: Rickard Strandqvist rickard_strandqv...@spectrumdigital.se
---
drivers/staging/bcm/nvm.c |4 ++--
1 file
In short, I believe this is just dead code for the upstream kernel but this
causes a bug for 2.6.32 based kernels.
The setup_node_data() function is used to initialize NODE_DATA() for a node.
It gets a node id and a memory range. The start address for the memory range
is rounded up to ZONE_ALIGN
Hi Tejun, Vivek,
I came across this crash when attempting to run the 'hello world'
example from the Getting Started section on the docker.io homepage.
Repro kernels:
(upstream linus) 3.15.0
(RHEL7 RC-2) 3.10.0-121.el7.x86_64
To reproduce, boot with slub_debug=FZPU and run the example.
%
Hi nice to meet you . I'm Ms Laura Roland from Switzerland, is a pleasure to
contact you today,please write me back . thanks from Laura
--
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 Sun, 8 Jun 2014, Luiz Capitulino wrote:
diff --git a/arch/x86/include/asm/numa.h b/arch/x86/include/asm/numa.h
index 4064aca..01b493e 100644
--- a/arch/x86/include/asm/numa.h
+++ b/arch/x86/include/asm/numa.h
@@ -9,7 +9,6 @@
#ifdef CONFIG_NUMA
#define NR_NODE_MEMBLKS
On Fri, 6 Jun 2014, Gu Zheng wrote:
When running with the kernel(3.15-rc7+), the follow bug occurs:
[ 9969.258987] BUG: sleeping function called from invalid context at
kernel/locking/mutex.c:586
[ 9969.359906] in_atomic(): 1, irqs_disabled(): 0, pid: 160655, name:
python
[
snprintf() returns the number of bytes that could have been written
(excluding the null), not the actual number of bytes written. Given a
long enough subsystem or device name, these functions will advance
beyond the end of the on-stack buffer in dev_vprintk_exit(), resulting
in an information
I have a few assorted cleanups in-work, but I was thinking about the
following and it's led to some thinking about the (non-)usefulness
of the out[] buffer from _mix_pool_bytes.
The problem I started trying to solve is readers (entropy extractors)
monopolizing the pool lock and stalling writers
Daniel Borkmann wrote:
On 06/08/2014 07:34 PM, Hannes Frederic Sowa wrote:
Please check this as it makes the code more complicated and I doubt it is
worth it.
Agreed.
Just to clarify, the goal is to be able to replace prandom_u32() %
range all over the kernel with prandom_u32_max(range) and
On Sat, Jun 7, 2014 at 4:18 PM, Dave Airlie airl...@gmail.com wrote:
cc'ing list
On 8 June 2014 04:08, Howard Chu h...@symas.com wrote:
On Asus NP56D, if you use vgaswitcheroo to turn off the discrete GPU, the
kernel starts spewing these messages endlessly, until /var/log partition
fills up:
Seeing from the code, it is OK.
Reviewed-by: Tang Chentangc...@cn.fujitsu.com
Thanks.
On 06/07/2014 02:21 PM, Fabian Frederick wrote:
memblock_set_bottom_up is only called by
__init cmdline_parse_movable_node and __init numa_init.
Cc: Andrew Mortona...@linux-foundation.org
Cc: Tang
On Sun, Jun 8, 2014 at 3:14 PM, Luiz Capitulino lcapitul...@redhat.com wrote:
In short, I believe this is just dead code for the upstream kernel but this
causes a bug for 2.6.32 based kernels.
The setup_node_data() function is used to initialize NODE_DATA() for a node.
It gets a node id and a
On Sun, Jun 08, 2014 at 08:05:24PM -0400, George Spelvin wrote:
The problem I started trying to solve is readers (entropy extractors)
monopolizing the pool lock and stalling writers (entropy mixers), which
are supposed to be fast and low overhead.
Which writer are you worried about,
On Fri, Jun 06, 2014 at 11:21:27AM -0400, Steven Rostedt wrote:
Date: Fri, 6 Jun 2014 11:21:27 -0400
From: Steven Rostedt rost...@goodmis.org
To: Chen, Gong gong.c...@linux.intel.com
Cc: Luck, Tony tony.l...@intel.com, Borislav Petkov b...@alien8.de,
m.che...@samsung.com
From: Fan Wu f...@marvell.com
What the patch did:
1.To call pinmux_disable_setting ahead of pinmux_enable_setting in each time of
calling pinctrl_select_state
2.Remove the HW disable operation in in pinmux_disable_setting function.
3.Remove the disable ops in struct pinmux_ops
4.Remove all the
Hi Linus,
On Sun, Jun 8, 2014 at 10:56 AM, Linus Torvalds
torva...@linux-foundation.org wrote:
On Wed, Jun 4, 2014 at 11:23 PM, Herbert Xu herb...@gondor.apana.org.au
wrote:
Here is the crypto update for 3.16:
There's something odd going on with bfin_crc.h.
You moved it in commit
On 2014-06-06 16:37, Rickard Strandqvist wrote:
Address of local variable assigned to a function parameter
This was partly found using a static code analysis program called cppcheck.
I'd be surprised if this was a real bug, but I agree on principle, we
should not leak stack data. The code is
On 06/06/14 at 04:04pm, Vivek Goyal wrote:
On Fri, Jun 06, 2014 at 03:37:48PM +0800, Dave Young wrote:
On 06/05/14 at 11:01am, Vivek Goyal wrote:
On Thu, Jun 05, 2014 at 04:31:34PM +0800, Dave Young wrote:
[..]
+ ret = kexec_file_load(kernel_fd, info.initrd_fd,
Hi, rt-people
I don't think it is the correct direction.
Softirq (including local_bh_disable()) in RT kernel should be preemptible.
Fixing these problems via converting spinlock_t to raw_spinlock_t will
result that all spinlock_t used in RCU-callbacks are converted which
means almost the
On Thu, Jun 05, 2014 at 11:22:00AM -0400, Santosh Shilimkar wrote:
Recently we introduced the generic device tree infrastructure for couple of
DMA
bus parameter, dma-ranges and dma-coherent. Update the documentation so that
its useful for future users.
The dma-ranges property is intended
Which writer are you worried about, specifically? A userspace write
to /dev/random from rgnd?
Actually, the part I'm actually worried about is latency in
add_interrupt_randomness.
But I may have not understood how the locking works. There's a per-CPU
fast pool which isn't locked at all,
On 06/06/14 at 02:19pm, Vivek Goyal wrote:
On Fri, Jun 06, 2014 at 02:56:05PM +0800, WANG Chao wrote:
On 06/03/14 at 09:06am, Vivek Goyal wrote:
Previous patch provided the interface definition and this patch prvides
implementation of new syscall.
Previously segment list was
On Thu, Jun 5, 2014 at 12:22 PM, Santosh Shilimkar
santosh.shilim...@ti.com wrote:
Recently we introduced the generic device tree infrastructure for couple of
DMA
bus parameter, dma-ranges and dma-coherent. Update the documentation so that
its useful for future users.
The dma-ranges
On Sun, 2014-06-08 at 23:51 +0100, Ben Hutchings wrote:
snprintf() returns the number of bytes that could have been written
(excluding the null), not the actual number of bytes written. Given a
long enough subsystem or device name, these functions will advance
beyond the end of the on-stack
On Fri, Jun 06, 2014 at 01:02:59PM +0200, Lothar Waßmann wrote:
Signed-off-by: Lothar Waßmann l...@karo-electronics.de
---
arch/arm/boot/dts/imx6qdl.dtsi |2 ++
1 file changed, 2 insertions(+)
Applied, thanks.
Shawn
diff --git a/arch/arm/boot/dts/imx6qdl.dtsi
Summarizing that, time to feed in 32 MiB of zeros (from user-space):
0 concurrent reads: 0.356898 0.357693
1 concurrent read: 0.505941 0.509075(+42%)
2 concurrent reads: 0.662240 0.657055(+84%)
Er, wait a minute... I'm not sure which kernel (patched or unpatched)
I did
On Mon, 2014-06-09 at 10:08 +0800, Lai Jiangshan wrote:
Hi, rt-people
I don't think it is the correct direction.
Yup, it's a band-aid, ergo RFC.
-Mike
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More
Linus Torvalds:
So I ended up doing an rc8 because I was a bit worried about some
last-minute dcache fixes, but it turns out that nobody seemed to even
notice those. We did have other issues during the week, though, so it
:::
I am afraid there is a problem in dcache. Please read
# RESEND and please ignore previous mail #
On 2014/06/08 20:58, Alexandre Courbot wrote:
Interesting approach to a long-standing problem. I had my own
embarrassing attempt at it (power sequences), and more recently Olof
(CC'd) sent something related for the MMC bus
On Fri, Jun 06, 2014 at 08:12:12PM +0800, Vivek Gautam wrote:
Some PHY controllers may need to calibrate certain
PHY settings after initialization of the controller and
sometimes even after initializing the PHY-consumer too.
Add support for the same in order to let consumers do so in need.
Sigh, adventures in unable to mount root filesystem currently underway.
Tested on a different computer without patches (half size, since it's
an older machine):
Writing 16 MiB:
16777216 bytes (17 MB) copied, 0.289169 s, 58.0 MB/s
16777216 bytes (17 MB) copied, 0.289378 s, 58.0 MB/s
Writing
Using an else following a break or return can unnecessarily
indent code blocks.
ie:
for (i = 0; i 100; i++) {
int foo = bar();
if (foo 1)
break;
else
usleep(1);
}
is generally better
On Fri, Jun 6, 2014 at 8:20 PM, Matias Bjørling m...@bjorling.me wrote:
This converts the current NVMe driver to utilize the blk-mq layer.
Looks it can't be applied cleanly against 3.15-rc8 + Jens's for-linux
branch, when I fix the conflict manually, below failure is triggered:
[ 487.696057]
Hi Andi,
On Fri, 30 May 2014 14:50:08 -0700, Andi Kleen wrote:
@@ -756,22 +816,31 @@ void print_pmu_events(const char *event_glob, bool
name_only)
(!is_cpu strglobmatch(alias-name,
event_glob
Hi experts.
I think all the macros with CONFIG_ prefix are supposed to be
defined in Kconfig.
But I've been long wondering why there exists one exception:
CONFIG_SHELL.
Is there any historical, or special reason?
Is it good to rename it to KBUILD_SHELL or something else?
Best Regards
Masahiro
On 8 June 2014 02:11, Srivatsa S. Bhat srivatsa.b...@linux.vnet.ibm.com wrote:
diff --git a/drivers/cpufreq/cpufreq_governor.c
b/drivers/cpufreq/cpufreq_governor.c
+ if (unlikely(wall_time (2 * sampling_rate))
+
On Sat, Jun 7, 2014 at 12:39 AM, Greg KH gre...@linuxfoundation.org wrote:
On Fri, Jun 06, 2014 at 07:44:08PM +0900, Magnus Damm wrote:
staging: Emma Mobile USB driver and KZM9D board code V3
[PATCH v3 01/05] staging: emxx_udc: Add Emma Mobile USB Gadget driver
[PATCH v3 02/05] staging:
Hi Suman,
On Sun, Jun 8, 2014 at 12:51 PM, Suman Tripathi stripa...@apm.com wrote:
Hi Ming,
I have attached the patches but it is not accepted by Tejun yet, So I will
post another version.
OK, thanks.
Since Tejun didn't think it is a workable approach, I am not going test
the attachment,
On Wed, 4 Jun 2014 09:59:30 -0700, Andi Kleen wrote:
I saw samples.
Oh well we can just drop it. The only difference is that the
event list cannot set a period then.
I tested with a downloaded event, and it does have samples. But the
frequency could not be changed even with your patch.
$
'copy_prev_load' was recently added by commit: 18b46ab (cpufreq: governor: Be
friendly towards latency-sensitive bursty workloads).
It actually is a bit redundant as we also have 'prev_load' which can store any
integer value and can be used instead of 'copy_prev_load' by setting it to zero
when
On 06/09/14 at 10:11am, Dave Young wrote:
On 06/06/14 at 02:19pm, Vivek Goyal wrote:
On Fri, Jun 06, 2014 at 02:56:05PM +0800, WANG Chao wrote:
On 06/03/14 at 09:06am, Vivek Goyal wrote:
Previous patch provided the interface definition and this patch prvides
implementation of new
When configuring event perf checked a wrong condition that user
specified both of freq (-F) and period (-c) or the event has no
default value. This worked because most of events don't have default
value and only tracepoint events have default of 1 (and it's not
desirable to change it for those
On Thu, Jun 05, 2014 at 11:49:49PM +0200, Richard Weinberger wrote:
Am 05.06.2014 06:15, schrieb Honggang Li:
arch/x86/um/checksum_32.S had been copy paste from x86. When build
x86 uml, csum_partial_copy_generic_i386 mess up the exception table.
In fact, exception table dose not work in
Hi, Richard
Any comment about this patch?
thanks
On Tue, Jun 03, 2014 at 01:30:44PM +0800, Real Name wrote:
From: Honggang Li enjoymind...@gmail.com
The patch based on linux-next-2014-06-02.
The old init_maps function does two things:
1) allocates and initializes one struct page array
On Thu, Jun 05, 2014 at 05:48:37PM +0200, Antoine Ténart wrote:
This series adds the support for the Marvell Berlin USB controllers,
the USB PHYs and also adds a reset controller.
The reset controller is used by the USB PHY driver and shares the
existing chip controller node with the clocks
On Fri, 30 May 2014 14:50:06 -0700, Andi Kleen wrote:
[v2: Review feedback addressed and some minor improvements]
[v3: More review feedback addressed and handle test failures better.
Ported to latest tip/core.]
[v4: Addressed Namhyung's feedback]
[v5: Rebase to latest tree. Minor description
201 - 264 of 264 matches
Mail list logo
