This is the start of the stable review cycle for the 4.14.54 release.
There are 61 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made by Sun Jul 8 05:46:58 UTC 2018.
Anything receiv
4.17-stable review patch. If anyone has any objections, please let me know.
--
From: Sean Nyekjaer
commit df07101e1c4a29e820df02f9989a066988b160e6 upstream.
According to the reference manual the shp_2_mcu / mcu_2_shp
scripts must be used for devices connected through the SPBA.
4.17-stable review patch. If anyone has any objections, please let me know.
--
From: Taehee Yoo
commit adc972c5b88829d38ede08b1069718661c7330ae upstream.
When depth of chain is bigger than NFT_JUMP_STACK_SIZE, the nft_do_chain
crashes. But there is no need to crash hard here.
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Karoly Pados
commit 2f839823382748664b643daa73f41ee0cc01ced6 upstream.
Silicon Labs defines alternative VID/PID pairs for some chips that when
used will automatically install drivers for Windo
4.17-stable review patch. If anyone has any objections, please let me know.
--
From: Neil Armstrong
commit d511b3e4087eedbe11c7496c396432b8b7c2d7d9 upstream.
Like LibreTech-CC, the USB0 needs the 5V regulator to be enabled to power the
devices on the P212 Reference Design base
4.17-stable review patch. If anyone has any objections, please let me know.
--
From: Alexander Potapenko
commit 21eff690e766ca0ce445b477698dc6a9f55a upstream.
KMSAN reported an infoleak when reading from /dev/vcs*:
BUG: KMSAN: kernel-infoleak in vcs_read+0x18ba/0x1cc0
4.17-stable review patch. If anyone has any objections, please let me know.
--
From: Zhengjun Xing
commit d850c1658328e757635a46763783c6fd56390dcb upstream.
commit 44a182b9d177 ("xhci: Fix use-after-free in xhci_free_virt_device")
set dev->udev pointer to NULL in xhci_free_dev
4.17-stable review patch. If anyone has any objections, please let me know.
--
From: Kenneth Graunke
commit 7a3727f385dc64773db1c144f6b15c1e9d4735bb upstream.
The SF and clipper units mishandle the provoking vertex in some cases,
which can cause misrendering with shaders that
4.17-stable review patch. If anyone has any objections, please let me know.
--
From: Andy Shevchenko
commit 20dcff436e9fcd2e106b0ccc48a52206bc176d70 upstream.
After the commit
7d8905d06405 ("serial: 8250_pci: Enable device after we check black list")
pure serial multi-port
4.17-stable review patch. If anyone has any objections, please let me know.
--
From: Leonard Crestez
commit b02ec67a8e38875cdc5f9214be885022f11c0017 upstream.
Interrupts are ignored if no event bit is set in the status status
register and this breaks the buffer interface. No d
4.17-stable review patch. If anyone has any objections, please let me know.
--
From: Florian Westphal
commit fc6ddbecce440df74fb4491c17c372b52cf5be83 upstream.
This needs to use xt_unregister_targets, else new revision is left
on the list which then causes list to point to a t
4.17-stable review patch. If anyone has any objections, please let me know.
--
From: Laura Abbott
commit 0a2bc00341dcfcc793c0dbf4f8d43adf60458b05 upstream.
The expected return value from ion_map_kernel is an ERR_PTR. The error
path for a vmalloc failure currently just returns
4.17-stable review patch. If anyone has any objections, please let me know.
--
From: Stefan Agner
commit 9fcf2b3c1c0276650fea537c71b513d27d929b05 upstream.
The statement always evaluates to true since the struct fields
are arrays. This has shown up as a warning when compiling
4.17-stable review patch. If anyone has any objections, please let me know.
--
From: Tetsuo Handa
commit ebec3f8f5271139df618ebdf8427e24ba102ba94 upstream.
syzbot is reporting stalls at __process_echoes() [1]. This is because
since ldata->echo_commit < ldata->echo_tail becomes
4.17-stable review patch. If anyone has any objections, please let me know.
--
From: Harry Wentland
commit d9fda248046ac035f18a6e663f2f9245b4bf9470 upstream.
We've had a number of users report failures to detect and light up
display with DC with LVDS and VGA. These connector t
4.17-stable review patch. If anyone has any objections, please let me know.
--
From: Paul Kocialkowski
commit 58b3d02f066e5b1480d80bd308c545526eea3250 upstream.
This reverts commit 2c17a4368aad2b88b68e4390c819e226cf320f70.
The offending commit triggers a run-time fault when a
4.17-stable review patch. If anyone has any objections, please let me know.
--
From: Mikita Lipski
commit 5326c4525d1b2d5f1519268dd305e19c9bd4ef56 upstream.
Clear connector's edid pointer on coonnector update, when unplugging
the display.
Fix poison EDID when hotplugging on p
4.17-stable review patch. If anyone has any objections, please let me know.
--
From: Johan Hovold
commit 24160628a34af962ac99f2f58e547ac3c4cbd26f upstream.
Add device ids for CESINEL products.
Reported-by: Carlos Barcala Lara
Cc: stable
Signed-off-by: Johan Hovold
Signed-o
4.17-stable review patch. If anyone has any objections, please let me know.
--
From: Peter Chen
commit d5a4f93511b7000183c0d528739b824752139f79 upstream.
The port->logbuffer_head may be wrong if the two processes enters
_tcpm_log at the mostly same time. The 2nd process enters
4.17-stable review patch. If anyone has any objections, please let me know.
--
From: Tetsuo Handa
commit 3d63b7e4ae0dc5e02d28ddd2fa1f945defc68d81 upstream.
syzbot is reporting stalls at n_tty_receive_char_special() [1]. This is
because comparison is not working as expected sin
This is the start of the stable review cycle for the 4.17.5 release.
There are 46 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made by Sun Jul 8 05:45:10 UTC 2018.
Anything receive
4.17-stable review patch. If anyone has any objections, please let me know.
--
From: Houston Yaroschoff
commit 4a762569a2722b8a48066c7bacf0e1dc67d17fa1 upstream.
Uniden UBC125 radio scanner has USB interface which fails to work
with cdc_acm driver:
usb 1-1.5: new full-speed
On Thu, Jul 05, 2018 at 02:14:28PM -0700, Joe Perches wrote:
> On Thu, 2018-07-05 at 11:19 -0700, Prakruthi Deepak Heragu wrote:
> > mb() API can relpace the dsb() API in the kernel code. So, dsb() usage
> > is discouraged. However, there are exceptions when dsb is used in a
> > variable or a funct
Hi all,
Changes since 20180705:
The slave-dma tree lost its build failure.
The ida tree lost its build failures.
Non-merge commits (relative to Linus' tree): 4035
4265 files changed, 152245 insertions(+), 90909 dele
On Tue 03-07-18 09:01:01, Paul E. McKenney wrote:
> On Tue, Jul 03, 2018 at 09:24:13AM +0200, Michal Hocko wrote:
> > On Mon 02-07-18 14:37:14, Paul E. McKenney wrote:
> > [...]
> > > commit d2b8d16b97ac2859919713b2d98b8a3ad22943a2
> > > Author: Paul E. McKenney
> > > Date: Mon Jul 2 14:30:37 20
On Thu 05-07-18 16:46:21, Andrew Morton wrote:
> On Thu, 21 Jun 2018 14:35:20 -0700 (PDT) David Rientjes
> wrote:
>
> > The oom reaper ensures forward progress by setting MMF_OOM_SKIP itself if
> > it cannot reap an mm. This can happen for a variety of reasons,
> > including:
> >
> > - the in
This patch adds the devicetree bindings for Maxim's ds2760 battery
monitors.
Signed-off-by: Daniel Mack
---
.../bindings/power/supply/maxim,ds2760.txt| 26 +++
1 file changed, 26 insertions(+)
create mode 100644
Documentation/devicetree/bindings/power/supply/maxim,ds2760.tx
This patch adds a generic w1 bindings document that describes how w1
slave deviceses are grouped under master nodes. It also augments the
existing w1-gpio.txt document a bit.
Signed-off-by: Daniel Mack
---
.../devicetree/bindings/w1/w1-gpio.txt| 11 +---
Documentation/devicetree/bind
This patch removes the w1 slave driver that used to register the w1 family
and instanciate a platform device at runtime. The code now lives in the
supply driver instead to avoid that level of indirection.
The old device name "ds2760-battery.0" is preserved, so userspace
applications can access the
Once a new slave device is detected, match it against all sub-nodes of the
master bus controller. If a match is found, set the slave device's of_node
pointer.
Signed-off-by: Daniel Mack
---
drivers/w1/w1.c| 3 +++
include/linux/w1.h | 2 ++
2 files changed, 5 insertions(+)
diff --git a/driv
Add a matching table for devicetree probing, and optionally set the module
parameter variables from DT properties.
Signed-off-by: Daniel Mack
---
drivers/power/supply/ds2760_battery.c | 29 ++-
1 file changed, 28 insertions(+), 1 deletion(-)
diff --git a/drivers/power/su
This patch set contains five patches that bring devicetree
functionality to w1 bus masters and slaves in general. As an example,
the ds2760 driver is made aware of devicetree probing. Other drivers
can easily be ported later.
W1 masters scan their bus in order to discover slave devices. Once
one i
On Friday, July 06, 2018 01:32 AM, Rob Herring wrote:
On Wed, Jul 04, 2018 at 06:44:08AM +0200, Daniel Mack wrote:
This patch adds a generic w1 bindings document that merely describes how
slave deviceses are grouped under master nodes. It also adds a specific
binding for the ds2760 battery monit
Fully initialize the aa_perms struct in profile_query_cb() to avoid the
potential of using an uninitialized struct member's value in a response
to a query from userspace.
Detected by CoverityScan CID#1415126 ("Uninitialized scalar variable")
Fixes: 4f3b3f2d79a4 ("apparmor: add profile permission
Don't read past the end of the buffer containing permissions
characters or write past the end of the destination string.
Detected by CoverityScan CID#1415361, 1415376 ("Out-of-bounds access")
Fixes: e53cfe6c7caa ("apparmor: rework perm mapping to a slightly broader set")
Signed-off-by: Tyler Hick
This set fixes three issues, discovered by CoverityScan, that I don't
believe are serious in practice but are worth fixing to make the
AppArmor code more robust and prevent them from becoming more serious
issues in the future. The first patch fixes possible out of bounds
access issues when mapping
On Mon, Jul 02, 2018 at 01:30:19AM +0800, Guo Ren wrote:
> +static int csky_of_cpu(struct device_node *node)
> +{
> + const char *status;
> + int cpu;
> +
> + if (of_property_read_u32(node, "reg", &cpu))
> + goto error;
> +
> + if (cpu >= NR_CPUS)
> + goto er
Am 05.07.2018 um 18:56 schrieb Takashi Iwai:
> On Thu, 05 Jul 2018 18:02:11 +0200,
> Rafael J. Wysocki wrote:
>>
>> [The Lv's address is not valid any more, so drop it from the CC]
>>
>> On Thursday, July 5, 2018 5:10:20 PM CEST Rafael J. Wysocki wrote:
>>> On Thu, Jul 5, 2018 at 5:09 PM, Takash
On Fri, Jul 6, 2018 at 2:07 AM Rob Herring wrote:
>
> On Wed, Jul 04, 2018 at 10:56:26PM +0530, Amit Kucheria wrote:
> > On Tue, Jul 3, 2018 at 9:56 PM, Rob Herring wrote:
> > > On Mon, Jul 02, 2018 at 06:14:07PM +0530, Amit Kucheria wrote:
> > >> SDM845 uses v2.4.0 of the TSENS IP block but the
Please do not comment out unneeded code, but remove it.
Signed-off-by: Masahiro Yamada
---
drivers/gpu/drm/bridge/synopsys/Makefile | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/gpu/drm/bridge/synopsys/Makefile
b/drivers/gpu/drm/bridge/synopsys/Makefile
index 5dad97d..3e1b1e3 10
During the processing of headless pages in z3fold_reclaim_page(),
there was a problem that the zhdr pointed to another page
or a page was already released in z3fold_free(). So, the wrong page
is encoded in headless, or test_bit does not work properly
in z3fold_reclaim_page(). This patch fixed these
On 05-07-18, 17:59, Loic Pallardy wrote:
> If rproc_start() failed, rproc_resource_cleanup() is called to clean
> debufs entries, then associated iommu mappings, carveouts and vdev.
typo debufs...
> Issue occurs when rproc_free_vring() is trying to reset vring resource
> table entry.
> At this ti
> -Original Message-
> From: Thomas Gleixner
> Sent: Thursday, July 5, 2018 3:46 PM
> To: Ingo Molnar
> Cc: KY Srinivasan ; x...@kernel.org;
> gre...@linuxfoundation.org; linux-kernel@vger.kernel.org;
> de...@linuxdriverproject.org; o...@aepfle.de; a...@canonical.com;
> jasow...@redhat
From: Li Yu
Add optional property hisilicon,dma-min-chan for k3dma.
Signed-off-by: Li Yu
Signed-off-by: Guodong Xu
---
Documentation/devicetree/bindings/dma/k3dma.txt | 6 ++
1 file changed, 6 insertions(+)
diff --git a/Documentation/devicetree/bindings/dma/k3dma.txt
b/Documentation/dev
This patchset fixes bug people found on hikey960 when allocating DMA
channels to peripherals such as SPI. It fails because the channel is
reserved and not accessible by kernel.
Patch 1, 2 and 3 add support to reserved channels for K3 DMA. Patch 4
includes a removal of axi_config who controls DMA s
From: Li Yu
On k3 series of SoC, DMA controller reserves some channels for
other on-chip coprocessors. By reading property "hisilicon,dma-min-chan"
from dts node, kernel will not use these reserved channels.
As an example, on Hi3660, channel 0 is reserved for lpm3.
Refer to Documentation/device
Update property name dma-min-chan to "hisilicon,dma-min-chan"
Signed-off-by: Guodong Xu
---
arch/arm64/boot/dts/hisilicon/hi3660.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm64/boot/dts/hisilicon/hi3660.dtsi
b/arch/arm64/boot/dts/hisilicon/hi3660.dtsi
index 8
From: Li Yu
Axi_config controls whether DMA resources can be accessed in non-secure
mode, such as linux kernel. The setting is actually done in
bootloader stage.
This patch removes axi_config from k3dma driver.
Signed-off-by: Li Yu
Signed-off-by: Guodong Xu
---
drivers/dma/k3dma.c | 3 ---
1
Looks ok to me.
Reviewed-by: Hamish Martin
On 07/06/2018 02:57 PM, xiu...@redhat.com wrote:
> From: Xiubo Li
>
> For the target_core_user use case, after the device is unregistered
> it maybe still opened in user space, then the kernel will crash, like:
>
> [ 251.163692] BUG: unable to handle
Looks ok to me.
Reviewed-by: Hamish Martin
On 07/06/2018 02:57 PM, xiu...@redhat.com wrote:
> From: Xiubo Li
>
> We are hitting a regression with the following commit:
>
> commit a93e7b331568227500186a465fee3c2cb5dffd1f
> Author: Hamish Martin
> Date: Mon May 14 13:32:23 2018 +1200
>
>
Hi Xiubo,
Thanks for your patch that addresses the regression found with my
earlier commit.
I will take your code and run it in our scenario that showed the bug
that led to my commit. Unfortunately I won't be able to get that done
until mid-next week. I intend to report back to you by July 13t
On Wed, Jul 4, 2018 at 9:14 AM Guodong Xu wrote:
>
> On Wed, Jul 4, 2018 at 2:54 AM Rob Herring wrote:
> >
> > On Fri, Jun 22, 2018 at 11:24:14AM +0800, Guodong Xu wrote:
> > > From: Li Yu
> > >
> > > Add optional property dma_min_chan for k3dma.
> > >
> > > Signed-off-by: Li Yu
> > > ---
> > >
On Thu, Jun 28, 2018 at 2:02 PM Vinod wrote:
>
> On 22-06-18, 11:24, Guodong Xu wrote:
> > From: Li Yu
> >
> > On k3 series of SoC, DMA controller reserves some channels for
> > other on-chip coprocessors. By adding support to dma_min_chan, kernel
> > will not be able to use these reserved channe
From: Xiubo Li
Prepraing for changing to use mutex lock.
Signed-off-by: Xiubo Li
---
drivers/uio/uio.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/uio/uio.c b/drivers/uio/uio.c
index e8f4ac9..b4b2ae1 100644
--- a/drivers/uio/uio.c
+++ b/drivers/uio/uio.c
@@
From: Xiubo Li
The V2 patch set maybe not post successfully, so post it again
with one new updation.
V2:
- resend it with some small fix
V3:
- switch to use request_threaded_irq
Xiubo Li (3):
uio: use request_threaded_irq instead
uio: change to use the mutex lock instead of the spin lock
From: Xiubo Li
We are hitting a regression with the following commit:
commit a93e7b331568227500186a465fee3c2cb5dffd1f
Author: Hamish Martin
Date: Mon May 14 13:32:23 2018 +1200
uio: Prevent device destruction while fds are open
The problem is the addition of spin_lock_irqsave in uio_wri
From: Xiubo Li
For the target_core_user use case, after the device is unregistered
it maybe still opened in user space, then the kernel will crash, like:
[ 251.163692] BUG: unable to handle kernel NULL pointer dereference at
0008
[ 251.163820] IP: [] show_name+0x23/0x40 [uio]
[ 2
On Thu, Jul 5, 2018 at 1:24 AM, Ingo Molnar wrote:
>
> * Dan Williams wrote:
>
>> The calculation of a uniform numa-node size attempted to perform
>> division with a 64-bit diviser leading to the following failure on
>> 32-bit:
>>
>> arch/x86/mm/numa_emulation.o: In function
>> `split_nodes_
2018-07-05 7:49 GMT+09:00 Randy Dunlap :
> From: Randy Dunlap
>
> Update Documentation/kbuild/kconfig.txt, which mostly contains
> user help for using the kernel config tools.
>
> - Add mention of 'nconfig' embedded help text.
> - Make the section on new config symbols readable.
> - Correct how to
On Fri, 2018-07-06 at 04:08 +0800, Rob Herring wrote:
> On Tue, Jul 3, 2018 at 5:39 PM houlong wei wrote:
> >
> > On Tue, 2018-07-03 at 10:30 +0800, Rob Herring wrote:
> > > On Wed, Jun 27, 2018 at 07:16:09PM +0800, Houlong Wei wrote:
> > > > This adds documentation for the MediaTek Global Command
On Thu, Jul 5, 2018 at 6:06 AM, Gustavo A. R. Silva
wrote:
> Add suffix ULL to constant 256 in order to give the compiler complete
> information about the proper arithmetic to use.
>
> Notice that such constant is used in a context that expects an
> expression of type u64 (64 bits, unsigned) and t
On Wed, 2018-07-04 at 17:03 +0800, CK Hu wrote:
> Hi, Houlong:
>
> On Wed, 2018-07-04 at 08:10 +0800, houlong wei wrote:
> > On Fri, 2018-06-29 at 15:08 +0800, CK Hu wrote:
> > > Hi, Houlong:
> > >
> > > Some inline comment.
> > >
> > > On Wed, 2018-06-27 at 19:16 +0800, Houlong Wei wrote:
> > >
I am leaving IBM and will move on to other working area,
so remove myself as a vfio-ccw maintainer.
Signed-off-by: Dong Jia Shi
---
I've enjoyed working with you guys. Hope to meet you in future,
until then, thank you for all your coach and help, please take
care, and farewell.
[I've send you m
Hi Pavel, sorry for the late reply
On 6/30/2018 1:07 AM, Pavel Tatashin Wrote:
> On Thu, Jun 28, 2018 at 10:30 PM Jia He wrote:
>>
>> Commit b92df1de5d28 ("mm: page_alloc: skip over regions of invalid pfns
>> where possible") optimized the loop in memmap_init_zone(). But it causes
>> possible p
> >> Lustre has a private interval-tree implementation. This
> >> implementation (inexplicably) refuses to insert an interval if an
> >> identical interval already exists. It is OK with all sorts of
> >> overlapping intervals, but identical intervals are rejected.
> >
> > I talked to Oleg about
On Wed, 2018-07-04 at 10:39 +0800, CK Hu wrote:
> Hi, Houlong:
>
> On Wed, 2018-07-04 at 08:47 +0800, houlong wei wrote:
> > On Fri, 2018-06-29 at 17:22 +0800, CK Hu wrote:
> > > Hi, Houlong:
> > >
> > > On Fri, 2018-06-29 at 07:32 +0800, houlong wei wrote:
> > > > On Thu, 2018-06-28 at 18:41 +08
Hi Andrew, Kees,
About the implemention of walk_system_ram_res_rev(), it was posted by
AKASHI firstly for his arm kexec_file adding, later he dropped it
because he took other way and doesn't need walk_system_ram_res_rev() any
more in his patchset.
Then I found my below patch needs a walk_system_
On Thu, 2018-07-05 at 16:58 -0700, Andrew Morton wrote:
> On Tue, 03 Jul 2018 14:45:15 +0800 Ian Kent wrote:
>
> > Initial patch contributed by Tomas Bortoli.
> >
> > The autofs subsystem does not check that the "path" parameter is
> > present for all cases where it is required when it is passed
From: Changbin Du
The function_graph tracer does not show the interrupt return marker for the
leaf entry. On leaf entries, we see an unbalanced interrupt marker (the
interrupt was entered, but nevern left).
Before:
1) | SyS_write() {
1) |__fdget_pos() {
1) 0
From: Yisheng Xie
clear_ftrace_function is not used outside of ftrace.c and is not help to
use a function, so nuke it per Steve's suggestion.
Link:
http://lkml.kernel.org/r/1517537689-34947-1-git-send-email-xieyishe...@huawei.com
Suggested-by: Steven Rostedt
Signed-off-by: Yisheng Xie
Signed
From: "Steven Rostedt (VMware)"
The comment in create_filter() states that the passed in filter pointer
(filterp) will either be NULL or contain an error message stating why the
filter failed. But it also expects the filter pointer to point to NULL when
passed in. If it is not, the function creat
Linus,
While cleaning out my INBOX, I found a few patches that were lost
in the noise. These are minor bug fixes and clean ups. Those include:
- Avoiding a string overflow
- Code that didn't match the comment (but should)
- A small code optimization (use of a conditional)
- Quieting printf
From: Arnd Bergmann
'err' is used as a NUL-terminated string, but using strncpy() with the length
equal to the buffer size may result in lack of the termination:
kernel/trace/trace_events_hist.c: In function 'hist_err_event':
kernel/trace/trace_events_hist.c:396:3: error: 'strncpy' specified bou
From: yuan linyu
Simplify and optimize the logic in trace_buffer_iter() to use a conditional
operation instead of an if conditional.
Link: http://lkml.kernel.org/r/20180408113631.3947-1-cug...@163.com
Signed-off-by: yuan linyu
Signed-off-by: Steven Rostedt (VMware)
---
kernel/trace/trace.h |
2018-07-05 4:57 GMT+09:00 Randy Dunlap :
> From: Randy Dunlap
>
> In Kbuild documentation, add alias for 64-bit sh ARCH ("sh64")
> to the list of ARCH aliases.
>
> Signed-off-by: Randy Dunlap
> ---
> Documentation/kbuild/kbuild.txt |1 +
> 1 file changed, 1 insertion(+)
>
> --- linux-next-20
2018-07-05 11:22 GMT+09:00 Randy Dunlap :
> On 07/04/18 18:49, Masahiro Yamada wrote:
>> 2018-07-05 4:59 GMT+09:00 Randy Dunlap :
>>> From: Randy Dunlap
>>>
>>> Removed Kbuild documentation for INSTALL_FW_PATH.
>>>
>>> The kbuild symbol INSTALL_FW_PATH was removed from Kbuild tools in
>>> Septembe
On 7 June 2018 at 17:09, Joel Stanley wrote:
> This is used by the host to talk to the BMC's PCIe slave device. The BMC
> is not involved, but the clock needs to be enabled so the host can use
> the device.
>
> Fixes: 15ed8ce5f84e ("clk: aspeed: Register gated clocks")
> Cc: sta...@vger.kernel.org
2018-07-05 11:47 GMT+09:00 Randy Dunlap :
> From: Randy Dunlap
>
> Add usage info for the Kbuild environment variable KBUILD_KCONFIG.
>
> Signed-off-by: Randy Dunlap
Applied to linux-kbuild. Thanks!
--
Best Regards
Masahiro Yamada
Hi Hans,
[...]
> So digging a bit deeper I just realized that another important
> difference
> between med_power_with_dipm and min_power is that min_power by
> default
> set the ASP bits making the link go to the slumber state instead of
> to
> the partial (power-saving) state.
>
> According to
2018-07-05 4:57 GMT+09:00 Randy Dunlap :
> From: Randy Dunlap
>
> In Kbuild documentation, add alias for 64-bit sh ARCH ("sh64")
> to the list of ARCH aliases.
>
> Signed-off-by: Randy Dunlap
> ---
> Documentation/kbuild/kbuild.txt |1 +
> 1 file changed, 1 insertion(+)
>
> --- linux-next-20
2018-07-02 11:46 GMT+09:00 Randy Dunlap :
> From: Randy Dunlap
>
> Verify that 'depmod' ($DEPMOD) is installed.
> This is a partial revert of 620c231c7a7f (from 2012):
> ("kbuild: do not check for ancient modutils tools")
>
> Also update Documentation/process/changes.rst to refer to
> kmod inste
From: Xiubo Li
We are hitting a regression with the following commit:
commit a93e7b331568227500186a465fee3c2cb5dffd1f
Author: Hamish Martin
Date: Mon May 14 13:32:23 2018 +1200
uio: Prevent device destruction while fds are open
The problem is the addition of spin_lock_irqsave in uio_wri
From: Xiubo Li
V2:
- resend it with some small fix
Xiubo Li (2):
uio: change to use the mutex lock instead of the spin lock
uio: fix crash after the device is unregistered
drivers/uio/uio.c | 142 ++---
include/linux/uio_driver.h | 2 +-
2
From: Xiubo Li
For the target_core_user use case, after the device is unregistered
it maybe still opened in user space, then the kernel will crash, like:
[ 251.163692] BUG: unable to handle kernel NULL pointer dereference at
0008
[ 251.163820] IP: [] show_name+0x23/0x40 [uio]
[ 2
On Tue, 03 Jul 2018 14:45:15 +0800 Ian Kent wrote:
> Initial patch contributed by Tomas Bortoli.
>
> The autofs subsystem does not check that the "path" parameter is
> present for all cases where it is required when it is passed in
> via the "param" struct.
>
> In particular it isn't checked fo
Replaces instances of "unsigned" with "unsigned int" in pinctrl-mt7621.c
Signed-off-by: Peter Vernia
---
drivers/staging/mt7621-pinctrl/pinctrl-rt2880.c | 27 +
1 file changed, 14 insertions(+), 13 deletions(-)
diff --git a/drivers/staging/mt7621-pinctrl/pinctrl-rt2880.c
On Thu, 21 Jun 2018 14:35:20 -0700 (PDT) David Rientjes
wrote:
> The oom reaper ensures forward progress by setting MMF_OOM_SKIP itself if
> it cannot reap an mm. This can happen for a variety of reasons,
> including:
>
> - the inability to grab mm->mmap_sem in a sufficient amount of time,
>
I didn’t try FLATMEM. Thanks for advising, I enabled FLATMEM for ARM64 and am
able to save ~14M. Will post a new patch for Kconfig changes.
Thanks,
-Nikunj
On 7/5/18, 11:35 AM, "Catalin Marinas" wrote:
On Tue, Jul 03, 2018 at 06:35:32PM +, Nikunj Kela (nkela) wrote:
> We are trying
On Wed, Jul 04, 2018 at 11:22:12AM -0700, Ray Jui wrote:
> Add binding document for Stingray PCIe PHYs for both PAXB and PAXC based
> root complex
>
> Signed-off-by: Ray Jui
> ---
> .../devicetree/bindings/phy/brcm,sr-pcie-phy.txt | 41
> ++
> 1 file changed, 41 insertions
On Wed, Jul 04, 2018 at 06:44:08AM +0200, Daniel Mack wrote:
> This patch adds a generic w1 bindings document that merely describes how
> slave deviceses are grouped under master nodes. It also adds a specific
> binding for the ds2760 battery monitor.
>
> Signed-off-by: Daniel Mack
> ---
> .../b
On Thu, Jul 05, 2018 at 08:44:10PM +0200, Andrea Parri wrote:
> On Thu, Jul 05, 2018 at 08:38:36PM +0200, Andrea Parri wrote:
> > > No, I'm definitely not pushing for anything stronger. I'm still just
> > > wondering if the name "RCsc" is right for what you described. For
> > > example, Andrea ju
On Thu, Jul 05, 2018 at 08:38:36PM +0200, Andrea Parri wrote:
> > No, I'm definitely not pushing for anything stronger. I'm still just
> > wondering if the name "RCsc" is right for what you described. For
> > example, Andrea just said this in a parallel email:
> >
> > > "RCsc" as ordering everyt
On 2018/7/6 4:56, Jann Horn wrote:
On Thu, Jul 5, 2018 at 10:53 PM wrote:
From: Xiubo Li
For the target_core_user use case, after the device is unregistered
it maybe still opened in user space, then the kernel will crash, like:
[...]
Signed-off-by: Xiubo Li
---
drivers/uio/uio.c | 101 +
On Wed, Jul 04, 2018 at 09:52:53AM +0800, Mars Cheng wrote:
> Update the dt-binding documentation of sysirq for mt6765
>
> Signed-off-by: Mars Cheng
> ---
> .../interrupt-controller/mediatek,sysirq.txt |1 +
> 1 file changed, 1 insertion(+)
Reviewed-by: Rob Herring
On Wed, Jul 04, 2018 at 09:52:51AM +0800, Mars Cheng wrote:
> Update binding document for mt6765 reference board
>
> Signed-off-by: Mars Cheng
> ---
> Documentation/devicetree/bindings/arm/mediatek.txt |4
> 1 file changed, 4 insertions(+)
Reviewed-by: Rob Herring
On Wed, Jul 04, 2018 at 09:52:52AM +0800, Mars Cheng wrote:
> Add documentation for mt6765 uart dt-bindings
>
> Signed-off-by: Mars Cheng
> ---
> .../devicetree/bindings/serial/mtk-uart.txt|1 +
> 1 file changed, 1 insertion(+)
Reviewed-by: Rob Herring
On 2018/7/6 0:33, Greg KH wrote:
On Thu, Jul 05, 2018 at 12:27:27PM -0400, xiu...@redhat.com wrote:
From: Xiubo Li
We are hitting a regression with the following commit:
commit a93e7b331568227500186a465fee3c2cb5dffd1f
Author: Hamish Martin
Date: Mon May 14 13:32:23 2018 +1200
uio: Pr
On Tue, Jul 03, 2018 at 11:25:20AM +0200, Saravanan Sekar wrote:
> Rename document generic to Actions Semi Owl S700/S900 Soc's.
> Add clock bindings constants for action S700
The important think you are doing is adding the S700, so the subject
should reflect that. Renaming is secondary. Please th
This patch adds bindings of new "System Timer" on Mediatek SoCs.
Remove RTC clock in the same time because it is not used by
both "General Purpose Timer" and "System Timer" now.
Signed-off-by: Stanley Chu
---
.../bindings/timer/mediatek,mtk-timer.txt | 34
1 file
Rename mtk_timer to timer-mediatek to apply new naming convention
in clocksource folder.
Signed-off-by: Stanley Chu
---
drivers/clocksource/Makefile |2 +-
drivers/clocksource/mtk_timer.c | 268 --
drivers/clocksource/timer-mediatek.c | 268
101 - 200 of 699 matches
Mail list logo
