On 2019 Mai 15, Kees Cook wrote:
> On Tue, May 14, 2019 at 06:10:55PM +0200, Johannes Hirte wrote:
> > On 2019 Mai 14, Kees Cook wrote:
> > > On Tue, May 14, 2019 at 02:04:21PM +0200, Johannes Hirte wrote:
> > > > This breaks the build on my system:
> > > >
> > > > RELOCS arch/x86/boot/compress
On 16.05.2019 16:32, Jann Horn wrote:
> On Wed, May 15, 2019 at 5:11 PM Kirill Tkhai wrote:
>> This patchset adds a new syscall, which makes possible
>> to clone a mapping from a process to another process.
>> The syscall supplements the functionality provided
>> by process_vm_writev() and process
On 5/15/19 4:54 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.19.44 release.
There are 113 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
On Thu 09-05-19 15:25:26, Vladimir Davydov wrote:
> On Mon, Apr 29, 2019 at 12:59:39PM +0200, Jiri Slaby wrote:
> > We have a single node system with node 0 disabled:
> > Scanning NUMA topology in Northbridge 24
> > Number of physical nodes 2
> > Skipping disabled node 0
> > Node 1 MemBase
This patch makes dw-hdmi pass DRM connector info to a respective
CEC adapter. In order to be able to do that it delays creation of
the dw-hdmi-cec platform device until DRM connector is initialized.
Requires testing.
Signed-off-by: Dariusz Marcinkiewicz
---
drivers/gpu/drm/bridge/synopsys/dw-hd
This patch proposes to expose explicit mapping between HDMI connectors
and /dev/cecX adapters to userland.
New structure with connector info (card number and connector id in case
of DRM connectors) is added to cec_adapter. That connector info is expected
to be provided when an adapter is created.
With that change tda998x provides a connector info to the CEC
adapter. In order to be able to that it delays creation of
respective CEC device until the DRM connector is initialized.
Requires testing.
Signed-off-by: Dariusz Marcinkiewicz
---
drivers/gpu/drm/i2c/tda9950.c | 7 -
dri
On 16.05.19 07:02, Andrew Cooper wrote:
> On 16/05/2019 14:50, Alexander Graf wrote:
>> On 14.05.19 08:16, Filippo Sironi wrote:
>>> Start populating /sys/hypervisor with KVM entries when we're running on
>>> KVM. This is to replicate functionality that's available when we're
>>> running on Xen.
On 5/15/19 4:55 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.9.177 release.
There are 51 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
> From: Anson Huang
> Sent: Thursday, May 16, 2019 8:01 PM
> > >
> > > Add i.MX SCU SoC info driver to support i.MX8QXP SoC, introduce
> > > driver dependency into Kconfig as CONFIG_IMX_SCU must be selected to
> > > support i.MX SCU SoC driver, also need to use platform driver model
> > > to make s
Hi Hans.
From: Hans Verkuil
Date: Thu, May 9, 2019 at 11:31 AM
To: Dariusz Marcinkiewicz
Cc: , ,
> On 5/9/19 9:52 AM, Dariusz Marcinkiewicz wrote:
> > Hi Hans.
> >
> > On Wed, Apr 24, 2019 at 2:09 PM Hans Verkuil wrote:
> >>
> >> Hi Dariusz,
> >>
> >> This is getting close, so I think for the
On 16/05/2019 14:41, Mark Rutland wrote:
> On Thu, May 16, 2019 at 02:38:20PM +0100, Mark Rutland wrote:
>> Hi,
>>
>> Since commit:
>>
>> 54c7a8916a887f35 ("initramfs: free initrd memory if opening /initrd.image
>> fails")
>
> Ugh, I dropped a paragarph here.
>
> Since that commit, I'm seeing
On 16/05/2019 14:50, Alexander Graf wrote:
> On 14.05.19 08:16, Filippo Sironi wrote:
>> Start populating /sys/hypervisor with KVM entries when we're running on
>> KVM. This is to replicate functionality that's available when we're
>> running on Xen.
>>
>> Start with /sys/hypervisor/uuid, which use
On 5/15/19 4:54 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.14.120 release.
There are 115 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 mad
On Thu, May 16, 2019 at 3:08 PM Christian Brauner wrote:
> On Wed, May 15, 2019 at 10:45:06AM -0700, Daniel Colascione wrote:
> > On Wed, May 15, 2019 at 3:04 AM Christian Brauner
> > wrote:
> > >
> > > This adds the pidfd_open() syscall. It allows a caller to retrieve
> > > pollable
> > > pidf
On Jo, 2019-05-16 at 10:14 -0300, Fabio Estevam wrote:
> On Thu, May 16, 2019 at 10:02 AM Viorel Suman wrote:
>
> >
> > + for (i = 0; i < ARRAY_SIZE(ak4458->supplies); i++)
> > + ak4458->supplies[i].supply = ak4458_supply_names[i];
> > +
> > + ret = devm_regulator_bulk_
On Tue, May 14, 2019 at 9:16 AM Kirill A. Shutemov wrote:
> Could you check what khugepaged doing?
>
> cat /proc/$(pidof khugepaged)/stack
It is doing it again, 10:12am - 2019-05-16
PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND
77 root 39 19 0
On 16/05/2019 15:16, Mark Rutland wrote:
> On Thu, May 16, 2019 at 03:05:31PM +0100, Steven Price wrote:
>> On 16/05/2019 14:41, Mark Rutland wrote:
>>> On Thu, May 16, 2019 at 02:38:20PM +0100, Mark Rutland wrote:
Hi,
Since commit:
54c7a8916a887f35 ("initramfs: free init
Hi.
On Thu, May 16, 2019 at 12:44:12PM +0200, Michal Hocko wrote:
> On Thu 16-05-19 11:42:29, Oleksandr Natalenko wrote:
> [...]
> > * to mark all the eligible VMAs as mergeable, use:
> >
> ># echo merge > /proc//madvise
> >
> > * to unmerge all the VMAs, use:
> >
> ># echo unmerge > /p
On 5/16/19 4:10 PM, Dariusz Marcinkiewicz wrote:
> Hi Hans.
>
> From: Hans Verkuil
> Date: Thu, May 9, 2019 at 11:31 AM
> To: Dariusz Marcinkiewicz
> Cc: , ,
>
>
>> On 5/9/19 9:52 AM, Dariusz Marcinkiewicz wrote:
>>> Hi Hans.
>>>
>>> On Wed, Apr 24, 2019 at 2:09 PM Hans Verkuil wrote:
>>>
On Thu, May 16, 2019 at 10:14 AM Justin Piszcz wrote:
>
> On Tue, May 14, 2019 at 9:16 AM Kirill A. Shutemov
> wrote:
>
> > Could you check what khugepaged doing?
> >
> > cat /proc/$(pidof khugepaged)/stack
>
> It is doing it again, 10:12am - 2019-05-16
>
> PID USER PR NIVIRTRES
Provide a wrapper for drm_gem_map_offset() for clients of shmem. This
wrapper provides the correct semantics for the drm_gem_shmem_mmap()
callback.
Signed-off-by: Steven Price
---
drivers/gpu/drm/drm_gem_shmem_helper.c | 20
include/drm/drm_gem_shmem_helper.h | 2 ++
2
On Thu, May 16, 2019 at 02:41:06PM +0100, Mark Rutland wrote:
> On Thu, May 16, 2019 at 02:38:20PM +0100, Mark Rutland wrote:
> > Hi,
> >
> > Since commit:
> >
> > 54c7a8916a887f35 ("initramfs: free initrd memory if opening /initrd.image
> > fails")
>
> Ugh, I dropped a paragarph here.
>
> S
On Thu, May 16, 2019 at 03:05:31PM +0100, Steven Price wrote:
> On 16/05/2019 14:41, Mark Rutland wrote:
> > On Thu, May 16, 2019 at 02:38:20PM +0100, Mark Rutland wrote:
> >> Hi,
> >>
> >> Since commit:
> >>
> >> 54c7a8916a887f35 ("initramfs: free initrd memory if opening
> >> /initrd.image fai
Hi.
On Thu, May 16, 2019 at 12:00:24PM +0200, Jann Horn wrote:
> On Thu, May 16, 2019 at 11:43 AM Oleksandr Natalenko
> wrote:
> > Use previously introduced remote madvise knob to mark task's
> > anonymous memory as mergeable.
> >
> > To force merging task's VMAs, "merge" hint is used:
> >
> >
Hello,
On power9 host, performing memory hotunplug from ppc64le guest results
in kernel oops.
Kernel used : https://github.com/torvalds/linux/tree/v5.1 built using
ppc64le_defconfig for host and ppc64le_guest_defconfig for guest.
Recreation steps:
1. Boot a guest with below mem configurati
On Thu, May 16, 2019 at 03:00:01PM +0300, Laurent Pinchart wrote:
> Hi Sean,
>
> On Mon, May 13, 2019 at 10:38:58AM -0400, Sean Paul wrote:
> > On Sat, May 11, 2019 at 3:12 PM Laurent Pinchart wrote:
> > > On Thu, May 02, 2019 at 03:49:46PM -0400, Sean Paul wrote:
> > >> From: Sean Paul
> > >>
>
On Thu, May 16, 2019 at 05:13:14PM +0300, Mike Rapoport wrote:
> On Thu, May 16, 2019 at 02:41:06PM +0100, Mark Rutland wrote:
> > On Thu, May 16, 2019 at 02:38:20PM +0100, Mark Rutland wrote:
> > > Hi,
> > >
> > > Since commit:
> > >
> > > 54c7a8916a887f35 ("initramfs: free initrd memory if op
On 16.05.2019 16:52, Michal Hocko wrote:
> On Thu 16-05-19 15:30:34, Michal Hocko wrote:
>> [You are defining a new user visible API, please always add linux-api
>> mailing list - now done]
>>
>> On Wed 15-05-19 18:11:15, Kirill Tkhai wrote:
> [...]
>>> The proposed syscall aims to introduce an in
On Thu, 2019-05-16 at 13:00 +, Viorel Suman wrote:
> From: Shengjiu Wang
>
> Add regulator for ak4458.
>
Hi Viorel,
While at it please disable/enable the regulator in suspend/resume.
thanks,
Daniel.
panfrost_ioctl_mmap_bo() contains a reimplementation of
drm_gem_shmem_map_offset() but with a bug - it allows mapping imported
objects (without going through the exporter). Fix this by switching to
use the new drm_gem_shmem_map_offset() function instead which has
the bonus of simplifying the code.
On Wed, May 15, 2019 at 05:21:51PM -0700, Dan Williams wrote:
[..]
> It just seems to me that we should stop pretending that the
> filesystem-dax facility requires block devices and try to move this
> functionality to generically use a dax device across all interfaces.
That sounds reasonable and
On 5/15/19 4:51 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.4.180 release.
There are 266 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
On Thu, May 16, 2019 at 03:21:19PM +0100, Mark Rutland wrote:
> > void __weak free_initrd_mem(unsigned long start, unsigned long end)
> > {
> > + if (!start)
> > + return;
> > +
> > free_reserved_area((void *)start, (void *)end, POISON_FREE_INITMEM,
> >
There is a race condition between removing glue directory and adding a new
device under the glue directory. It can be reproduced in following test:
path 1: Add the child device under glue dir
device_add()
get_device_parent()
mutex_lock(&gdp_mutex);
/*find parent fr
Hi Kieran and Niklas,
thank you for your responses!
> Hi Kieran and Michael,
>
> On 2019-05-10 17:25:24 +0100, Kieran Bingham wrote:
>
>
> >
> > Niklas, how does RCar-CSI determine the top/bottom sequence?
>
> That patch just got merged in the media tree a few days ago,
>
> 9f7983bdc4925ae2
On 16.05.2019 16:42, Adam Borowski wrote:
> On Thu, May 16, 2019 at 04:10:07PM +0300, Kirill Tkhai wrote:
>> On 15.05.2019 22:38, Adam Borowski wrote:
>>> On Wed, May 15, 2019 at 06:11:15PM +0300, Kirill Tkhai wrote:
This patchset adds a new syscall, which makes possible
to clone a mappin
On 5/15/19 4:54 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.18.140 release.
There are 86 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
Support for ad7616 running in software was added. In order
to activate the software mode, HW_RNGSEL pins must be pulled low.
Oversampling and input ranges are now configured in corresponding
registers. Ad7616 has multiple scale options when it is configured
in software mode.
Signed-off-by: Beniami
Add the hdmitx glue device linking the SoC audio interfaces to the
embedded Synopsys hdmi controller.
Signed-off-by: Jerome Brunet
---
Hi Kevin,
The related device driver and dt-binding have been merged in the ASoC
tree, for-5.3 branch [0]
This patch is based on the audio series I have jus
On Fri, 26 Apr 2019 at 16:59, Grzegorz Halat wrote:
>
> After memory allocation failure vc_allocate() doesn't clean up data
> which has been initialized in visual_init(). In case of fbcon this
> leads to divide-by-0 in fbcon_init() on next open of the same tty.
Hi,
A gentle reminder. Could you pl
Support for register access was added for spi devices.
Signed-off-by: Beniamin Bia
---
drivers/iio/adc/ad7606.c | 25 +
1 file changed, 25 insertions(+)
diff --git a/drivers/iio/adc/ad7606.c b/drivers/iio/adc/ad7606.c
index f77df3efe43f..b03bdce4fd4e 100644
--- a/drivers
Power and volume button support for 5th and 6th genration Microsoft
Surface devices via soc_button_array.
Note that these devices use the same MSHW0040 device as on the Surface
Pro 4, however the implementation is different (GPIOs vs. ACPI
notifications). Thus some checking is required to ensure w
Since 54c7a8916a88 ("initramfs: free initrd memory if opening
/initrd.image fails"), the kernel has unconditionally attempted to free
the initrd even if it doesn't exist. In the non-existent case this
causes a boot-time splat if CONFIG_DEBUG_VIRTUAL is enabled due to a
call to virt_to_phys() with a
In order to support AD7616 software mode, the spi register access must be
added and the calculation of registers address must be generic.
The length of address and bit which specifies the read/write operation is
different for every device, that is why it was made generic.
Signed-off-by: Beniamin B
Do not use the surfacepro3_button driver on newer Microsoft Surface
models, only use it on the Surface Pro 3 and 4. Newer models (5th, 6th
and possibly future generations) use the same device as the Surface Pro
4 to represent their volume and power buttons (MSHW0040), but their
acutal implementatio
On Thu, May 16, 2019 at 03:20:59PM +0100, Steven Price wrote:
> On 16/05/2019 15:16, Mark Rutland wrote:
> > On Thu, May 16, 2019 at 03:05:31PM +0100, Steven Price wrote:
> >> I suspect the following is sufficient to fix the problem:
> >>
> >> 8<-
> >> diff --git a/init/initramfs.c b/init/i
The device dependent options which are going to be different for devices
which will be supported in the future by this driver,
were moved in chip info for a more generic driver. This patch allows
supporting more devices by the driver. Also, it is an intermediate
step of adding support for ad7616 i
Because this driver will support multiple configurations for software,
the software configuration was made generic.
Signed-off-by: Beniamin Bia
---
drivers/iio/adc/ad7606.c | 40 +---
drivers/iio/adc/ad7606.h | 2 ++
2 files changed, 39 insertions(+), 3 delet
On Thu, May 16, 2019 at 11:36:39AM +0100, Raphael Gault wrote:
> Noteworthy points:
> * I still haven't figured out how to detect switch-tables on arm64. I
> have a better understanding of them but still haven't implemented checks
> as it doesn't look trivial at all.
Switch tables were tricky to g
On Thu, May 16, 2019 at 10:17 AM Justin Piszcz wrote:
>
> On Thu, May 16, 2019 at 10:14 AM Justin Piszcz
> wrote:
> >
> > On Tue, May 14, 2019 at 9:16 AM Kirill A. Shutemov
> > wrote:
> >
> > > Could you check what khugepaged doing?
> > >
> > > cat /proc/$(pidof khugepaged)/stack
> >
> > It is
This series adds suport for power and volume buttons on 5th and 6th
generation Microsoft Surface devices. Specifically, it adds support for
the power-button on the Surface Laptop 1 and Laptop 2, as well as
support for power- and (on-device) volume-buttons on the Surface Pro 5
(2017), Pro 6, and Boo
On 5/14/2019 1:14 PM, Lakshmi wrote:
The motive behind this patch series is to measure the public key
of the IMA signature signer in the IMA log.
I have some questions about the rationale for the design ...
> The IMA signature of the file, logged using ima-sig template, contains
the key ident
On Thu, May 16, 2019 at 5:28 AM Hsin-Yi Wang wrote:
>
> Basically does similar things like __fixmap_remap_fdt(). It's supposed
> to be called after fixmap_remap_fdt() is called at least once, so region
> checking can be skipped. Since it needs to know dt physical address, make
> a copy of the valu
From: Naveen Kumar Parna
According to checkpatch: EXPORT_SYMBOL(foo); should immediately follow its
function/variable.
This patch fixes the following checkpatch.pl issues in drivers/char/misc.c:
WARNING: EXPORT_SYMBOL(foo); should immediately follow its function/variable
Signed-off-by: Naveen K
On Thu, 16 May 2019 at 16:37, Rob Herring wrote:
>
> On Thu, May 16, 2019 at 5:28 AM Hsin-Yi Wang wrote:
> >
> > Basically does similar things like __fixmap_remap_fdt(). It's supposed
> > to be called after fixmap_remap_fdt() is called at least once, so region
> > checking can be skipped. Since i
On Thu, May 16, 2019 at 09:37:05AM -0500, Rob Herring wrote:
> On Thu, May 16, 2019 at 5:28 AM Hsin-Yi Wang wrote:
> >
> > Basically does similar things like __fixmap_remap_fdt(). It's supposed
> > to be called after fixmap_remap_fdt() is called at least once, so region
> > checking can be skipped
On Thu, May 16, 2019 at 04:20:13PM +0200, Oleksandr Natalenko wrote:
> > [...]
> > > @@ -2960,15 +2962,63 @@ static int proc_stack_depth(struct seq_file *m,
> > > struct pid_namespace *ns,
> > > static ssize_t madvise_write(struct file *file, const char __user *buf,
> > > size_t c
On Mon, May 6, 2019 at 12:01 PM Richard Weinberger
wrote:
>
> On Wed, May 1, 2019 at 7:52 PM Kamal Dasu wrote:
> >
> > If mtd_oops is in progress switch to polling for nand command completion
> > interrupts and use PIO mode wihtout DMA so that the mtd_oops buffer can
> > be completely written in
On Thu, May 16, 2019 at 10:37 PM Rob Herring wrote:
>
> Why not just map the FDT R/W at the start and change it to RO just
> before calling unflatten_device_tree? Then all the FDT scanning
> functions or any future fixups we need can just assume R/W. That is
> essentially what Stephen suggested.
Hi David, Christian,
On Thu, May 16, 2019 at 1:54 PM David Howells wrote:
> Wire up the mount API syscalls on non-x86 arches.
>
> Reported-by: Arnd Bergmann
> Signed-off-by: David Howells
> Reviewed-by: Arnd Bergmann
> +428common open_tree sys_open_tree
> +429co
On -rt kernels, it is sometimes desirable to be able to prioritize
some hardware interrupts over others, i.e. being able to set the
priorities of the irq threads different from the default of 50. While
chrt(1) can be used after the threads are created, there are at least
two problems with that: (1)
Since the OOM interrupt directly deals with the binner bo, it doesn't
make sense to try and handle it without a binner buffer registered.
Signed-off-by: Paul Kocialkowski
Reviewed-by: Eric Anholt
---
drivers/gpu/drm/vc4/vc4_irq.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/gp
[Cc Alexey + kvm]
On Thu, 16 May 2019 20:38:26 +0800
"richard.p...@oppo.com" wrote:
> Use a vma helper function to simply code.
>
> Signed-off-by: Peng Hao
> ---
> drivers/vfio/pci/vfio_pci_nvlink2.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/drivers/vfio/pci/
Hi Christian, David,
On Thu, May 16, 2019 at 4:00 PM Christian Brauner wrote:
> This adds the pidfd_open() syscall. It allows a caller to retrieve pollable
> pidfds for a process which did not get created via CLONE_PIDFD, i.e. for a
> process that is created via traditional fork()/clone() calls t
In preparation for wrapping the binner bo allocation helper with
put/get helpers, pass the vc4 dev directly and drop the vc4 prefix.
Signed-off-by: Paul Kocialkowski
Reviewed-by: Eric Anholt
---
drivers/gpu/drm/vc4/vc4_v3d.c | 11 +--
1 file changed, 5 insertions(+), 6 deletions(-)
dif
On Thu, 16 May 2019, Jim Lin wrote:
> The Clear_TT_Buffer request sent to the hub includes the address of
> the LS/FS child device in wValue field. usb_hub_clear_tt_buffer()
> uses udev->devnum to set the address wValue. This won't work for
> devices connected to xHC.
>
> For other host controlle
Check that we have a V3D device registered before attempting to
allocate a binner buffer object.
Signed-off-by: Paul Kocialkowski
Reviewed-by: Eric Anholt
---
drivers/gpu/drm/vc4/vc4_v3d.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/gpu/drm/vc4/vc4_v3d.c b/drivers/gpu/drm/vc4
02.05.2019 4:39, Dmitry Osipenko пишет:
> 02.05.2019 3:52, Dmitry Osipenko пишет:
>> 02.05.2019 3:17, Rob Herring пишет:
>>> On Wed, May 1, 2019 at 7:06 PM Dmitry Osipenko wrote:
30.04.2019 1:05, Rob Herring пишет:
> On Sun, Apr 14, 2019 at 11:20:07PM +0300, Dmitry Osipenko wrote:
>>
Hi YueHaibing,
Thanks for the patch.
On Thu, May 16, 2019 at 9:42 AM YueHaibing wrote:
>
> If ulite_probe is not called or failed to registed
s/registed/register
> uart_register_driver, unload the module will call
> uart_unregister_driver, which will tigger NULL
s/tigger/trigger
> pointer derefer
On Thu, May 16, 2019 at 04:56:08PM +0200, Geert Uytterhoeven wrote:
> Hi Christian, David,
>
> On Thu, May 16, 2019 at 4:00 PM Christian Brauner
> wrote:
> > This adds the pidfd_open() syscall. It allows a caller to retrieve pollable
> > pidfds for a process which did not get created via CLONE_P
On Thu, May 16, 2019 at 08:27:55AM -0600, shuah wrote:
> On 5/15/19 4:54 AM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 3.18.140 release.
> > There are 86 patches in this series, all will be posted as a response
> > to this one. If anyone has any issues with
On Thu, May 16, 2019 at 04:56:10PM +0200, Geert Uytterhoeven wrote:
> Hi David, Christian,
>
> On Thu, May 16, 2019 at 1:54 PM David Howells wrote:
> > Wire up the mount API syscalls on non-x86 arches.
> >
> > Reported-by: Arnd Bergmann
> > Signed-off-by: David Howells
> > Reviewed-by: Arnd Ber
On 5/16/19 10:08 AM, Alexander Graf wrote:
>
> My point is mostly that we should be as common
> as possible when it comes to /sys/hypervisor, so that tools don't have
> to care about the HV they're working against.
It might make sense to have a common sys-hypervisor.c file
(drivers/hypervisor/sys-
diff --git a/Documentation/usb/power-management.txt
b/Documentation/usb/power-management.txt
index 7b90fe034c4b..d3e38fe2091d 100644
--- a/Documentation/usb/power-management.txt
+++ b/Documentation/usb/power-management.txt
@@ -364,11 +364,15 @@ autosuspend the interface's device. When the usage
On Wed, May 15, 2019 at 9:43 PM Eduardo Valentin wrote:
>
> - thermal core has a new devm_* API for registering cooling devices, thanks
> to Guenter R.
> I took the entire series, that is why you see changes on drivers/hwmon in
> this pull.
This clashed badly with commit 6b1ec4789fb1 ("hwmon:
Hi Hans,
On 5/16/19 1:40 PM, Hans Verkuil wrote:
> On 5/16/19 11:56 AM, Tomasz Figa wrote:
>> On Thu, May 16, 2019 at 5:09 PM Stanimir Varbanov
>> wrote:
>>>
>>> Hi Hans,
>>>
>>> On 5/14/19 11:54 AM, Hans Verkuil wrote:
Hi Stanimir,
On 4/12/19 5:59 PM, Stanimir Varbanov wrote:
On Tue, May 14, 2019 at 01:44:35PM -0700, Yang Shi wrote:
> On 5/13/19 11:20 PM, Michal Hocko wrote:
> > On Mon 13-05-19 21:36:59, Yang Shi wrote:
> > > On Mon, May 13, 2019 at 2:45 PM Michal Hocko wrote:
> > > > On Mon 13-05-19 14:09:59, Yang Shi wrote:
> > > > [...]
> > > > > I think we can just
The pull request you sent on Thu, 16 May 2019 12:27:54 +1000:
> git://anongit.freedesktop.org/drm/drm tags/drm-next-2019-05-16
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/cc7ce90153e74f8266eefee9fba466faa1a2d5df
Thank you!
--
Deet-doot-dot, I am a bot.
https://ko
The pull request you sent on Wed, 15 May 2019 21:43:14 -0700:
> git://git.kernel.org/pub/scm/linux/kernel/git/evalenti/linux-soc-thermal linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/a455eda33faafcaac1effb31d682765b14ef868c
Thank you!
--
Deet-doot-dot, I am a
I'm announcing the release of the 3.18.140 kernel.
All users of the 3.18 kernel series must upgrade.
Note, this is the LAST 3.18.y release that I will be doing on
kernel.org. I know it has been marked as End-of-Life for quite some
time, but I have kept it alive due to a few million phones out th
Hi,
On Sun, May 12, 2019 at 11:41:28PM +0200, Ondřej Jirman wrote:
> > > +static int tsens_get_temp(void *data, int *temp)
> > > +{
> > > + struct tsensor *s = data;
> > > + struct tsens_device *tmdev = s->tmdev;
> > > + int val;
> > > +
> > > + regmap_read(tmdev->regmap, tmdev->chip->temp_data_ba
Without USB_QUIRK_NO_LPM ethernet will not work and rtl8152 will
complain with
r8152 : Stop submitting intr, status -71
Adding the quirk resolves this. As the dock is externally powered, this
should not have any drawbacks.
Signed-off-by: Maximilian Luz
---
drivers/usb/core/quirks.c | 3 +++
On Thu, May 16, 2019 at 03:31:25PM +0100, Steven Price wrote:
> Since 54c7a8916a88 ("initramfs: free initrd memory if opening
> /initrd.image fails"), the kernel has unconditionally attempted to free
> the initrd even if it doesn't exist. In the non-existent case this
> causes a boot-time splat if
On 2019-05-16, Oleg Nesterov wrote:
> On 05/17, Aleksa Sarai wrote:
> > On 2019-05-16, Oleg Nesterov wrote:
> > > On 05/16, Christian Brauner wrote:
> > > > With the introduction of pidfds through CLONE_PIDFD it is possible to
> > > > created pidfds at process creation time.
> > >
> > > Now I am
Add pinconf support for PIN_CONFIG_OUTPUT_ENABLE and PIN_CONFIG_OUTPUT
in the meson pinctrl driver.
Signed-off-by: Jerome Brunet
---
drivers/pinctrl/meson/pinctrl-meson.c | 182 ++
1 file changed, 127 insertions(+), 55 deletions(-)
diff --git a/drivers/pinctrl/meson/pinc
This patchset adds output support in the amlogic pinctrl driver.
Linus, this patchset is based on the drive strength series from Guillaume
which you just applied [0]
[0]:
https://lkml.kernel.org/r/cacrpkdz+p-j5em3rzzcuwpa-a+cvoy91cglqorm_qvzp6e4...@mail.gmail.com
Jerome Brunet (2):
dt-binding
add support for the pinconf DT property output-enable, output-disable,
output-low and output-high in the meson pinctrl driver.
Signed-off-by: Jerome Brunet
---
.../devicetree/bindings/pinctrl/meson,pinctrl.txt| 12 +---
1 file changed, 9 insertions(+), 3 deletions(-)
diff --git a/Do
> On 16. May 2019, at 17:02, Boris Ostrovsky wrote:
>
> On 5/16/19 10:08 AM, Alexander Graf wrote:
>>
>> My point is mostly that we should be as common
>> as possible when it comes to /sys/hypervisor, so that tools don't have
>> to care about the HV they're working against.
>
> It might make
On Thu, May 16, 2019 at 9:43 AM Mark Rutland wrote:
>
> On Thu, May 16, 2019 at 09:37:05AM -0500, Rob Herring wrote:
> > On Thu, May 16, 2019 at 5:28 AM Hsin-Yi Wang wrote:
> > >
> > > Basically does similar things like __fixmap_remap_fdt(). It's supposed
> > > to be called after fixmap_remap_fdt
W dniu 15.05.2019 o 17:18, Matthew Wilcox pisze:
> On Wed, May 15, 2019 at 08:02:17AM -0700, Eric Dumazet wrote:
>> On Wed, May 15, 2019 at 7:43 AM Matthew Wilcox wrote:
>>> You're seeing a race between page_address(page) being called twice.
>>> Between those two calls, something has caused the p
Hi rafael,
Thanks for your review.
Rafael J. Wysocki 于2019年5月15日周三 下午4:35写道：
>
> On Wed, May 15, 2019 at 2:57 AM Muchun Song wrote:
> >
> > There is a race condition between removing glue directory and adding a new
> > device under the glue directory. It can be reproduced in following test:
> >
> On 16. May 2019, at 15:56, Graf, Alexander wrote:
>
> On 14.05.19 08:16, Filippo Sironi wrote:
>> On x86, we report the UUID in DMI System Information (i.e., DMI Type 1)
>> as VM UUID.
>>
>> Signed-off-by: Filippo Sironi
>> ---
>> arch/x86/kernel/kvm.c | 7 +++
>> 1 file changed, 7 inser
Hi, Linus,
Please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/rzhang/linux.git next
to receive the latest Thermal management updates for v5.2-rc1 with
top-most commit 6df24c3e81b9ba9c5e8d815e593826c169e3f366:
Merge branches 'thermal-core', 'thermal-built-it' and 'thermal-intel'
- Original Message -
> On Mon, May 13, 2019 at 04:01:09PM -0700, Yang Shi wrote:
> >
> >
> > On 5/13/19 9:38 AM, Will Deacon wrote:
> > > On Fri, May 10, 2019 at 07:26:54AM +0800, Yang Shi wrote:
> > > > diff --git a/mm/mmu_gather.c b/mm/mmu_gather.c
> > > > index 99740e1..469492d 1006
On Thu, May 16, 2019 at 9:51 AM Hsin-Yi Wang wrote:
>
> On Thu, May 16, 2019 at 10:37 PM Rob Herring wrote:
>
> >
> > Why not just map the FDT R/W at the start and change it to RO just
> > before calling unflatten_device_tree? Then all the FDT scanning
> > functions or any future fixups we need c
On 16.05.19 08:25, Sironi, Filippo wrote:
>> On 16. May 2019, at 15:56, Graf, Alexander wrote:
>>
>> On 14.05.19 08:16, Filippo Sironi wrote:
>>> On x86, we report the UUID in DMI System Information (i.e., DMI Type 1)
>>> as VM UUID.
>>>
>>> Signed-off-by: Filippo Sironi
>>> ---
>>> arch/x86/ke
On Wed, May 15, 2019 at 11:43 PM Olof Johansson wrote:
>
> SoC updates, mostly refactorings and cleanups of old legacy platforms.
> Major themes this release:
Hmm. This brings in a new warning:
drivers/clocksource/timer-ixp4xx.c:78:20: warning:
‘ixp4xx_read_sched_clock’ defined but not used [-
During probe, return the "get_irq" error value instead of -EINVAL which
allows the driver to be deferred probed if needed.
Fix also the case where of_irq_get() returns a negative value.
Note :
On failure of_irq_get() returns 0 or a negative value while
platform_get_irq() returns a negative value.
On Thu, May 16, 2019 at 05:22:53PM +0200, Oleg Nesterov wrote:
> On 05/17, Aleksa Sarai wrote:
> >
> > On 2019-05-16, Oleg Nesterov wrote:
> > > On 05/17, Aleksa Sarai wrote:
> > > > On 2019-05-16, Oleg Nesterov wrote:
> > > > > On 05/16, Christian Brauner wrote:
> > > > > > With the introduction
401 - 500 of 888 matches
Mail list logo
