On Mon, Apr 15, 2019 at 2:26 PM Jonathan Kowalski wrote:
>
> On Mon, Apr 15, 2019 at 9:34 PM Andy Lutomirski wrote:
> > I would personally *love* it if distros started setting no_new_privs
> > for basically all processes. And pidfd actually gets us part of the
> > way toward a straightforward wa
On Mon, Apr 15, 2019 at 04:20:17PM -0700, Khazhismel Kumykov wrote:
> I was able to reproduce this by setting security.capability xattr on a
> blockdev file, then writing to it - when writing to the blockdev we
> never lock the inode, so when we clear the capability we hit this
> lockdep warning.
>
The Librem5 devkit is based on the imx8mq from NXP. This is a default
devicetree to boot the board to a command prompt.
Changes since v3:
Freshly sorted and pressed nodes.
Change the backlight to an interpolated scale.
Dropped i2c2.
Dropped devkit version number to match debian MR.
Changes since
Add an entry for Purism, SPC
Signed-off-by: Angus Ainslie (Purism)
---
Documentation/devicetree/bindings/vendor-prefixes.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/vendor-prefixes.txt
b/Documentation/devicetree/bindings/vendor-prefixes.txt
index 40
This is the development kit board for the Librem 5. The current level of
support yields a working console and is able to boot userspace from the
Network or eMMC.
Additional subsystems that are active :
- Both USB ports
- SD card socket
- WiFi usdhc
- WWAN modem
- GNSS
- GPIO keys
- LEDs
- gyro
-
Check whether PTRACE_GET_SYSCALL_INFO semantics implemented in the kernel
matches userspace expectations.
Acked-by: Shuah Khan
Cc: Oleg Nesterov
Cc: Andy Lutomirski
Cc: Elvira Khabirova
Cc: Eugene Syromyatnikov
Cc: linux-kselft...@vger.kernel.org
Signed-off-by: Dmitry V. Levin
---
Notes:
From: Elvira Khabirova
PTRACE_GET_SYSCALL_INFO is a generic ptrace API that lets ptracer obtain
details of the syscall the tracee is blocked in.
There are two reasons for a special syscall-related ptrace request.
Firstly, with the current ptrace API there are cases when ptracer cannot
retrieve
syscall_get_error() is required to be implemented on this
architecture in addition to already implemented syscall_get_nr(),
syscall_get_arguments(), syscall_get_return_value(), and
syscall_get_arch() functions in order to extend the generic
ptrace API with PTRACE_GET_SYSCALL_INFO request.
Cc: Mich
syscall_get_error() is required to be implemented on all
architectures in addition to already implemented syscall_get_nr(),
syscall_get_arguments(), syscall_get_return_value(), and
syscall_get_arch() functions in order to extend the generic
ptrace API with PTRACE_GET_SYSCALL_INFO request.
Acked-by
syscall_get_* functions are required to be implemented on all
architectures in order to extend the generic ptrace API with
PTRACE_GET_SYSCALL_INFO request.
This adds remaining 2 syscall_get_* functions as documented in
asm-generic/syscall.h: syscall_get_error and syscall_get_return_value.
Cc: Ric
All syscall_get_*() and syscall_set_*() functions must be defined
as static inline as on all other architectures, otherwise asm/syscall.h
cannot be included in more than one compilation unit.
This bug has to be fixed in order to extend the generic
ptrace API with PTRACE_GET_SYSCALL_INFO request.
syscall_get_error() is required to be implemented on all
architectures in addition to already implemented syscall_get_nr(),
syscall_get_arguments(), syscall_get_return_value(), and
syscall_get_arch() functions in order to extend the generic
ptrace API with PTRACE_GET_SYSCALL_INFO request.
Acked-by
> From: Peter Zijlstra
> Sent: Monday, April 15, 2019 5:21 AM
> To: Dexuan Cui
>
> On Fri, Apr 12, 2019 at 11:53:57PM +, Dexuan Cui wrote:
> > If smp_call_function_single() is calling the function for itself, it's safe
> > to run with irqs_disabled() == true.
> >
> > I hit the warning becaus
When we boot with the LED support (CONFIG_NEW_LEDS) disabled,
gpio_led_register_device() will return a NULL pointer and we try
to dereference it. Fix by checking also for a NULL pointer.
Fixes: 19a2668a8ae3 ("ARM: OMAP1: ams-delta: Provide GPIO lookup table for LED
device")
Signed-off-by: Aaro Ko
On Mon, 15 Apr 2019 16:52:39 -0600
Raul E Rangel wrote:
> Example:
> sd_ssr: mmc0: au: 8192, erase time: 0, erase offset: 0x0, raw:
> {0x0,0x300,0x1019000,0x1,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0}
>
> Signed-off-by: Raul E Rangel
> ---
>
> drivers/mmc/core/sd.c | 2 +
On Mon, 15 Apr 2019 16:52:38 -0600
Raul E Rangel wrote:
> Example:
> sd_scr: mmc0: version: 2, spec3: 1, width: 5, cmds: 0, raw: {0x2b58000,0x0}
>
> Signed-off-by: Raul E Rangel
> ---
>
> drivers/mmc/core/sd.c | 4
> include/trace/events/mmc.h | 42 +
to clear it at all? Or should we really be locking the inode for
blockdevs after all? I'm not too familiar, but my gut says former
this reproducer is able to immediately crash machine running
linux-next-20190415:
#include
#include
#include
#include
#include
#include
#include
#in
On 4/15/19 10:46 AM, Thomas Gleixner wrote:
> Xose reported warnings when NX is disabled on the kernel command line.
Thank you for doing the dirty work.
>
> __early_set_fixmap() triggers:
>
> attempted to set unsupported pgprot:8163
> bits: 8
Example:
mmc_csd: mmc0: struct: 0, cmdclass: 0x5b5, raw:
{0x400e0032,0x5b59,0x3b4b7f80,0xa404000}
Signed-off-by: Raul E Rangel
---
drivers/mmc/core/mmc.c | 4
drivers/mmc/core/sd.c | 2 ++
include/trace/events/mmc.h | 28
3 files changed, 34 ins
Example:
sd_ssr: mmc0: au: 8192, erase time: 0, erase offset: 0x0, raw:
{0x0,0x300,0x1019000,0x1,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0}
Signed-off-by: Raul E Rangel
---
drivers/mmc/core/sd.c | 2 ++
include/trace/events/mmc.h | 31 +++
2 file
Example:
ocr_request: mmc0: 0x5120 SDHC or SDXC Supported (HCS) | Maximum
Performance (XPC) | Switch to 1.8V (S18R) | 3.3 ~ 3.4
ocr_response: mmc0: 0xff8000 2.7 ~ 2.8 | 2.8 ~ 2.9 | 2.9 ~ 3.0 | 3.0 ~ 3.1 |
3.1 ~ 3.2 | 3.2 ~ 3.3 | 3.3 ~ 3.4 | 3.4 ~ 3.5 | 3.5 ~ 3.6
Signed-off-by: Raul E Rangel
Example:
sd_scr: mmc0: version: 2, spec3: 1, width: 5, cmds: 0, raw: {0x2b58000,0x0}
Signed-off-by: Raul E Rangel
---
drivers/mmc/core/sd.c | 4
include/trace/events/mmc.h | 42 ++
2 files changed, 46 insertions(+)
diff --git a/drivers/mmc/core/sd
Neil Armstrong writes:
> On 01/04/2019 13:51, Neil Armstrong wrote:
>> On 25/03/2019 11:03, Neil Armstrong wrote:
>>> Add following peripherals :
>>> - SAR-ADC
>>> - USB
>>> - Mali GPU
>>>
>>> Dependencies :
>>> - ADC
>>>
>>> Depends on CLKID_AO_SAR_ADC_SEL, stable clk headers tags will be
>>> av
On 4/15/19 2:59 PM, Halil Pasic wrote:
On Mon, 15 Apr 2019 12:51:23 -0400
Tony Krowiak wrote:
Having said that, I understand your concern about a driver hogging
resources. I think I can provide a solution that serves both the
purpose of preventing problems associated with accidental removal
of
On 4/15/19 5:34 PM, Takashi Iwai wrote:
> On Mon, 15 Apr 2019 21:35:17 +0200,
> Gustavo A. R. Silva wrote:
>>
>> Hi all,
>>
>> Friendly ping:
>>
>> Who can take this?
>
> All platforms that support ISA boards are so old and they don't suffer
> from Spectre at all.
>
Oh okay.
I'll take this
On 4/4/19 4:25 PM, Natarajan, Janakarajan wrote:
> CPPC (Collaborative Processor Performance Control) offers optional
> registers which can be used to tune the system based on energy and/or
> performance requirements.
>
> Newer AMD processors add support for a subset of these optional CPPC
> regist
On Mon, 15 Apr 2019 21:35:17 +0200,
Gustavo A. R. Silva wrote:
>
> Hi all,
>
> Friendly ping:
>
> Who can take this?
All platforms that support ISA boards are so old and they don't suffer
from Spectre at all.
thanks,
Takashi
>
> Thanks
> --
> Gustavo
>
> On 3/26/19 1:32 PM, Gustavo A.
On Mon, 15 Apr 2019 17:00:05 -0300
Mauro Carvalho Chehab wrote:
> There are some warnings produced when building trace. Fix them.
>
> Signed-off-by: Mauro Carvalho Chehab
Acked-by: Steven Rostedt (VMware)
Jon,
Care to take this through your tree?
Thanks,
-- Steve
> ---
> Documentation/t
On Mon, Apr 15, 2019 at 01:04:03PM +0200, Sebastian Andrzej Siewior wrote:
> On 2019-04-15 03:56:45 [-0700], Paul E. McKenney wrote:
> > This is new in rcutorture as well. It is complaining that we just got
> > done with a stutter interval (in which torturing temporarily stops)
> > but not everyth
On 4/15/19 3:14 PM, Dave Hansen wrote:
On 4/15/19 3:10 PM, Yang Shi wrote:
Also, I don't see anything in the code tying this to strictly demote
from DRAM to PMEM. Is that the end effect, or is it really implemented
that way and I missed it?
No, not restrict to PMEM. It just tries to demote
On 4/15/19 3:13 PM, Dave Hansen wrote:
On 4/15/19 3:06 PM, Yang Shi wrote:
This seems like an actively bad idea to me.
Why do we need an *active* note to say the node is contended? Why isn't
just getting a failure back from migrate_pages() enough? Have you
observed this in practice?
The f
On Mon, Apr 15, 2019 at 05:08:41PM +, Nicholas Johnson wrote:
> I have split the last patch into the two patches as suggested. One to
> add the new parameter and another to rename them nicely.
>
> There is no longer depreciation of the old kernel parameters - they are
> simply dropped, as su
On 4/15/19 3:10 PM, Yang Shi wrote:
>> Also, I don't see anything in the code tying this to strictly demote
>> from DRAM to PMEM. Is that the end effect, or is it really implemented
>> that way and I missed it?
>
> No, not restrict to PMEM. It just tries to demote from "preferred node"
> (or call
On 4/15/19 3:06 PM, Yang Shi wrote:
>>>
>> This seems like an actively bad idea to me.
>>
>> Why do we need an *active* note to say the node is contended? Why isn't
>> just getting a failure back from migrate_pages() enough? Have you
>> observed this in practice?
>
> The flag will be used to che
Hi,
On Sat, Mar 23, 2019 at 06:28:09PM +0100, Artur Rojek wrote:
> Add a driver for battery present on Ingenic JZ47xx SoCs.
>
> Signed-off-by: Artur Rojek
I just applied the patch, but it results in the following warning:
WARNING: modpost: missing MODULE_LICENSE() in
drivers/power/supply/inge
On 4/11/19 7:31 AM, Dave Hansen wrote:
On 4/10/19 8:56 PM, Yang Shi wrote:
include/linux/gfp.h| 12
include/linux/migrate.h| 1 +
include/trace/events/migrate.h | 3 +-
mm/debug.c | 1 +
mm/internal.h | 13 +
mm/
On 4/15/19 8:27 AM, Sudeep Holla wrote:
Hi Atish,
Thanks again for doing this. Overall changes look good except a couple
of minor nit, see below.
On Wed, Mar 20, 2019 at 04:48:04PM -0700, Atish Patra wrote:
Both RISC-V & ARM64 are using cpu-map device tree to describe
their cpu topology. It's
On Mon, Apr 15, 2019 at 10:07:47PM +0200, Pavel Machek wrote:
On Mon 2019-04-15 20:58:22, Greg Kroah-Hartman wrote:
[ Upstream commit 896c80bef4d3b357814a476663158aaf669d0fb3 ]
x86_64 restores system call MSRs in fix_processor_context(), and
x86_32 restored them along with segment registers. T
On 4/11/19 9:06 AM, Dave Hansen wrote:
On 4/10/19 8:56 PM, Yang Shi wrote:
When demoting to PMEM node, the target node may have memory pressure,
then the memory pressure may cause migrate_pages() fail.
If the failure is caused by memory pressure (i.e. returning -ENOMEM),
tag the node with PG
On Mon, Apr 15, 2019 at 08:44:36PM +0200, Greg Kroah-Hartman wrote:
> From: Will Deacon
>
> commit 045afc24124d80c6998d9c770844c67912083506 upstream.
>
> Rather embarrassingly, our futex() FUTEX_WAKE_OP implementation doesn't
> explicitly set the return value on the non-faulting path and instead
This patch allows reading and writing the input voltage and current
limit through the POWER_SUPPLY_PROP_INPUT_VOLTAGE_LIMIT and
POWER_SUPPLY_PROP_INPUT_CURRENT_LIMIT sysfs properties. This allows
userspace to see current values and to re-configure these values at
runtime based on system-level knowl
This is part of the Pixel C's thermal management strategy to effectively
limit the input power to 5V 3A when the screen is on. When the screen is
on, the display, the CPU, and the GPU all contribute more heat to the
system than while the screen is off, and we made a tradeoff to throttle
the charger
From: Long Li
To support compounding, __smb_send_rqst() now sends an array of requests to
the transport layer.
Change smbd_send() to take an array of requests, and send them in as few
packets as possible.
Signed-off-by: Long Li
---
fs/cifs/smbdirect.c | 55 +++--
On Mon, Apr 15, 2019 at 03:00:31PM -0600, Raul E Rangel wrote:
> The SD Physical Layer Spec says the following: Since the SD Memory Card
> shall support at least the two bus modes 1-bit or 4-bit width, then any SD
> Card shall set at least bits 0 and 2 (SD_BUS_WIDTH="0101").
>
> This change verifi
On Mon, 15 Apr 2019 14:57:04 -0600
Raul E Rangel wrote:
> This is useful to see which EC commands are being executed and when.
>
> To enable:
>
> echo 'cros_ec:*' >> /sys/kernel/debug/tracing/set_event
Note, you can accomplish the same thing with:
echo 1 > /sys/kernel/debug/tracing/even
On Mon, Apr 15, 2019 at 2:35 PM Enric Balletbo i Serra
wrote:
>
> This patch makes use of cros_ec_cmd_xfer_status() instead of
> cros_ec_cmd_xfer() so we can remove some redundant code.
>
> Signed-off-by: Enric Balletbo i Serra
Reviewed-by: Guenter Roeck
> ---
>
> drivers/platform/chrome/cro
Hi all,
Commit
d9a3f2b2a31b ("platform/chrome: cros_ec: Add EC host command support using
rpmsg")
is missing a Signed-off-by from its committer.
--
Cheers,
Stephen Rothwell
pgpxJQwYP2mit.pgp
Description: OpenPGP digital signature
This patch makes use of cros_ec_cmd_xfer_status() instead of
cros_ec_cmd_xfer() so we can remove some redundant code.
Signed-off-by: Enric Balletbo i Serra
---
drivers/platform/chrome/cros_ec_debugfs.c | 30 ++-
1 file changed, 8 insertions(+), 22 deletions(-)
diff --git a/
This patch fixes PIO mode transfer to use PIO bit in SPI_COMMAND1 register.
Current driver uses DMA_EN instead of PIO bit.
Signed-off-by: Sowjanya Komatineni
---
drivers/spi/spi-tegra114.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/spi/spi-tegra114.c b/drive
Tegra SPI master controller supports configuring least significant
first byte order or most significant first byte order for transfers.
This patch adds SPI_LSBYTE_FIRST to supported mode list and also
configures byte order based on the mode request for transfer.
Signed-off-by: Sowjanya Komatineni
Tegra SPI controller supports both HW and SW based CS control
for SPI transfers.
This patch adds support for HW based CS control where CS is driven
to active state during the transfer and is driven inactive at the
end of the transfer directly by the HW.
This patch enables the use of HW based CS o
Tegra SPI master controller has programmable trimmers to adjust the
data with respect to the clock.
These trimmers are programmed in TX_CLK_TAP_DELAY and RX_CLK_TAP_DELAY
fields of COMMAND2 register.
SPI TX trimmer is to adjust the outgoing data with respect to the
outgoing clock and SPI RX trimm
This patch implements set_cs_timing SPI controller method to allow
SPI client driver to configure device specific SPI CS timings.
Signed-off-by: Sowjanya Komatineni
---
drivers/spi/spi-tegra114.c | 48 --
1 file changed, 46 insertions(+), 2 deletions(-
This patch adds support for GPIO based CS control through SPI core
function spi_set_cs.
Signed-off-by: Sowjanya Komatineni
---
drivers/spi/spi-tegra114.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/drivers/spi/spi-tegra114.c b/drivers/spi/spi-tegra114.c
index f4e39eb3857c..0b04eba
This patch exports spi_set_cs of the spi core to allow SPI masters
to use when gpio based chip select is needed.
Signed-off-by: Sowjanya Komatineni
---
drivers/spi/spi.c | 3 ++-
include/linux/spi/spi.h | 1 +
2 files changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/spi/spi.c
[V3] : This patch series version includes
- only patches that are not applied from V2.
- splitted expanding mode and adding LSByte First support
in separate patches and removed DT property for selecting
LSByte First.
- Updated GPIO based chip select contr
This patch changes mode and mode_bits from u16 to u32 to allow more
mode configurations.
Signed-off-by: Sowjanya Komatineni
---
include/linux/spi/spi.h | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/include/linux/spi/spi.h b/include/linux/spi/spi.h
index 589f9dc9ac2b..
Some SPI slaves expect bytes to be in least significant first order
and some expects most significant first oder.
This patch adds support for requesting SPI master controllers for
least significant first order using SPI_LSBYTE_FIRST mode.
Signed-off-by: Sowjanya Komatineni
---
drivers/spi/spi.c
From: Lin Huang
Enable the DMC (Dynamic Memory Controller) and the DFI (DDR PHY
Interface) nodes on gru boards so we can support DDR DVFS.
The patch also introduces a new file with default DRAM settings.
Signed-off-by: Lin Huang
Signed-off-by: Enric Balletbo i Serra
Signed-off-by: Gaël PORTAY
From: Enric Balletbo i Serra
The Rockchip DMC (Dynamic Memory Interface) needs to access to the PMU
general register files to know the DRAM type, so add a phandle to the
syscon that manages these registers.
Signed-off-by: Enric Balletbo i Serra
Reviewed-by: Chanwoo Choi
Acked-by: Rob Herring
From: Enric Balletbo i Serra
Some rk3399 GRF (Generic Register Files) definitions can be used for
different drivers. Move these definitions to a common include so we
don't need to duplicate these definitions.
Signed-off-by: Enric Balletbo i Serra
Acked-by: Chanwoo Choi
Signed-off-by: Gaël PORT
From: Lin Huang
These are required to support DDR DVFS on rk3399 platform.
Signed-off-by: Lin Huang
Signed-off-by: Enric Balletbo i Serra
Signed-off-by: Gaël PORTAY
---
Changes in v4:
- [PATCH v3 4/5] Remove board related DDR settings.
Changes in v3: None
Changes in v2:
- [PATCH 7/8] Rewor
Dear all,
The rk3399 platform has a DFI controller that can monitor DDR load and a
DMC driver that talks with the TF-A (Trusted Firmware-A) to dynamically
set the DDR frequency with following flow.
kernel Trusted Firmware-A
From: Enric Balletbo i Serra
Trusted Firmware-A (TF-A) for rk3399 implements a SiP call to get the
on-die termination (ODT) and auto power down parameters from kernel,
this patch adds the functionality to do this. Also, if DDR clock
frequency is lower than the on-die termination (ODT) disable fre
On Mon, Apr 15, 2019 at 9:34 PM Andy Lutomirski wrote:
>
> On Mon, Apr 15, 2019 at 12:59 PM Aleksa Sarai wrote:
> >
> > On 2019-04-15, Enrico Weigelt, metux IT consult wrote:
> > > > This patchset makes it possible to retrieve pid file descriptors at
> > > > process creation time by introducing
Hi Herbert,
In commit
2e53582d158e ("crypto: mxc-scc - Remove broken driver")
Fixes tag
Fixes: d293b640ebd ("crypto: mxc-scc - add basic driver for the...")
has these problem(s):
- SHA1 should be at least 12 digits long
Can be fixed by setting core.abbrev to 12 (or more) or (for git
From: Mian Yousaf Kaukab
spectre v1, has been mitigated, and the mitigation is
always active.
Signed-off-by: Mian Yousaf Kaukab
Signed-off-by: Jeremy Linton
Reviewed-by: Andre Przywara
Reviewed-by: Catalin Marinas
Tested-by: Stefan Wahren
Acked-by: Suzuki K Poulose
---
arch/arm64/kernel/c
Display the system vulnerability status. This means that
while its possible to have the mitigation enabled, the
sysfs entry won't indicate that status. This is because
the core ABI doesn't express the concept of mitigation
when the system isn't vulnerable.
Signed-off-by: Jeremy Linton
Reviewed-by
From: Marc Zyngier
The SMCCC ARCH_WORKAROUND_1 service can indicate that although the
firmware knows about the Spectre-v2 mitigation, this particular
CPU is not vulnerable, and it is thus not necessary to call
the firmware on this CPU.
Let's use this information to our benefit.
Signed-off-by: M
The ssb detection logic is necessary regardless of whether
the vulnerability mitigation code is built into the kernel.
Break it out so that the CONFIG option only controls the
mitigation logic and not the vulnerability detection.
Signed-off-by: Jeremy Linton
Reviewed-by: Andre Przywara
Reviewed-
On Mon, 15 Apr 2019, Andy Lutomirski wrote:
> On Mon, Apr 15, 2019 at 9:17 AM Josh Poimboeuf wrote:
> > On Mon, Apr 15, 2019 at 06:07:44PM +0200, Thomas Gleixner wrote:
> > > > Looks like stack_trace.nr_entries isn't initialized? (though this code
> > > > gets eventually replaced by a later patch
Add code to track whether all the cores in the machine are
vulnerable, and whether all the vulnerable cores have been
mitigated.
Once we have that information we can add the sysfs stub and
provide an accurate view of what is known about the machine.
Signed-off-by: Jeremy Linton
Reviewed-by: Andr
The sysfs patches need to display machine vulnerability
status regardless of kernel config. Prepare for that
by breaking out the vulnerability/mitigation detection
code from the logic which implements the mitigation.
Signed-off-by: Jeremy Linton
Reviewed-by: Andre Przywara
Reviewed-by: Catalin M
From: Marc Zyngier
We currently have a list of CPUs affected by Spectre-v2, for which
we check that the firmware implements ARCH_WORKAROUND_1. It turns
out that not all firmwares do implement the required mitigation,
and that we fail to let the user know about it.
Instead, let's slightly revamp
Return status based on ssbd_state and __ssb_safe. If the
mitigation is disabled, or the firmware isn't responding then
return the expected machine state based on a whitelist of known
good cores.
Given a heterogeneous machine, the overall machine vulnerability
defaults to safe but is reset to unsaf
From: Mian Yousaf Kaukab
Enable CPU vulnerabilty show functions for spectre_v1, spectre_v2,
meltdown and store-bypass.
Signed-off-by: Mian Yousaf Kaukab
Signed-off-by: Jeremy Linton
Reviewed-by: Andre Przywara
Reviewed-by: Catalin Marinas
Tested-by: Stefan Wahren
---
arch/arm64/Kconfig | 1
Arm64 machines should be displaying a human readable
vulnerability status to speculative execution attacks in
/sys/devices/system/cpu/vulnerabilities
This series enables that behavior by providing the expected
functions. Those functions expose the cpu errata and feature
states, as well as whether
On Mon, 15 Apr 2019, Josh Poimboeuf wrote:
> On Mon, Apr 15, 2019 at 06:07:44PM +0200, Thomas Gleixner wrote:
> > >
> > > Looks like stack_trace.nr_entries isn't initialized? (though this code
> > > gets eventually replaced by a later patch)
> >
> > struct initializer initialized the non mention
When remounting with debug_want_extra_isize, we were not performing the
same checks that we do during a normal mount. That allowed us to set a
value for s_want_extra_isize that reached outside the s_inode_size.
Reported-by: syzbot+f584efa0ac7213c22...@syzkaller.appspotmail.com
Signed-off-by: Barr
On Thu, Apr 11, 2019 at 10:06 PM Wu Hao wrote:
>
> On Thu, Apr 11, 2019 at 03:07:35PM -0500, Alan Tull wrote:
> > On Sun, Mar 24, 2019 at 10:24 PM Wu Hao wrote:
> >
> > Hi Hao,
> >
> > >
> > > This patch adds support for power management private feature under
> > > FPGA Management Engine (FME), s
On 4/15/19 8:31 AM, Sudeep Holla wrote:
On Wed, Mar 20, 2019 at 04:48:05PM -0700, Atish Patra wrote:
Currently, ARM32 and ARM64 uses different data structures to
represent their cpu toplogies. Since, we are moving the ARM64
topology to common code to be used by other architectures, we
can reuse
On Mon, Apr 15 2019 at 06:42 -0600, Marc Zyngier wrote:
On 04/04/2019 16:58, Lina Iyer wrote:
On Mon, Mar 18 2019 at 11:54 -0600, Marc Zyngier wrote:
On Wed, 13 Mar 2019 15:18:37 -0600
Lina Iyer wrote:
Please do Cc Rob when posting DT related patches.
Some interrupt controllers in a SoC, ar
Some user spaces (e.g. some Android devices) use /dev/input/event* for handling
the 3D position of the device with respect to the center of gravity (earth).
This can be used for gaming input, auto-rotation of screens etc.
This interface should be the standard for such use cases because it is an
a
The SD Physical Layer Spec says the following: Since the SD Memory Card
shall support at least the two bus modes 1-bit or 4-bit width, then any SD
Card shall set at least bits 0 and 2 (SD_BUS_WIDTH="0101").
This change verifies the card has specified a bus width.
verified it didn't mount.
Signed
On Mon, Apr 15, 2019 at 10:54 PM Guenter Roeck wrote:
>
> >
> > config KS8695_WATCHDOG
> > tristate "KS8695 watchdog"
> > - depends on ARCH_KS8695
> > + depends on ARCH_KS8695 || COMPILE_TEST
>
> Is __raw_readl / __raw_writel really available for all architectures /
> platforms ?
This series contain 2 follow-up patches to alleviate the performance
regression found in the page_fault1 test of the will-it-scale benchmark.
This does not recover all the lost performance, but reclaim a sizeable
portion of it.
The regression was found on an Intel system. I have run the test on
an
Reader optimistic spinning is helpful when the reader critical section
is short and there aren't that many readers around. It makes readers
relatively more preferred than writers. When a writer times out spinning
on a reader-owned lock and set the nospinnable bits, there are two main
reasons for th
Bit 1 of sem->owner was previously used to designate an anonymous
owner - reader or anonymous writer. With the reader optimistic spinning
patches, bit 1 is now used to indicate that optimistic spinning should
be disabled. So change RWSEM_ANONYMOUSLY_OWNED to RWSEM_NONSPINNABLE
to clarify its curren
This is useful to see which EC commands are being executed and when.
To enable:
echo 'cros_ec:*' >> /sys/kernel/debug/tracing/set_event
Example:
/* cros_ec_cmd: version: 0, command: EC_CMD_GET_VERSION */
/* cros_ec_cmd: version: 0, command: EC_CMD_GET_PROTOCOL_INFO */
/* cros_ec
On Mon, Apr 15, 2019 at 10:24:13PM +0200, Arnd Bergmann wrote:
> drivers should not rely on machine specific headers but
> get their information from the platform device.
>
> Signed-off-by: Arnd Bergmann
> ---
> arch/arm/mach-ks8695/devices.c | 13 -
> drivers/watchdog/Kconfig
On Mon, 2019-04-15 at 10:09 -0700, Bart Van Assche wrote:
> On Tue, 2019-03-19 at 10:40 -0700, Bart Van Assche wrote:
> > This patch avoids that gcc reports the following warning when building
> > with W=1:
> >
> > kernel/workqueue.c:4250:2: warning: function alloc_workqueue might be a
> > candid
Hello RT Folks!
I'm pleased to announce the 4.14.109-rt58 stable release.
You can get this release via the git tree at:
git://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stable-rt.git
branch: v4.14-rt
Head SHA1: d805ec17820ce0dc625fe3787c782eb0130130f7
Or to build 4.14.109-rt58 dire
On Mon, Apr 8, 2019 at 3:15 PM Li Yang wrote:
>
> On Fri, Apr 5, 2019 at 4:51 AM Ioana Ciornei wrote:
> >
> > This patch adds DPAA2 MC and AIOP console log support.
> >
> > The platform driver probes on the "fsl,dpaa2-console" device tree node
> > which describes the base firmware address needed
On Mon, Apr 15, 2019 at 12:59 PM Aleksa Sarai wrote:
>
> On 2019-04-15, Enrico Weigelt, metux IT consult wrote:
> > > This patchset makes it possible to retrieve pid file descriptors at
> > > process creation time by introducing the new flag CLONE_PIDFD to the
> > > clone() system call as previou
The uart driver is tightly coupled with the platform code, without
real need. The uart registers can be moved into the driver itself
(and the uncompress code), and instead of referring to the IRQ
lines by number, we can generally use port->irq.
Finally, the initialization of the uart_port structur
The TX interrupt is marked as edge triggered, so it will
already be acked by the top-level irq code, and does not
need the ack in the driver.
Removing this avoids a nasty dependency on the regs-irq.h
file that is otherwise reserved for the interrupt controller
driver.
Signed-off-by: Arnd Bergmann
Properly splitting this out into a portable driver is
hard, as the gpio code tightly interacts with the irqchip
code. Give up and move it back to its original location,
but make the headers private in the process.
Signed-off-by: Arnd Bergmann
---
arch/arm/mach-ks8695/Makefile
Remove an unused struct tx_pending_t, as it is never used in
kernel tree.
Signed-off-by: Madhumitha Prabakaran
---
drivers/staging/rtl8723bs/include/ieee80211.h | 7 ---
1 file changed, 7 deletions(-)
diff --git a/drivers/staging/rtl8723bs/include/ieee80211.h
b/drivers/staging/rtl8723bs/in
Remove typedef in struct ieee_param_ex, as the struct that
has elements that can reasonably be directly accessed should
never be a typedef.
Signed-off-by: Madhumitha Prabakaran
---
drivers/staging/rtl8723bs/include/ieee80211.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
Remove typedef in struct ieee_param, as the struct that
has elements that can reasonably be directly accessed
should never be a typedef.
Signed-off-by: Madhumitha Prabakaran
---
drivers/staging/rtl8723bs/include/ieee80211.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/
101 - 200 of 1116 matches
Mail list logo
