Hi,
Currently, many drivers implement their own strategy when trying to find
which timer to use as the clocksource or the clockevent.
The main issue is that this selection is happen early in the boot
process and the kernel doesn't always have all the information to take
that decision.
So we end
The driver currently uses aliases to know whether the timer is the
clocksource or the clockevent. Add the /chosen/linux,clocksource and
/chosen/linux,clockevent parsing while keeping backward compatibility.
Signed-off-by: Alexandre Belloni
---
drivers/clocksource/Kconfig | 1 +
dr
Add a way for drivers to know whether the timer they are currently handling
is a clocksource or a clockevent.
Signed-off-by: Alexandre Belloni
---
drivers/clocksource/timer-of.c | 22 ++
drivers/clocksource/timer-of.h | 3 +++
2 files changed, 25 insertions(+)
diff --git a/
The clocksource and clockevent timer are probed early in the boot process.
At that time it is difficult for linux to know whether a particular timer
can be used as the clocksource or the clockevent or by another driver,
especially when they are all identical or have similar features.
Until now, mu
From: ssjoh...@mac.com
Date: Mon, 11 Dec 2017 21:51:14 +0100
> From: Sebastian Sjoholm
>
> Sierra Wireless EM7565 is an Qualcomm MDM9x50 based M.2 modem.
> The USB id is added to qmi_wwan.c to allow QMI communication
> with the EM7565.
>
> Signed-off-by: Sebastian Sjoholm
> Acked-by: Bjørn Mo
On Wed, Dec 13, 2017 at 10:07:32AM -0800, Darrick J. Wong wrote:
> On Wed, Dec 13, 2017 at 01:03:57PM -0500, Josef Bacik wrote:
> > On Tue, Dec 12, 2017 at 03:11:50PM -0800, Darrick J. Wong wrote:
> > > On Mon, Dec 11, 2017 at 11:36:45AM -0500, Josef Bacik wrote:
> > > > This is the same as v8, jus
From: Branislav Radocaj
Date: Tue, 12 Dec 2017 00:13:38 +0100
> If clk_set_rate() fails, we should disable clk before return.
> Found by Linux Driver Verification project (linuxtesting.org).
>
> Changes since v2 [1]:
> * Merged with latest code changes
>
> Changes since v1:
> Update made thanks
On Wed, 2017-12-13 at 15:21 +0100, Valentin Vidic wrote:
> WARNING: Missing a blank line after declarations
[]
> diff --git a/drivers/staging/pi433/pi433_if.c
> b/drivers/staging/pi433/pi433_if.c
[]
> @@ -565,6 +565,7 @@ pi433_tx_thread(void *data)
> bool rx_interrupted = false;
>
I should clarify that the packet being forwarded originated on the
Virtual Interface (i.e. it wasn't received on it). When data is received
on the Virtual Interface (i.e. sent by a virtual host) then ip_summed is
CHECKSUM_PARTIAL and the checksum is calculated before transmission on
the wire.
i2c_new_dummy is typically called from the probe function of the
driver for the primary i2c client. It requires calls to
i2c_unregister_device in the error path of the probe function and
in the remove function.
This can be simplified by introducing a device-managed version.
Make at24 driver the fi
Reviewed-by: Jim Mattson
On Wed, Dec 13, 2017 at 4:51 AM, Paolo Bonzini wrote:
> xsetbv can be expensive when running on nested virtualization, try to
> avoid it.
>
> Signed-off-by: Paolo Bonzini
> ---
> arch/x86/kvm/x86.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --gi
On Wed, 13 Dec 2017 14:22:12 +, Al Viro wrote:
> IMO it's not worth the trouble; let's go with the check inside of
> static inline and accept that on clang builds it'll do nothing.
Ack, thanks for investigating!
From: Markus Elfring
Date: Wed, 13 Dec 2017 20:03:45 +0100
Two update suggestions were taken into account
from static source code analysis.
Markus Elfring (2):
Delete an error message for a failed memory allocation
Improve a size determination
drivers/sn/ioc3.c | 5 +
1 file changed, 1
From: Markus Elfring
Date: Wed, 13 Dec 2017 19:39:18 +0100
Omit an extra message for a memory allocation failure in this function.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
drivers/sn/ioc3.c | 3 ---
1 file changed, 3 deletions(-)
diff --git
From: Markus Elfring
Date: Wed, 13 Dec 2017 19:53:18 +0100
Replace the specification of a data structure by a pointer dereference
as the parameter for the operator "sizeof" to make the corresponding size
determination a bit safer according to the Linux coding style convention.
This issue was det
Currently i2c_new_device and i2c_new_dummy return just NULL in error
case although they have more error details internally. Therefore move
the functionality into new functions returning detailed errors and
add wrappers for compatibilty with the current API.
This allows to use these functions with
Make use of recently introduced device-managed version of
i2c_new_dummy to simplify the code.
Signed-off-by: Heiner Kallweit
---
v2:
- small improvements regarding code readability
v3:
- no changes
---
drivers/misc/eeprom/at24.c | 31 +++
1 file changed, 11 insertions
i2c_new_dummy is typically called from the probe function of the
driver for the primary i2c client. It requires calls to
i2c_unregister_device in the error path of the probe function and
in the remove function.
This can be simplified by introducing a device-managed version.
Note the changed error
Em Fri, 13 Oct 2017 15:08:34 +0900
escreveu:
> From: Yasunari Takiguchi
>
> These functions monitor the driver and watch for task completion.
> This is part of the Sony CXD2880 DVB-T2/T tuner + demodulator driver.
If I understand well, the goal here is to have thread that would
be waking up fr
Hi,
On Wed, Dec 13, 2017 at 4:41 AM, Enric Balletbo Serra
wrote:
> Hi Doug,
>
> 2017-12-11 22:45 GMT+01:00 Douglas Anderson :
>> Bind / unbind stress testing of the USB controller on rk3399 found
>> that we'd often end up with lots of failures that looked like this:
>>
>> phy phy-ff80.phy.9
On Wed, Dec 13, 2017 at 11:50:56AM -0500, Tyler Baicar wrote:
> On 11/15/2017 12:56 PM, Bjorn Helgaas wrote:
> >Hi Tyler,
> >
> >On Wed, Nov 15, 2017 at 09:47:41AM -0500, Tyler Baicar wrote:
> >>On 10/17/2017 11:42 AM, Tyler Baicar wrote:
> >>>Currently the AER driver uses cper_print_bits() to prin
Em Fri, 13 Oct 2017 15:09:34 +0900
escreveu:
> From: Yasunari Takiguchi
>
> This provides the main dvb frontend operation functions
> for the Sony CXD2880 DVB-T2/T tuner + demodulator driver.
>
> Signed-off-by: Yasunari Takiguchi
> Signed-off-by: Masayuki Yamamoto
> Signed-off-by: Hideki Noz
On 12/13/2017 03:55 AM, Greg KH wrote:
> On Sat, Dec 09, 2017 at 12:41:11PM -0800, Tomas Marek wrote:
>> This patch fix several brace on next line, braces not necessary, space
>> around =/<, and space before/after open/close parenthesis coding style
>> errors find by checkpatch in pi433_if.c.
>>
>
On Wed, Dec 13, 2017 at 11:27:00AM -0500, Jeff Moyer wrote:
> Matthew Wilcox writes:
>
> > On Wed, Dec 13, 2017 at 09:42:52PM +0800, Zhen Lei wrote:
> >> Below information is reported by a lower kernel version, and I saw the
> >> problem still exist in current version.
> >
> > I think you're righ
2017-12-02 1:39 GMT+01:00 Jakub Kicinski :
> Hi!
>
> I'm hitting these after DaveM pulled rc1 into net-next on my Xeon
> E5-2630 v4 box. It also happens on linux-next. Did anyone else
> experience it? (.config attached)
>
> [5.003771] WARNING: CPU: 14 PID: 1 at
> ../arch/x86/events/intel/un
Em Fri, 13 Oct 2017 14:46:35 +0900
escreveu:
> From: Yasunari Takiguchi
>
> Hi,
>
> This is the patch series (version 4) of Sony CXD2880 DVB-T2/T tuner +
> demodulator driver.The driver supports DVB-API and interfaces through
> SPI.
>
> We have tested the driver on Raspberry Pi 3 and got pi
Hello,
running Fedora 27 on an Intel Atom C3758 CPU Supermicro system
(A2SDi-8C+-HLN4F) I've noticed that crypto selftests fail when the
qat_c3xxx module is loaded (it is loaded, by default). That means that
stuff like `modprobe dm-crypt`, `cryptsetup benchmark` and `cryptsetup
luksOpen` fail.
Th
This will fix the following warning:
Warning (unit_address_vs_reg): Node /memory has a reg or ranges property, but
no unit name
Signed-off-by: Corentin Labbe
---
arch/arm/boot/dts/sun8i-a83t.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/sun8i-a83t.dt
This will fix the following warning:
Warning (simple_bus_reg): Node /soc/cpucfg@0170 simple-bus unit address
format error, expected "170"
Signed-off-by: Corentin Labbe
---
arch/arm/boot/dts/sun8i-a83t.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot
Hi Mylène,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on input/next]
[also build test WARNING on v4.15-rc3 next-20171213]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci
Fixes: 68d0bd1e4815 ("Input: Add driver for Cypress Generation 5 touchscreen")
Signed-off-by: Fengguang Wu
---
cyttsp5.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/input/touchscreen/cyttsp5.c
b/drivers/input/touchscreen/cyttsp5.c
index a41feea..9694ae41 10064
The patch
spi: jcore: disable clock when registering spi conroller failed
has been applied to the spi tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hou
The patch
regmap: potentially duplicate the name string stored in regmap
has been applied to the regmap tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 2
On Wed, 2017-12-13 at 12:25 +0100, Bartosz Golaszewski wrote:
> Users often pass a pointer to a static string to gpiochip_add_data()
> family of functions. Avoid unnecessary memory allocations with the
> provided helper routine.
[]
> diff --git a/drivers/gpio/gpiolib.c b/drivers/gpio/gpiolib.c
[]
>
All parameters of watchdog_init_timeout() are documented with exception
of wdd, thus generating a build warning.
This patch document it and so remove the following build warning:
drivers/watchdog/watchdog_core.c:113: warning: No description found for
parameter 'wdd'
Signed-off-by: Corentin Labbe
Fix variable naming and checkpatch warning:
WARNING: Missing a blank line after declarations
Signed-off-by: Valentin Vidic
---
v2: use a better variable name
v3: keep the variable scope
drivers/staging/pi433/pi433_if.c | 8 +---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git
On Wed, Dec 13, 2017 at 9:13 AM, Priit Laes wrote:
> On Wed, Dec 13, 2017 at 05:09:33PM +, Priit Laes wrote:
>> On Tue, Dec 12, 2017 at 01:24:52PM -0800, Kevin Hilman wrote:
>> > On Tue, Dec 12, 2017 at 9:26 AM, Priit Laes wrote:
>> > > On Mon, Dec 11, 2017 at 02:22:30PM -0800, Kevin Hilman w
Also, mention this in the bootsplash documentation.
Signed-off-by: Max Staudt
---
Documentation/bootsplash.rst | 10 ++
tools/bootsplash/.gitignore| 3 ++
tools/bootsplash/ajax-loader.gif | Bin 0 -> 3208 bytes
tools/bootsplash/bootsplash-tux.sh | 66 +
This allows showing multiple logos, each in its own position,
relative to the eight screen corners.
Signed-off-by: Max Staudt
---
drivers/video/fbdev/core/bootsplash_render.c | 136 ++-
include/uapi/linux/bootsplash_file.h | 45 -
2 files changed, 178 ins
Signed-off-by: Max Staudt
---
.../ABI/testing/sysfs-platform-bootsplash | 11 ++
Documentation/bootsplash.rst | 177 +
MAINTAINERS| 2 +
3 files changed, 190 insertions(+)
create mode 100644 Documentati
Signed-off-by: Max Staudt
---
MAINTAINERS | 1 +
tools/bootsplash/.gitignore | 1 +
tools/bootsplash/Makefile| 9 +
tools/bootsplash/bootsplash-packer.c | 471 +++
4 files changed, 482 insertions(+)
create mode 1
After exiting a KD_GRAPHICS program and falling back to the text
console, a previously enabled splash needs to be fully redrawn.
This corner case was introduced with selective re-drawing while
implementing animations.
Without this patch, the following happens:
1. Switch to a text console
2. Enab
Dear fbdev and fbcon developers,
Thank you very much for your input for the first patch series.
I've included your feedback into this second roll, and kindly ask for
your opinion on the new patch series.
Changes from v1 to v2:
+ Added a user space tool to create splash theme files
+ Bumped t
Signed-off-by: Max Staudt
Reviewed-by: Oliver Neukum
---
drivers/video/fbdev/core/fbcon.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/drivers/video/fbdev/core/fbcon.c b/drivers/video/fbdev/core/fbcon.c
index 9a39a6fcfe98..8a9c67e1c5d8 100644
--- a/drivers/video/fbdev/core/fbc
Users can use this to replace their splash screen at runtime by writing
a path and filename to /sys/devices/platform/bootsplash.0/load_file and
making sure the splash is enabled.
Notes:
- The path has to be a path in /lib/firmware since request_firmware()
is used to fetch the data.
- When
Each 'picture' in the splash file can consist of multiple 'blobs'.
If animation is enabled, these blobs become the frames of an animation,
in the order in which they are stored in the file.
Note: There is only one global timer, so all animations happen at
the same frame rate. It doesn't rea
Let's disable the splash if the user presses ESC or F1-F12 on a VT.
The F1-F12 check is to disable the splash on VT switches.
Signed-off-by: Max Staudt
---
drivers/tty/vt/keyboard.c | 24
1 file changed, 24 insertions(+)
diff --git a/drivers/tty/vt/keyboard.c b/drivers
Add the corresponding section in cgroup v2 documentation.
Signed-off-by: Roman Gushchin
Cc: Tejun Heo
Cc: Alexei Starovoitov
Cc: kernel-t...@fb.com
Cc: cgro...@vger.kernel.org
Cc: linux-...@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
---
Documentation/cgroup-v2.txt | 33 ++
Load logo(s) from a file and render them in the center of the screen.
This removes the "black screen" functionality, which can now be emulated
by providing a splash file with no pictures and a black background.
Signed-off-by: Max Staudt
---
MAINTAINERS| 1 +
When the user requests a clean TTY via the SAK SysRq, that means he
really wants to use the console.
Let's disable the bootsplash, even if the request is not on a VT, as
the user probably knows what he's doing and it's more helpful to get
out of his way.
Signed-off-by: Max Staudt
Reviewed-by: Ol
Framebuffers with deferred I/O need to be flushed to the screen
explicitly, since we use neither the mmap nor the file I/O abstractions
that handle this for userspace FB clients.
Example: xenfb
Some framebuffer drivers implement lazy access to the screen without
actually exposing a fbdefio interf
This is the initial prototype for a lean Linux kernel bootsplash.
It works by replacing fbcon's FB manipulation routines (such as
bitblit, tileblit) with dummy functions, effectively disabling text
output, and drawing the splash directly onto the FB device.
As it is now, it will show a black scre
Unfortunately I've forgotten to rebase this patchset to 4.15, so it still
builds on top of 4.14.
I'll rebase it for the next roll.
Max
From: Jia-Ju Bai
Date: Tue, 12 Dec 2017 16:49:52 +0800
> The driver may sleep under a spinlock.
> The function call path is:
> rr_close (acquire the spinlock)
> free_irq --> may sleep
>
> To fix it, free_irq is moved to the place without holding the spinlock.
>
> This bug is found by my stati
Good day
I emailed you earlier without any response from you, in my first email I
mentioned about my late client, whose relatives I cannot get in touch with. He
deposited a large sum of funds in our bank. I am in a position to front you as
the next of kin to late client and move funds to you
Dan,
Patch set applied, thanks.
--
Best regards,
Jacek Anaszewski
On 12/12/2017 11:01 PM, Dan Murphy wrote:
> All
>
> v4 - Fix checkpatch warning for code indentation on the
> leds: lp8860: Update the dt parsing for LED labeling patch.
>
> v3 - Made changes to the patch set to address concern
On Wed, 13 Dec 2017 20:37:02 +0100, Björn Töpel wrote:
> 2017-12-02 1:39 GMT+01:00 Jakub Kicinski:
> > [5.777076] ---[ end Kernel panic - not syncing: Attempted to kill init!
> > exitcode=0x0009
>
> Yes, I'm getting that as well (v4.15-rc2-772-gcdc0974f10cf).
>
> Did you bisect it? I h
On Mon, Dec 11, 2017 at 4:43 PM, Joel Fernandes wrote:
> Hi Vincent,
>
>>>
>
> Here we have RT activity running on big CPU cluster induced with rt-app,
> and running hackbench in parallel. The RT tasks are bound to 4 CPU
Fixes checkpatch warning:
CHECK: Avoid CamelCase:
Signed-off-by: Valentin Vidic
---
drivers/staging/pi433/rf69.c | 30 +++---
drivers/staging/pi433/rf69.h | 6 +++---
drivers/staging/pi433/rf69_enum.h | 18 +-
3 files changed, 27 insertions(
From: Colin King
Date: Tue, 12 Dec 2017 13:03:11 +
> From: Colin Ian King
>
> The function meson_gxl_read_status is local to the source and does
> not need to be in global scope, so make it static.
>
> Cleans up sparse warning:
> symbol 'meson_gxl_read_status' was not declared. Should it b
On Wed, 2017-12-13 at 10:05 -0500, J. Bruce Fields wrote:
> This is great, thanks.
>
> On Wed, Dec 13, 2017 at 09:19:58AM -0500, Jeff Layton wrote:
> > With this, we reduce inode metadata updates across all 3 filesystems
> > down to roughly the frequency of the timestamp granularity, particularly
On Tue, 12 Dec 2017 19:15:53 +0800
"Du, Changbin" wrote:
> Hi Rostedt, How about this version?
>
I've pulled it, but due to traveling, I haven't been able to push it to
Linus yet. I'm hoping to do that soon.
-- Steve
From: Colin Ian King
The check of len being zero is redundant as it has already been
sanity checked for this value at the start of the function. Hence
it is impossible for this test to be true and so the redundant
code can be removed.
Detected by CoverityScan, CID#1462748 ("Logically dead code")
On Wed, 13 Dec 2017 20:17:43 +
Colin King wrote:
> From: Colin Ian King
>
> The check of len being zero is redundant as it has already been
> sanity checked for this value at the start of the function. Hence
> it is impossible for this test to be true and so the redundant
> code can be remo
On 13/12/17 20:24, Boris Brezillon wrote:
> On Wed, 13 Dec 2017 20:17:43 +
> Colin King wrote:
>
>> From: Colin Ian King
>>
>> The check of len being zero is redundant as it has already been
>> sanity checked for this value at the start of the function. Hence
>> it is impossible for this tes
Hi Dan,
checkpatch.pl doesn't want to be mentioned in the patch subject :-)
"WARNING: A patch subject line should describe the change not the tool
that found it"
Preferably I'd see two separate patches.
Also, line length limit for the commit description is 75 characters.
Please use whole availa
On Wed, 13 Dec 2017 20:30:04 +
Colin Ian King wrote:
> On 13/12/17 20:24, Boris Brezillon wrote:
> > On Wed, 13 Dec 2017 20:17:43 +
> > Colin King wrote:
> >
> >> From: Colin Ian King
> >>
> >> The check of len being zero is redundant as it has already been
> >> sanity checked for th
The following changes since commit 50c4c4e268a2d7a3e58ebb698ac74da0de40ae36:
Linux 4.15-rc3 (2017-12-10 17:56:26 -0800)
are available in the git repository at:
ssh://g...@gitolite.kernel.org/pub/scm/linux/kernel/git/palmer/linux.git
tags/riscv-for-linus-4.15-rc4-riscv_fixes
for you to fetc
Jason,
Am Mittwoch, 13. Dezember 2017, 18:22:30 CET schrieb Jason A. Donenfeld:
> Recent libcs have gotten a bit more strict, so we actually need to
> include the right headers and use the right types. This enables UML to
> compile again.
>
> Signed-off-by: Jason A. Donenfeld
> Cc: sta...@vger.k
Jacek
On 12/13/2017 02:29 PM, Jacek Anaszewski wrote:
> Hi Dan,
>
> checkpatch.pl doesn't want to be mentioned in the patch subject :-)
>
Ack
> "WARNING: A patch subject line should describe the change not the tool
> that found it"
>
> Preferably I'd see two separate patches.
>
So you want
Dan,
On 12/13/2017 09:41 PM, Dan Murphy wrote:
> Jacek
>
> On 12/13/2017 02:29 PM, Jacek Anaszewski wrote:
>> Hi Dan,
>>
>> checkpatch.pl doesn't want to be mentioned in the patch subject :-)
>>
>
> Ack
>
>> "WARNING: A patch subject line should describe the change not the tool
>> that found it
On 13/12/17 20:38, Boris Brezillon wrote:
> On Wed, 13 Dec 2017 20:30:04 +
> Colin Ian King wrote:
>
>> On 13/12/17 20:24, Boris Brezillon wrote:
>>> On Wed, 13 Dec 2017 20:17:43 +
>>> Colin King wrote:
>>>
From: Colin Ian King
The check of len being zero is redundant
On Wed, 13 Dec 2017 21:38:44 +0100
Boris Brezillon wrote:
> On Wed, 13 Dec 2017 20:30:04 +
> Colin Ian King wrote:
>
> > On 13/12/17 20:24, Boris Brezillon wrote:
> > > On Wed, 13 Dec 2017 20:17:43 +
> > > Colin King wrote:
> > >
> > >> From: Colin Ian King
> > >>
> > >> The ch
Hi HL,
On Mon, Dec 04, 2017 at 03:17:48PM +0800, Lin Huang wrote:
> Refactor Innolux P079ZCA panel driver, let it support
> multi panel.
>
> Signed-off-by: Lin Huang
> ---
> Changes in v2:
> - Change regulator property name to meet the panel datasheet
> Changes in v3:
> - this patch only refact
From: Arnd Bergmann
We get a build error in the irqsoff tracer in some configurations:
kernel/trace/trace_irqsoff.c: In function 'trace_preempt_on':
kernel/trace/trace_irqsoff.c:855:2: error: implicit declaration of function
'trace_preempt_enable_rcuidle'; did you mean 'trace_irq_enable_rcuidle
From: Chunyu Hu
Naming in code comments for tracing_snapshot, tracing_snapshot_alloc
and trace_pid_filter_add_remove_task don't match the real function
names. And latency_trace has been removed from tracing directory.
Fix them.
Link:
http://lkml.kernel.org/r/1508394753-20887-1-git-send-email-c
-static bool pcie_has_flr(struct pci_dev *dev)
+bool pcie_has_flr(struct pci_dev *dev)
{
u32 cap;
@@ -3882,6 +3882,7 @@ static bool pcie_has_flr(struct pci_dev *dev)
pcie_capability_read_dword(dev, PCI_EXP_DEVCAP, &cap);
return cap & PCI_EXP_DEVCAP_FLR;
}
+EXPORT_SYMB
This should have gone out a while ago, but due to traveling and
system updates of my home office, it was delayed.
-- Steve
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
for-next
Head SHA1: 7cf19b391f18a230dc989928334a9b8d10b1bf51
Arnd Bergmann (2):
tracing: alw
From: Changbin Du
The default NR_CPUS can be very large, but actual possible nr_cpu_ids
usually is very small. For my x86 distribution, the NR_CPUS is 8192 and
nr_cpu_ids is 4. About 2 pages are wasted.
Most machines don't have so many CPUs, so define a array with NR_CPUS
just wastes memory. So
From: "Steven Rostedt (VMware)"
The stack tracer records a stack dump whenever it sees a stack usage that is
more than what it ever saw before. This can happen at any function that is
being traced. If it happens when the CPU is going idle (or other strange
locations), RCU may not be watching, and
From: Arnd Bergmann
When CONFIG_TRACING is disabled, the new preemptirq events tracer
produces a build failure:
In file included from kernel/trace/trace_irqsoff.c:17:0:
kernel/trace/trace.h: In function 'trace_test_and_set_recursion':
kernel/trace/trace.h:542:28: error: 'struct task_struct' has
From: Matthias Kaehlcke
This fixes the following warning when building with clang:
kernel/trace/ring_buffer.c:1842:1: error: unused function
'__rb_data_page_index' [-Werror,-Wunused-function]
Link: http://lkml.kernel.org/r/20170518001415.5223-1-...@chromium.org
Reviewed-by: Douglas Anderso
From: Felipe Balbi
By passing an export descriptor to the write function, users don't need to
keep a global static pointer and can rely on container_of() to fetch their
own structure.
Link:
http://lkml.kernel.org/r/20170602102025.5140-1-felipe.ba...@linux.intel.com
Acked-by: Steven Rostedt (VM
From: Colin Ian King
There are two error return paths that are not kfree'ing ep that
lead to memory leaks. Fix this by exiting on error via the
ext_out exit path that performs the necessary kfree.
Detected by CoverityScan, CID#1462747 ("Resource Leak")
Fixes: b83ea87958c5 ("mtd: nand: provide
On 13/12/17 15:00, Jose Abreu wrote:
> Hi Hans,
>
> On 13-12-2017 10:00, Hans Verkuil wrote:
>> On 12/12/17 17:02, Jose Abreu wrote:
>>>
> +static int dw_hdmi_s_routing(struct v4l2_subdev *sd, u32 input, u32
> output,
> + u32 config)
> +{
> + struct dw_hdmi_dev *dw_dev
Pavel and Laurent
On 12/13/2017 02:43 PM, Jacek Anaszewski wrote:
> Dan,
>
> On 12/13/2017 09:41 PM, Dan Murphy wrote:
>> Jacek
>>
>> On 12/13/2017 02:29 PM, Jacek Anaszewski wrote:
>>> Hi Dan,
>>>
>>> checkpatch.pl doesn't want to be mentioned in the patch subject :-)
>>>
>>
>> Ack
>>
>>> "WARNI
On Wed, 13 Dec 2017 20:44:45 +
Colin Ian King wrote:
> On 13/12/17 20:38, Boris Brezillon wrote:
> > On Wed, 13 Dec 2017 20:30:04 +
> > Colin Ian King wrote:
> >
> >> On 13/12/17 20:24, Boris Brezillon wrote:
> >>> On Wed, 13 Dec 2017 20:17:43 +
> >>> Colin King wrote:
> >>>
From: Ivan Khoronzhuk
Date: Tue, 12 Dec 2017 23:06:35 +0200
> It's not correct to return NULL when that is actually an error and
> function returns errors in any other wrong case. In the same time,
> the cpsw driver and davinci emac doesn't check error case while
> creating channel and it can mis
This patch fix brace on next line coding style errors reported by
checkpatch.
Signed-off-by: Tomas Marek
---
drivers/staging/vc04_services/interface/vchiq_arm/vchiq_shim.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/staging/vc04_services/interface/vchiq_arm/vchi
On Wed, 13 Dec 2017, Thomas Gleixner wrote:
> On Wed, 13 Dec 2017, Linus Torvalds wrote:
>
> > On Wed, Dec 13, 2017 at 8:41 AM, Thomas Gleixner wrote:
> > >
> > > Definitely. That was fragile forever but puzzles me is that I can't figure
> > > out what now causes that spurious interrupt to surfac
Em Wed, Dec 13, 2017 at 03:01:53PM +0800, Mengting Zhang escreveu:
> While monitoring a multithread process with pid option, perf sometimes
> may return sys_perf_event_open failure with 3(No such process) if any
> of the process's threads die before we open the event. However, we want
> perf contin
On Wed, Dec 13, 2017 at 07:49:03PM +, Roman Gushchin wrote:
> Add the corresponding section in cgroup v2 documentation.
>
> Signed-off-by: Roman Gushchin
> Cc: Tejun Heo
> Cc: Alexei Starovoitov
> Cc: kernel-t...@fb.com
> Cc: cgro...@vger.kernel.org
> Cc: linux-...@vger.kernel.org
> Cc: lin
This looks okay to me. Although we should change eaction->tv_* type
to 64-bit as well.
I'll roll this in to our next pull request.
thanks,
Sinclair
On Mon, Nov 27, 2017 at 12:16:19PM +0100, Arnd Bergmann wrote:
> DRM_VMW_EVENT_FENCE_SIGNALED (struct drm_vmw_event_fence) and
> DRM_EVENT_VBLANK
Em Wed, Dec 13, 2017 at 03:01:53PM +0800, Mengting Zhang escreveu:
> While monitoring a multithread process with pid option, perf sometimes
> may return sys_perf_event_open failure with 3(No such process) if any
> of the process's threads die before we open the event. However, we want
> perf contin
Hi Colin,
On Wed, 13 Dec 2017 20:49:09 +
Colin King wrote:
> From: Colin Ian King
>
> There are two error return paths that are not kfree'ing ep that
> lead to memory leaks. Fix this by exiting on error via the
> ext_out exit path that performs the necessary kfree.
Well, given that no on
On Wed, 13 Dec 2017, Thomas Gleixner wrote:
> On Wed, 13 Dec 2017, Thomas Gleixner wrote:
> > On Wed, 13 Dec 2017, Linus Torvalds wrote:
> >
> > > On Wed, Dec 13, 2017 at 8:41 AM, Thomas Gleixner
> > > wrote:
> > > >
> > > > Definitely. That was fragile forever but puzzles me is that I can't
>
Improve the DTS files by removing all the leading "0x" and zeros to fix the
following dtc warnings:
Warning (unit_address_format): Node /XXX unit name should not have leading "0x"
and
Warning (unit_address_format): Node /XXX unit name should not have leading 0s
Converted using the following com
- Original Message -
> From: "Konrad Rzeszutek Wilk"
> To: "Paolo Bonzini"
> Cc: linux-kernel@vger.kernel.org, k...@vger.kernel.org, "Jim Mattson"
> , "Wanpeng Li"
>
> Sent: Wednesday, December 13, 2017 4:59:47 PM
> Subject: Re: [PATCH] KVM: vmx: shadow more fields that are read/writt
On 13/12/17 21:02, Boris Brezillon wrote:
> Hi Colin,
>
> On Wed, 13 Dec 2017 20:49:09 +
> Colin King wrote:
>
>> From: Colin Ian King
>>
>> There are two error return paths that are not kfree'ing ep that
>> lead to memory leaks. Fix this by exiting on error via the
>> ext_out exit path th
On 12/13/2017 06:45 AM, Lorenzo Pieralisi wrote:
+/*
+ * Erratum 44 for QDF2432v1 and QDF2400v1 SoCs describes the BUSY bit as
+ * occasionally getting stuck as 1. To avoid the potential for a hang, check
+ * TXFE == 0 instead of BUSY == 1. This may not be suitable for all UART
+ * implementation
201 - 300 of 1055 matches
Mail list logo
