On Thu, Feb 15, 2018 at 06:24:16PM -0800, Matthias Kaehlcke wrote:
> On some systems a delay is needed after switching on the clocks, to allow
> the output to stabilize and avoid a popping noise at the beginning of
> the recording. Add the optional device tree property 'wakeup-delay-ms'
This doesn
On Fri, Feb 16, 2018 at 12:21:15PM +0100, Hans de Goede wrote:
> Hi,
>
> On 16-02-18 12:00, Andy Shevchenko wrote:
> > On Fri, Feb 16, 2018 at 12:47 PM, Hans de Goede wrote:
> > > From: Heikki Krogerus
> > >
> > > Several frameworks - clk, gpio, phy, pmw, etc. - maintain
> > > lookup tables for
From: Borislav Petkov
Add a callback which the microcode loader calls after microcode has been
upgraded late to let the user know that any CPUID changes potentially
won't take effect.
One possible example for this is that late loading happens after
alternatives have run and thus patching which r
From: Borislav Petkov
With some microcode upgrades, new CPUID features can become visible on
the CPU. Check what the kernel has mirrored now and issue a warning
hinting at possible things the user/admin can do to make use of the
newly visible features.
Originally-by: Ashok Raj
Signed-off-by: Bo
From: Borislav Petkov
... so that callers can know when microcode was updated and act
accordingly.
Signed-off-by: Borislav Petkov
---
arch/x86/include/asm/microcode.h | 9 +++--
arch/x86/kernel/cpu/microcode/amd.c | 10 +-
arch/x86/kernel/cpu/microcode/core.c | 33
From: Borislav Petkov
Add a callback function which the microcode loader calls when microcode
has been updated to a newer revision. Do the callback only when no error
was encountered during loading.
Signed-off-by: Borislav Petkov
---
arch/x86/include/asm/processor.h | 1 +
arch/x86/kernel
There are many segments of ARM32 uprobes code that is very specific to 32-bit
ARM arch and many differences between the two architectures that could be made
portable (e.g. register numbers). Exclude the ARM32 specific code from ARM64
compilation process and make adjustments in ARM32 uprobes code to
A probes_handler_t() handler function prototype differ between ARM32 and ARM64
arch subtrees. Make ARM64 prototype the same as ARM32 prototype and adjust the
ARM64 code to work with the new prototype.
Signed-off-by: Maciej Slodczyk
---
arch/arm64/include/asm/probes.h | 6 +-
arch/a
In uprobes generic code, an arch specific software breakpoint instruction
is statically assigned with a #define statement. It does not allow to examine
the context and set the proper arch on runtime, which is the case of uprobing
either a 32 or 64 bit app on a 64-bit kernel. Introduce get_swbp_insn
Detect what kind of instruction is being probed and depending on the result:
- if an A64 instruction handle it the old way, using existing A64 instructions
probing code,
- if an A32 instruction decode it and handle using the new code, moved from
32 bit arm kernel tree.
Signed-off-by: Maciej Slodcz
Fix checkpatch.pl issues in moved arm uprobes code.
Signed-off-by: Maciej Slodczyk
---
lib/probes/arm/actions-arm.c | 4 ++--
lib/probes/arm/decode-arm.c | 1 +
lib/probes/arm/decode-arm.h | 4 ++--
lib/probes/arm/decode.c | 6 ++
lib/probes/arm/decode.h | 7 +--
5 files chan
Move ARM32 uprobes code from arch/arm/probes/ to a more common location -
lib/probes/arm/. This code will be used by ARM64 code when uprobing 32-bit
applications.
Signed-off-by: Maciej Slodczyk
---
arch/arm/probes/Makefile | 8
arch/arm/probes/kprobes/ac
ARM probe decoding function has similar name in arm32 -
arm_probes_decode_insn(), and arm64 - arm_probe_decode_insn(). Change arm64
probes decoding function name from arm_probe_decode_insn() to
arm64_probes_decode_insn() to minimize the risk of confusion.
Signed-off-by: Maciej Slodczyk
---
arch/
The uprobe feature on ARM64 kernel does not support ARM A32 instruction
probing, making 32 bit apps running on 64 bit kernel unprobeable.
This patchset utilizes ARM32 uprobe code in ARM64 tree with following
modifications:
- moves ARM32 uprobes code form arch/arm to lib/uprobes/arm to be reused
by
Hi Abhishek,
On 2/3/2018 1:28 PM, Abhishek Sahu wrote:
> Following are the major issues in current driver code
>
> 1. The current driver simply assumes the transfer completion
>whenever its gets any non-error interrupts and then simply do the
>polling of available/free bytes in FIFO.
> 2.
On Friday 19 January 2018 08:15 PM, Maxime Ripard wrote:
> On Fri, Jan 19, 2018 at 05:25:41PM +0800, Chen-Yu Tsai wrote:
>> The AXP223 PMIC, like the AXP221, does not generate VBUS change
>> interrupts when N_VBUSEN is used to drive VBUS for the OTG port
>> on the board.
>>
>> This was not notice
Hi,
On 16-02-18 12:00, Andy Shevchenko wrote:
On Fri, Feb 16, 2018 at 12:47 PM, Hans de Goede wrote:
From: Heikki Krogerus
Several frameworks - clk, gpio, phy, pmw, etc. - maintain
lookup tables for describing connections and provide custom
API for handling them. This introduces a single gen
Hi,
On 16-02-18 12:07, Andy Shevchenko wrote:
On Fri, Feb 16, 2018 at 12:47 PM, Hans de Goede wrote:
From: Heikki Krogerus
In order to allow the USB Type-C Class driver take care of
things like muxes and other possible dependencies for the
port drivers, returning ERR_PTR instead of NULL from
On 16 February 2018 at 11:08, Borislav Petkov wrote:
> On Fri, Feb 16, 2018 at 10:58:47AM +, Ard Biesheuvel wrote:
>> By your own reasoning above, that's a no-no as well.
>
> I'm sure we can come up with some emulation - the same way we did the
> BIOS emulation.
>
>> But thanks for your input.
On Friday 19 January 2018 01:43 PM, Kishon Vijay Abraham I wrote:
> Hi,
>
> On Friday 19 January 2018 11:55 AM, Chen-Yu Tsai wrote:
>> Hi Kishon,
>>
>> On Mon, Jan 15, 2018 at 11:06 PM, Hermann Lauer
>> wrote:
>>> On Wed, Jan 03, 2018 at 04:49:44PM +0800, Icenowy Zheng wrote:
Allwinner R40
On Sun, Feb 11, 2018 at 10:07:26PM +0100, Micha?? K??pie?? wrote:
> Use named constants instead of integers in call_fext_func() invocations
> related to backlight power control in order to more clearly convey the
> intent of each call.
>
> Signed-off-by: Micha?? K??pie??
> ---
[cut]
> +/* FUNC in
On Fri, Feb 16, 2018 at 10:58:47AM +, Ard Biesheuvel wrote:
> By your own reasoning above, that's a no-no as well.
I'm sure we can come up with some emulation - the same way we did the
BIOS emulation.
> But thanks for your input. Anyone else got something constructive to
> contribute?
The n
On Fri, Feb 16, 2018 at 12:47 PM, Hans de Goede wrote:
> From: Heikki Krogerus
>
> In order to allow the USB Type-C Class driver take care of
> things like muxes and other possible dependencies for the
> port drivers, returning ERR_PTR instead of NULL from the
> registration functions in case of
Because READ_ONCE() now implies smp_read_barrier_depends(), the
smp_read_barrier_depends() in __ptr_ring_consume() is redundant;
this commit removes it and updates the comments.
Signed-off-by: Andrea Parri
Cc: "David S. Miller"
Cc: "Michael S. Tsirkin"
Cc: Jason Wang
Cc: John Fastabend
Cc: Er
Commit-ID: 98219dda2ab56ce2a967fdebf81e838d676d9ddc
Gitweb: https://git.kernel.org/tip/98219dda2ab56ce2a967fdebf81e838d676d9ddc
Author: Kirill A. Shutemov
AuthorDate: Wed, 14 Feb 2018 21:25:40 +0300
Committer: Ingo Molnar
CommitDate: Fri, 16 Feb 2018 10:48:48 +0100
x86/mm: Fold p4d pag
Commit-ID: 6657fca06e3ffab8d0b3f9d8b397f5ee498952d7
Gitweb: https://git.kernel.org/tip/6657fca06e3ffab8d0b3f9d8b397f5ee498952d7
Author: Kirill A. Shutemov
AuthorDate: Wed, 14 Feb 2018 21:25:42 +0300
Committer: Ingo Molnar
CommitDate: Fri, 16 Feb 2018 10:48:49 +0100
x86/mm: Allow to boo
Commit-ID: 91f606a8fa68264224cbc76888fa8649cdbe9990
Gitweb: https://git.kernel.org/tip/91f606a8fa68264224cbc76888fa8649cdbe9990
Author: Kirill A. Shutemov
AuthorDate: Wed, 14 Feb 2018 21:25:41 +0300
Committer: Ingo Molnar
CommitDate: Fri, 16 Feb 2018 10:48:49 +0100
x86/mm: Replace comp
Hi,
On Friday 10 February 2017 01:14 PM, Chris Zhong wrote:
>
> There are 2 Type-c PHYs in RK3399, but only one DP controller. Hence
> only one PHY can connect to DP controller at one time, the other should
> be disconnected. The GRF_SOC_CON26 register has a switch bit to do it,
> set this bit me
Commit-ID: a7412546d8cb5ad578805060b4006f2a021b5868
Gitweb: https://git.kernel.org/tip/a7412546d8cb5ad578805060b4006f2a021b5868
Author: Kirill A. Shutemov
AuthorDate: Wed, 14 Feb 2018 21:25:37 +0300
Committer: Ingo Molnar
CommitDate: Fri, 16 Feb 2018 10:48:47 +0100
x86/mm: Adjust vmall
Commit-ID: 6f9dd329717f696f578347c0781a0247db957596
Gitweb: https://git.kernel.org/tip/6f9dd329717f696f578347c0781a0247db957596
Author: Kirill A. Shutemov
AuthorDate: Wed, 14 Feb 2018 21:25:39 +0300
Committer: Ingo Molnar
CommitDate: Fri, 16 Feb 2018 10:48:48 +0100
x86/mm: Support boot
Commit-ID: 9b46a051e43461a9afda2bdd50e0e0ae349341df
Gitweb: https://git.kernel.org/tip/9b46a051e43461a9afda2bdd50e0e0ae349341df
Author: Kirill A. Shutemov
AuthorDate: Wed, 14 Feb 2018 21:25:38 +0300
Committer: Ingo Molnar
CommitDate: Fri, 16 Feb 2018 10:48:48 +0100
x86/mm: Initialize v
On 16/02/2018 11:21, David Woodhouse wrote:
> Why? With IBRS_ALL the guest *never* gets to affect the actual hardware
> MSR, which is always on. The MSR is purely an emulated no-op. Why does
> that affect migration?
Because even if the host has IBRS_ALL, as long as you want to migrate to
a system
Commit-ID: 4fa5662b6b49611f11856db8be346710217473ef
Gitweb: https://git.kernel.org/tip/4fa5662b6b49611f11856db8be346710217473ef
Author: Kirill A. Shutemov
AuthorDate: Wed, 14 Feb 2018 21:25:36 +0300
Committer: Ingo Molnar
CommitDate: Fri, 16 Feb 2018 10:48:47 +0100
x86/mm: Initialize '
Commit-ID: 4c2b4058ab32581931c2caf760b689fd4b019a87
Gitweb: https://git.kernel.org/tip/4c2b4058ab32581931c2caf760b689fd4b019a87
Author: Kirill A. Shutemov
AuthorDate: Wed, 14 Feb 2018 21:25:34 +0300
Committer: Ingo Molnar
CommitDate: Fri, 16 Feb 2018 10:48:46 +0100
x86/mm: Initialize '
Commit-ID: b16e770bfa5344f1cd4f7b4ecd7bbae25001e120
Gitweb: https://git.kernel.org/tip/b16e770bfa5344f1cd4f7b4ecd7bbae25001e120
Author: Kirill A. Shutemov
AuthorDate: Wed, 14 Feb 2018 21:25:35 +0300
Committer: Ingo Molnar
CommitDate: Fri, 16 Feb 2018 10:48:47 +0100
x86/mm: Initialize '
Commit-ID: 25d76ac888216c369dea91768764728b83769799
Gitweb: https://git.kernel.org/tip/25d76ac888216c369dea91768764728b83769799
Author: Matthew Whitehead
AuthorDate: Thu, 15 Feb 2018 11:54:56 -0500
Committer: Ingo Molnar
CommitDate: Fri, 16 Feb 2018 10:36:39 +0100
x86/Kconfig: Explicit
On Fri, Feb 16, 2018 at 12:47 PM, Hans de Goede wrote:
> From: Heikki Krogerus
>
> Several frameworks - clk, gpio, phy, pmw, etc. - maintain
> lookup tables for describing connections and provide custom
> API for handling them. This introduces a single generic
> lookup table and API for the conne
Commit-ID: 69b8d3fcabdc81d9efd82b4a506c8279cbaba692
Gitweb: https://git.kernel.org/tip/69b8d3fcabdc81d9efd82b4a506c8279cbaba692
Author: Matthew Whitehead
AuthorDate: Thu, 15 Feb 2018 11:54:55 -0500
Committer: Ingo Molnar
CommitDate: Fri, 16 Feb 2018 10:36:39 +0100
x86/Kconfig: Exclude
Commit-ID: f960cfd12650fad43c1cde07a1f7642cf2c57f97
Gitweb: https://git.kernel.org/tip/f960cfd12650fad43c1cde07a1f7642cf2c57f97
Author: Matthew Whitehead
AuthorDate: Thu, 15 Feb 2018 11:54:54 -0500
Committer: Ingo Molnar
CommitDate: Fri, 16 Feb 2018 10:36:39 +0100
x86/Kconfig: Add miss
On 16 February 2018 at 10:55, Borislav Petkov wrote:
> On Fri, Feb 16, 2018 at 10:41:45AM +, Ard Biesheuvel wrote:
>> On 15 February 2018 at 18:22, Joe Konno wrote:
>> > From: Joe Konno
>> >
>> > It was pointed out that normal, unprivileged users reading certain EFI
>> > variables (through e
On Sun, Feb 11, 2018 at 10:07:20PM +0100, Micha?? K??pie?? wrote:
> The patch series contains miscellaneous cleanups which I think are worth
> getting done before splitting fujitsu-laptop into two separate modules.
> I am not 100% sure that all the changes in the last patch in this series
> actuall
On Fri, Feb 16, 2018 at 10:41:45AM +, Ard Biesheuvel wrote:
> On 15 February 2018 at 18:22, Joe Konno wrote:
> > From: Joe Konno
> >
> > It was pointed out that normal, unprivileged users reading certain EFI
> > variables (through efivarfs) can generate SMIs. Given these nodes are
> > create
On Fri, Feb 16, 2018 at 11:39 AM, Andy Shevchenko
wrote:
> On Fri, Feb 16, 2018 at 11:14 AM, Rafael J. Wysocki wrote:
>> On Wed, Feb 14, 2018 at 12:23 PM, Andy Shevchenko
>> wrote:
>>> On Fri, Feb 9, 2018 at 6:14 PM, Tony Lindgren wrote:
This makes it easy to grep :wakeup /proc/interrupts.
Commit-ID: d207af2eab3f8668b95ad02b21930481c42806fd
Gitweb: https://git.kernel.org/tip/d207af2eab3f8668b95ad02b21930481c42806fd
Author: Michael Kelley
AuthorDate: Wed, 14 Feb 2018 02:54:03 +
Committer: Ingo Molnar
CommitDate: Fri, 16 Feb 2018 10:40:24 +0100
cpumask: Make for_each_c
Commit-ID: b753a2b79a5bbad35dfaf8d3dba964727c30654a
Gitweb: https://git.kernel.org/tip/b753a2b79a5bbad35dfaf8d3dba964727c30654a
Author: Dou Liyang
AuthorDate: Wed, 14 Feb 2018 14:25:54 +0800
Committer: Ingo Molnar
CommitDate: Fri, 16 Feb 2018 10:39:11 +0100
x86/apic: Make setup_local_A
From: Heikki Krogerus
In order to allow the USB Type-C Class driver take care of
things like muxes and other possible dependencies for the
port drivers, returning ERR_PTR instead of NULL from the
registration functions in case of failure.
The reason for taking over control of the muxes for examp
Hi All,
Some devices with an USB Type-C connector have a bunch of muxes
behind that connector which need to be controlled by the kernel (rather
then having them controlled by firmware as on most devices).
Quite a while back I submitted a patch-series to tie together these muxes
and the Type-C Por
From: Heikki Krogerus
USB role switch is a device that can be used to choose the
data role for USB connector. With dual-role capable USB
controllers, the controller itself will be the switch, but
on some platforms the USB host and device controllers are
separate IPs and there is a mux between the
From: Heikki Krogerus
USB Type-C connectors consist of various muxes and switches
that route the pins on the connector to the right locations.
The USB Type-C drivers need to be able to control the muxes,
as they are the ones that know things like the cable plug
orientation, and the current mode t
Remove the unused (not implemented anywhere) tcpc_mux_dev abstraction
and replace it with calling the new typec_set_orientation,
usb_role_switch_set and typec_set_mode functions.
Signed-off-by: Hans de Goede
---
drivers/usb/typec/Kconfig | 1 +
drivers/usb/typec/fusb302/fusb302.c | 1
The xHCI controller on various Intel SoCs has an extended cap mmio-range
which contains registers to control the muxing to the xHCI (host mode)
or the dwc3 (device mode) and vbus-detection for the otg usb-phy.
Having a role-sw driver included in the xhci code (under drivers/usb/host)
is not desira
Setting the mux to MUX_NONE and the switch to USB_SWITCH_DISCONNECT when
the data-role is device is not correct. Plenty of devices support
operating as USB device through a (separate) USB device controller.
We really need 2 different versions of USB_SWITCH_CONNECT,
USB_SWITCH_CONNECT_HOST and USB_
Hi Greentime,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v4.16-rc1 next-20180216]
[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
Add a driver for the Pericom PI3USB30532 Type-C cross switch /
mux chip found on some devices with a Type-C port.
Signed-off-by: Hans de Goede
---
Note this is a rewrite of my previous driver which was using the
drivers/mux framework to use the new drivers/usb/typec/mux framework
---
MAINTAINERS
> > Yes.
>
> Would it make sense for virtio-gpu to map buffers to the guest via PCI BARs?
> So we can use a single drm driver for both 2d and 3d.
Should be doable.
I'm wondering two things though:
(1) Will shmem actually help avoiding a copy?
virtio-gpu with virgl will (even if the guest doesn
The AXP288 BC1.2 charger detection / extcon code may seem like a strange
place to add code to control the USB role-switch on devices with an AXP288,
but there are 2 reasons to do this inside the axp288 extcon code:
1) On many devices the USB role is controlled by ACPI AML code, but the AML
code
Various Intel SoCs (Cherry Trail, Broxton and others) have an internal USB
role switch for swiching the OTG USB data lines between the xHCI host
controller and the dwc3 gadget controller.
Note on some Cherry Trail systems there is ACPI/AML code listening to
edge interrupts on the id-pin (through a
We need to add device-connections for the TYPE-C mux/switch and usb-role
code to be able to find the PI3USB30532 Type-C cross-switch and the
device/host switch integrated in the CHT SoC.
Signed-off-by: Hans de Goede
---
drivers/platform/x86/intel_cht_int33fe.c | 25 +
1 f
From: Mathias Nyman
Modify xhci_find_next_ext_cap(base, offset, id) to return the next
capability offset if 0 is passed for id. Otherwise it will behave as
previously and return the offset of the next capability with matching id
capability id 0 is not used by xhci (reserved)
This is useful when
From: Heikki Krogerus
Several frameworks - clk, gpio, phy, pmw, etc. - maintain
lookup tables for describing connections and provide custom
API for handling them. This introduces a single generic
lookup table and API for the connections.
The motivation for this commit is centralizing the
connect
From: Heikki Krogerus
Several frameworks - clk, gpio, phy, pmw, etc. - maintain
lookup tables for describing connections and provide custom
API for handling them. This introduces a single generic
lookup table and API for the connections.
The motivation for this commit is centralizing the
connect
Hi All,
Some devices with an USB Type-C connector have a bunch of muxes
behind that connector which need to be controlled by the kernel (rather
then having them controlled by firmware as on most devices).
Quite a while back I submitted a patch-series to tie together these muxes
and the Type-C Por
Setting the mux to MUX_NONE and the switch to USB_SWITCH_DISCONNECT when
the data-role is device is not correct. Plenty of devices support
operating as USB device through a (separate) USB device controller.
We really need 2 different versions of USB_SWITCH_CONNECT,
USB_SWITCH_CONNECT_HOST and USB_
From: Heikki Krogerus
USB role switch is a device that can be used to choose the
data role for USB connector. With dual-role capable USB
controllers, the controller itself will be the switch, but
on some platforms the USB host and device controllers are
separate IPs and there is a mux between the
From: Heikki Krogerus
In order to allow the USB Type-C Class driver take care of
things like muxes and other possible dependencies for the
port drivers, returning ERR_PTR instead of NULL from the
registration functions in case of failure.
The reason for taking over control of the muxes for examp
From: Mathias Nyman
Modify xhci_find_next_ext_cap(base, offset, id) to return the next
capability offset if 0 is passed for id. Otherwise it will behave as
previously and return the offset of the next capability with matching id
capability id 0 is not used by xhci (reserved)
This is useful when
Remove the unused (not implemented anywhere) tcpc_mux_dev abstraction
and replace it with calling the new typec_set_orientation,
usb_role_switch_set and typec_set_mode functions.
Signed-off-by: Hans de Goede
---
drivers/usb/typec/Kconfig | 1 +
drivers/usb/typec/fusb302/fusb302.c | 1
Free Electrons is now Bootlin.
Signed-off-by: Boris Brezillon
---
Note that I'm planning to take this patch through the MTD tree.
---
.mailmap| 7 ---
MAINTAINERS | 10 +-
2 files changed, 9 insertions(+), 8 deletions(-)
diff --git a/.mailmap b/.mailmap
index e18cab73e209..50c1
Hi All.
Ugh, I had my .git/config still setup for sending AHCI patches, so
sorry, please ignore this series while I resend it to the right
people.
Regards,
Hans
On 16-02-18 11:43, Hans de Goede wrote:
Hi All,
Some devices with an USB Type-C connector have a bunch of muxes
behind that connec
From: Heikki Krogerus
USB Type-C connectors consist of various muxes and switches
that route the pins on the connector to the right locations.
The USB Type-C drivers need to be able to control the muxes,
as they are the ones that know things like the cable plug
orientation, and the current mode t
Add a driver for the Pericom PI3USB30532 Type-C cross switch /
mux chip found on some devices with a Type-C port.
Signed-off-by: Hans de Goede
---
Note this is a rewrite of my previous driver which was using the
drivers/mux framework to use the new drivers/usb/typec/mux framework
---
MAINTAINERS
We need to add device-connections for the TYPE-C mux/switch and usb-role
code to be able to find the PI3USB30532 Type-C cross-switch and the
device/host switch integrated in the CHT SoC.
Signed-off-by: Hans de Goede
---
drivers/platform/x86/intel_cht_int33fe.c | 25 +
1 f
From: Markus Elfring
Date: Fri, 16 Feb 2018 11:34:53 +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/ata/pata_mpc52xx.c | 1 -
1 file changed, 1 deletion(-)
diff
The xHCI controller on various Intel SoCs has an extended cap mmio-range
which contains registers to control the muxing to the xHCI (host mode)
or the dwc3 (device mode) and vbus-detection for the otg usb-phy.
Having a role-sw driver included in the xhci code (under drivers/usb/host)
is not desira
Various Intel SoCs (Cherry Trail, Broxton and others) have an internal USB
role switch for swiching the OTG USB data lines between the xHCI host
controller and the dwc3 gadget controller.
Note on some Cherry Trail systems there is ACPI/AML code listening to
edge interrupts on the id-pin (through a
The AXP288 BC1.2 charger detection / extcon code may seem like a strange
place to add code to control the USB role-switch on devices with an AXP288,
but there are 2 reasons to do this inside the axp288 extcon code:
1) On many devices the USB role is controlled by ACPI AML code, but the AML
code
On 15 February 2018 at 18:22, Joe Konno wrote:
> From: Joe Konno
>
> It was pointed out that normal, unprivileged users reading certain EFI
> variables (through efivarfs) can generate SMIs. Given these nodes are created
> with 0644 permissions, normal users could generate a lot of SMIs. By
> rest
On Fri, Feb 16, 2018 at 11:14 AM, Rafael J. Wysocki wrote:
> On Wed, Feb 14, 2018 at 12:23 PM, Andy Shevchenko
> wrote:
>> On Fri, Feb 9, 2018 at 6:14 PM, Tony Lindgren wrote:
>>> This makes it easy to grep :wakeup /proc/interrupts.
>>
>> I used to have another patch (not published) to provide t
On Fri, Feb 16, 2018 at 10:57 AM, Rodrigo Rivas Costa
wrote:
> On Fri, Feb 16, 2018 at 10:31:35AM +0100, Benjamin Tissoires wrote:
>> > Ok, I'll do that. The weird thing, however, is that:
>> >
>> > hid_hw_raw_request(steam->hid_dev, 0x00,
>> > buf, hid_report_len(r), /* 64
On Thu, Feb 15, 2018 at 06:20:49PM +, Will Deacon wrote:
> > The only other comment is that I think it would be better if you use
> > atomic_t instead of atomic_long_t. It would just mean changing
> > BIT_WORD() and BIT_MASK().
>
> It would make it pretty messy for big-endian architectures, I
On Fri, Feb 16, 2018 at 11:31:34AM +0530, Naresh Kamboju wrote:
> On 15 February 2018 at 20:45, Greg Kroah-Hartman
> wrote:
> > This is the start of the stable review cycle for the 4.15.4 release.
> > There are 202 patches in this series, all will be posted as a response
> > to this one. If anyon
Hi,
On 15-02-18 20:00, Kai-Heng Feng wrote:
After Laptop Mode Tools starts to use min_power for LPM, a user found
out Crucial BX100 SSD can't get mounted.
Crucial BX100 SSD drives don't work well with min_power. This also
happens to med_power_with_dipm.
So let's disable LPM for Crucial BX100 S
On Thu, Feb 15, 2018 at 02:59:50PM -0700, Shuah Khan wrote:
> On 02/15/2018 08:15 AM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.15.4 release.
> > There are 202 patches in this series, all will be posted as a response
> > to this one. If anyone has any iss
On Fri 16-02-18 15:14:40, t.vi...@samsung.com wrote:
> From: Vivek Trivedi
>
> If fanotify userspace response server thread is frozen first,
> it may fail to send response from userspace to kernel space listener.
> In this scenario, fanotify response listener will never get response
> from userep
On 16/02/2018 at 11:03, Alexandre Belloni wrote:
Free Electrons is now Bootlin.
Signed-off-by: Alexandre Belloni
Acked-by: Nicolas Ferre
Sure! Welcome Bootlin!
Regards,
Nicolas
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAIN
Hi Ingo, Eric,
On 02/16/18 at 10:38am, Ingo Molnar wrote:
>
> * Baoquan He wrote:
>
> > This is v5 post. Newly added patch 0002 includes the change
> > related to KEXEC_JUMP path. Patch 0003 only includes the
> > regression fix.
> >
> > A regression bug was introduced in below commit.
> > comm
On Fri, 2018-02-16 at 11:08 +0100, Paolo Bonzini wrote:
> On 16/02/2018 10:58, David Woodhouse wrote:
> >
> > On Tue, 2018-02-13 at 11:41 +0100, Paolo Bonzini wrote:
> >
> > >
> > > On 13/02/2018 11:36, David Woodhouse wrote:
> > > >
> > > > >
> > > > > >
> > > > > > - if the VM has IBRS_AL
On Thu, Feb 15, 2018 at 06:20:49PM +, Will Deacon wrote:
> On Thu, Feb 15, 2018 at 06:08:47PM +0100, Peter Zijlstra wrote:
> > On Thu, Feb 15, 2018 at 03:29:33PM +, Will Deacon wrote:
> > > +static inline void __clear_bit_unlock(unsigned int nr,
> > > + volatil
Hi Stephen,
On Fri, Feb 16, 2018 at 07:28:39AM +1100, Stephen Rothwell wrote:
> Hi all,
>
> I noticed commit
>
> 0a815fc929e6 ("MAINTAINERS: update email address for Maxime Ripard")
>
> Should I change the contact address I have for Maxime as well?
Yes, definitely. Sorry for forgetting to te
On Wed, Feb 14, 2018 at 02:03:29PM +0200, Tomas Winkler wrote:
> This fixes regression introduced by
> commit 8d52af6795c0 ("mei: speed up the power down flow")
In the future, put:
Fixes: 8d52af6795c0 ("mei: speed up the power down flow")
in your signed-off-by area so that we can track th
On 16/02/2018 10:58, David Woodhouse wrote:
> On Tue, 2018-02-13 at 11:41 +0100, Paolo Bonzini wrote:
>
>> On 13/02/2018 11:36, David Woodhouse wrote:
> - if the VM has IBRS_ALL, pass through the MSR when it is zero and
> intercept writes when it is one (no writes should happen)
>
>>
From: Markus Elfring
Date: Fri, 16 Feb 2018 10:55:51 +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/ata/pata_samsung_cf.c | 4 +---
1 file changed, 1 insertion(+)
Free Electrons is now Bootlin.
Signed-off-by: Alexandre Belloni
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 99038a885ba6..afeca452ba6d 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -11693,7 +11693,7 @@ X: kernel/torture
Hi Todor,
thanks for the patch.
Is the datsheet for this sensor public? I failed to find any reference
to it online, am I wrong?
On Thu, Feb 08, 2018 at 10:53:38AM +0200, Todor Tomov wrote:
> The ov7251 sensor is a 1/7.5-Inch B&W VGA (640x480) CMOS Digital Image
> Sensor from Omnivision.
>
>
Free Electrons is now Bootlin.
Signed-off-by: Alexandre Belloni
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 3bdc260e36b7..99038a885ba6 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -1238,7 +1238,7 @@ F:drivers/clk/at
On Tue, 2018-02-13 at 11:41 +0100, Paolo Bonzini wrote:
> On 13/02/2018 11:36, David Woodhouse wrote:
> > > > - if the VM has IBRS_ALL, pass through the MSR when it is zero and
> > > > intercept writes when it is one (no writes should happen)
> > > >
> > > > - if the VM doesn't have IBRS_ALL, do
Commit-ID: a66b86f0026b07b0ea7340e3690ac9fd5ac1499a
Gitweb: https://git.kernel.org/tip/a66b86f0026b07b0ea7340e3690ac9fd5ac1499a
Author: Andy Shevchenko
AuthorDate: Wed, 14 Feb 2018 17:43:17 +0200
Committer: Ingo Molnar
CommitDate: Fri, 16 Feb 2018 10:10:14 +0100
x86/platform/quark: Re-
Commit-ID: 3130451e270960065e8de684c60b898e970c940c
Gitweb: https://git.kernel.org/tip/3130451e270960065e8de684c60b898e970c940c
Author: Andy Shevchenko
AuthorDate: Wed, 14 Feb 2018 17:43:16 +0200
Committer: Ingo Molnar
CommitDate: Fri, 16 Feb 2018 10:10:14 +0100
x86/platform/atom: Re-u
On Fri, Feb 16, 2018 at 10:31:35AM +0100, Benjamin Tissoires wrote:
> > Ok, I'll do that. The weird thing, however, is that:
> >
> > hid_hw_raw_request(steam->hid_dev, 0x00,
> > buf, hid_report_len(r), /* 64 */
> > HID_FEATURE_REPORT, HID_REQ_GET_REPORT);
> >
On 02/16/2018 10:16 AM, Kamil Konieczny wrote:
>
> On 15.02.2018 19:32, Marek Vasut wrote:
>> On 02/15/2018 07:06 PM, Kamil Konieczny wrote:
>>>
>>>
>>> On 15.02.2018 18:06, Marek Vasut wrote:
On 02/15/2018 06:00 PM, Kamil Konieczny wrote:
>
>
> On 15.02.2018 17:27, Marek Vasut wr
701 - 800 of 889 matches
Mail list logo