Amstrad Delta NAND driver now uses GPIO API for data I/O so there is no
need to assign memory I/O resource to the device any longer. Drop it.
Signed-off-by: Janusz Krzysztofik
---
arch/arm/mach-omap1/board-ams-delta.c | 11 ---
1 file changed, 11 deletions(-)
diff --git a/arch/arm/mach
Don't readw()/writew() data directly from/to GPIO port which is under
control of gpio-omap driver, use GPIO consumer API instead.
The driver should now work with any 8-bit bidirectional GPIO port, not
only OMAP.
Signed-off-by: Janusz Krzysztofik
Reviewed-by: Linus Walleij
---
drivers/mtd/nand/
Data port used by the driver is actually an OMAP MPUIO device, already
under control of gpio-omap driver. For that reason we used to not
request the memory region of the port as that would fail because the
region is already busy. Despite that, we are still accessing the port
by just ioremapping i
Finalize implementation of the idea suggested by Artem Bityutskiy and
Tony Lindgren, described in commit b027274d2e3a ("mtd: ams-delta: fix
request_mem_region() failure"). Use pure GPIO consumer API, as reqested
by Boris Brezillon.
Janusz Krzysztofik (4):
ARM: OMAP1: ams-delta: Provide GPI
Data port used by Amstrad Delta NAND driver is actually an OMAP MPUIO
device, already under control of gpio-omap driver. The NAND driver
gets access to the port by ioremapping it and performs read/write
operations. That is done without any proteciton from other users
legally manipulating the port
Because the task p is always guaranteed to be non-NULL.
Signed-off-by: Yafang Shao
---
arch/x86/kernel/process.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/kernel/process.c b/arch/x86/kernel/process.c
index c93fcfd..3c3ee89 100644
--- a/arch/x86/kernel/process.c
On Wed, 21 Nov 2018, Geert Uytterhoeven wrote:
> > This suggests that either 0 or N (the latched value) would result from
> > a read from the counter immediately following an interrupt. Who can
> > say which? Just have to try it. The answer should allow us to avoid
> > the risk of a clocksource
Arnd, Olof,
A simple DT fix that is necessary to get reliable access to the NAND on
sama5d2 based boards.
The following changes since commit 651022382c7f8da46cb4872a545ee1da6d097d2a:
Linux 4.20-rc1 (2018-11-04 15:37:52 -0800)
are available in the Git repository at:
git://git.kernel.org/pub
On Wed, Nov 21, 2018 at 08:35:28AM +0800, Yang Shi wrote:
>
>
> On 11/20/18 9:42 PM, Kirill A. Shutemov wrote:
> > On Tue, Nov 20, 2018 at 08:10:51PM +0800, Yang Shi wrote:
> > >
> > > On 11/20/18 4:57 PM, Kirill A. Shutemov wrote:
> > > > On Fri, Nov 16, 2018 at 08:56:04AM -0800, Yang Shi wrote
The GXL Documentation specifies 12 bits for the Fractional bit field,
bit the last bits have a different purpose that we cannot handle right
now, so update the bitwidth to have correct fractional calculations.
Signed-off-by: Neil Armstrong
---
drivers/clk/meson/gxbb.c | 2 +-
1 file changed, 1 i
On Wed, 2018-11-21 at 08:44 +0800, kernel test robot wrote:
> Greeting,
>
> FYI, we noticed a -65.2% regression of will-it-scale.per_thread_ops due to
> commit:
>
>
> commit: 3c19f2312f48a3d36a4e13f5072a6a95e755b3d5 ("fs/locks: always
> delete_block after waiting.")
> https://git.kernel.org/cg
On 21/11/18 12:33 PM, Faiz Abbas wrote:
> The following patches fix tuning related errors in the
> sdhci-omap driver.
>
> v2:
> Added Fixes and stable tags for patch 1.
> Re-enable DCRC in patch 1 only if it was enabled before
> Squashed patches 2 & 3
>
> Faiz Abbas (3):
> mmc: sdhci-omap: Fix
On 20/11/2018 21:20:43+, Peter Rosin wrote:
> The pwm-backlight driver initializes BLON (the enable gpio) to
> output-high if the gpio is input on probe. Initializing the gpio
> to output-low before the driver probes prevents this action by
> the pwm-backlight driver and gets rid of a nasty bli
Hi,
On 20-11-18 16:59, Andy Shevchenko wrote:
Currently i2c-multi-instantiate driver does not support the case
of INT3515 USB PD device, where:
- Interrupt() is used instead of GpioInt()
- All slaves may be the same from IP point of view
- There can be variadic amount of slaves
This series is
From: yuzhoujian
OOM report contains several sections. The first one is the allocation
context that has triggered the OOM. Then we have cpuset context
followed by the stack trace of the OOM path. The tird one is the OOM
memory information. Followed by the current memory state of all system
tasks.
From: yuzhoujian
The current oom report doesn't display victim's memcg context during the
global OOM situation. While this information is not strictly needed, it
can be really helpful for containerized environments to locate which
container has lost a process. Now that we have a single line for t
This patch implements power management callback function for USART as
SPI driver.
Signed-off-by: Radu Pirea
---
drivers/spi/spi-at91-usart.c | 61
1 file changed, 61 insertions(+)
diff --git a/drivers/spi/spi-at91-usart.c b/drivers/spi/spi-at91-usart.c
index
+ Kees.
On Fri, Nov 16, 2018 at 03:17:49AM +0530, Bhupesh Sharma wrote:
> x86_64 kernel uses 'page_offset_base' variable to point to the
> start of direct mapping of all physical memory. This variable
> is also updated for KASLR boot cases, so this can be exported
> via vmcoreinfo as a standard AB
Hi,
This patch series improves the SPI driver for AT91 USART IP and
adds support for DMA transfers, updates the bindings of driver
and PM callback functions.
I decided to use DMA only for transfers long than 16 bytes. DMA
setup introduces a little overhead and is better to use PIO for
short trans
This patch adds support for DMA. Transfers are done with dma only if
they are longer than 16 bytes in order to achieve a better performance.
DMA setup introduces a little overhead and for transfers shorter than 16
bytes there is no performance improvement.
Signed-off-by: Radu Pirea
---
drivers/s
The bindings for DMA are now common for both drivers of the USART
IP.
The node given as an example for USART in SPI mode has been updated in
order to include DMA bindings.
Signed-off-by: Radu Pirea
---
.../devicetree/bindings/mfd/atmel-usart.txt | 15 ++-
1 file changed, 10 in
Hi Ingo,
On Wed, Nov 21, 2018 at 09:02:58AM +0100, Ingo Molnar wrote:
>
> * tip-bot for Mark Rutland wrote:
>
> > Commit-ID: 8d32588077bdc390420cfa6946f407033a20d7a8
> > Gitweb:
> > https://git.kernel.org/tip/8d32588077bdc390420cfa6946f407033a20d7a8
> > Author: Mark Rutland
> > Autho
Hi,
On 20-11-18 16:59, Andy Shevchenko wrote:
i2c_acpi_new_device() doesn't assign fwnode like it's done, for example,
in i2c_acpi_register_devices() path.
Assign fwnode in i2c_acpi_new_device() as it's done elsewhere.
Signed-off-by: Andy Shevchenko
As already mentioned in my reply to the c
Hi Chunyan,
On 12/11/18 12:56 PM, Chunyan Zhang wrote:
> Currently the generic SDHCI code in the Linux kernel supports the SD
> standard DMA integrated into the host controller but does not have any
> support for external DMA controllers implemented using dmaengine meaning
> that custom code is ne
On Thu, Nov 15, 2018 at 10:16:25PM +0200, Jarkko Sakkinen wrote:
> This is how strongly think. I can go with VMAs for swapping *but* if
> that is the route I would recommend using vm_mmap() instead of taking
> pointer from user space. This way the way swapping is done can be always
> changed. It wi
From: Jan Beulich
> Sent: 21 November 2018 10:11
>
> Add missing insn suffixes and use rmwcc.h just like was (more or less)
> recently done for bitops.h as well.
Why? bts (etc) on memory don't really have an 'operand size'.
IIRC the suffix determines the width of the %cx register that selects the
From: Matt Sealey
Most compilers should be able to merge adjacent loads/stores of sizes which
are less than but effect a multiple of a machine word size (in effect a
memcpy() of a constant amount). However the semantics of the macro are that
it just does the copy, the pointer increment is in the
From: Matt Sealey
Enable faster 8-byte copies on arm64.
Signed-off-by: Dave Rodgman
Signed-off-by: Matt Sealey
---
lib/lzo/lzodefs.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/lzo/lzodefs.h b/lib/lzo/lzodefs.h
index d167f8fc6795..341d0f6095ab 100644
--- a/lib/lzo/
From: Matt Sealey
ARMv6 Thumb state introduced an RBIT instruction which, combined with CLZ
as present in ARMv5, introduces an extremely fast path for counting
trailing zeroes.
Enable the use of the GCC builtin for this on ARMv6+ with
CONFIG_THUMB2_KERNEL to ensure we get the 'new' instruction u
When using zram, we frequently encounter long runs of zero bytes.
This adds a special case which identifies runs of zeros and encodes
them using run-length encoding.
This is faster for both compression and decompresion. For
high-entropy data which doesn't hit this case, impact is minimal.
Compres
To prevent any issues with persistent data, separate lzo-rle
from lzo so that it is treated as a separate algorithm, and
lzo is still available.
Use lzo-rle as the default algorithm for
zram.
Signed-off-by: Dave Rodgman
---
Documentation/lzo.txt | 12 ++-
crypto/Makefile
>
> Signed-off-by: Nicholas Mc Guire
>
> Problem located with experimental coccinelle script
>
> Patch was compile tested with: multi_v7_defconfig (implies
> CONFIG_ARCH_ZYNQ=y)
>
> Patch is against 4.20-rc3 (localversion-next is next-20181121)
I have no problem wi
Hi,
On 20-11-18 16:59, Andy Shevchenko wrote:
Instead of relying on hard coded and thus expected number of I2C clients,
count the real amount provided by firmware.
This allows to support non-fixed amount of the slaves.
Signed-off-by: Andy Shevchenko
---
drivers/platform/x86/i2c-multi-instan
Not sure whom to offer the fix, since 'Kernel lockdown for secure boot'
in not upstream, but it has been picked by fedora and ubuntu. And I see
it in next-lockdown branch of
git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git
So, in addition to (prior to) opening bug reports t
With "debugfs: Restrict debugfs when the kernel is locked down"
return code "r" is unconditionally set to -EPERM, which stays like that
until function return if no "open" file operation defined, effectivelly
resulting in "Operation not permitted" for all such files despite kernel
lock down status o
Add imem clock for exynos5433.
Signed-off-by: Kamil Konieczny
---
drivers/clk/samsung/clk-exynos5433.c | 123 +
include/dt-bindings/clock/exynos5433.h | 55 +++
2 files changed, 178 insertions(+)
diff --git a/drivers/clk/samsung/clk-exynos5433.c
b/drivers/clk
From: Matt Sealey
LZO leaves some performance on the table by not realising that AArch64 can
optimize count-trailing-zeros bit operations.
Add __aarch64__ to the checked definitions alongside __x86_64__ to enable
the use of rbit/clz instructions on full 64-bit quantities.
Signed-off-by: Matt Se
Hi,
On 21-11-18 12:27, Hans de Goede wrote:
Hi,
On 20-11-18 16:59, Andy Shevchenko wrote:
Currently i2c-multi-instantiate driver does not support the case
of INT3515 USB PD device, where:
- Interrupt() is used instead of GpioInt()
- All slaves may be the same from IP point of view
- There can
This patch series introduces performance improvements for lzo.
The improvements fall into two categories: general Arm-specific optimisations
(e.g., more efficient memory access); and the introduction of a special case
for handling runs of zeros (which is a common case for zram) using run-length
e
On Wed, 24 Oct 2018, Petr Mladek wrote:
> On Thu 2018-10-18 07:58:24, Josh Poimboeuf wrote:
> > On Thu, Oct 18, 2018 at 01:11:53PM +0200, Petr Mladek wrote:
> > > On Wed 2018-10-17 13:17:56, Josh Poimboeuf wrote:
> > > > On Mon, Oct 15, 2018 at 02:37:03PM +0200, Petr Mladek wrote:
> > > > > The de
On Wed, Nov 21, 2018 at 10:26:30AM +0100, Marek Szyprowski wrote:
> from wm8994_ldo_remove(), switched to regulator_register() in
> wm8994_ldo_probe() and added regulator_unregister() in
> wm8994_ldo_remove(). This way the warning is gone. If there is any
I don't understand why you'd need to swit
Em Thu, Nov 15, 2018 at 04:01:46PM -0500, Liang, Kan escreveu:
>
>
> On 11/15/2018 3:44 PM, Jiri Olsa wrote:
> > On Wed, Nov 14, 2018 at 01:24:15PM -0800, kan.li...@linux.intel.com wrote:
> > > From: Kan Liang
> > >
> > > Perf tools cannot find the proper event list for Cascadelake server.
> >
Hi Mark,
On 2018-11-21 13:19, Mark Brown wrote:
> On Wed, Nov 21, 2018 at 10:26:30AM +0100, Marek Szyprowski wrote:
>
>> from wm8994_ldo_remove(), switched to regulator_register() in
>> wm8994_ldo_probe() and added regulator_unregister() in
>> wm8994_ldo_remove(). This way the warning is gone. If
HI,
On 20-11-18 16:59, Andy Shevchenko wrote:
On some laptops the ACPI device with BOSC0200 _HID is representing
two accelerometers under one node.
We add an ID to the I2C multi instantiate list to enumerate
all I2C slaves correctly.
For reference here is the relevant DSDT blurb from the Yoga
From: Aisheng Dong
If wakeup is enabled, enter stop mode, else enter disabled mode. Self wake
can only work on stop mode.
Starting from IMX6, the flexcan stop mode control bits is SoC specific,
move it out of IP driver and parse it from devicetree.
Signed-off-by: Aisheng Dong
Signed-off-by: Jo
This patch intends to add CAN self wakeup support. The CAN controller can
parse stop mode property from device tree to enable self wakeup feature.
ChangeLog:
V1->V2:
*add a vendor prefix in property (stop-mode -> fsl,stop-mode).
V2->V3:
*add FLEXCAN_QUIRK_SETUP_STOP_MODE quirk.
rsion-next is next-20181121)
drivers/clk/zynq/clkc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/clk/zynq/clkc.c b/drivers/clk/zynq/clkc.c
index d7b53ac..014d4a4 100644
--- a/drivers/clk/zynq/clkc.c
+++ b/drivers/clk/zynq/clkc.c
@@ -440,7 +440,7 @@ stati
The Cygnus architecture use a Kona PWM. This is already present
in the device tree but can't be built actually. Hence, allow the
Kona PWM to be built for Cygnus arch.
Signed-off-by: Clément Péron
---
drivers/pwm/Kconfig | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drive
On Tue, Nov 20, 2018 at 11:03:45PM +0100, Rafael J. Wysocki wrote:
> On Thursday, November 8, 2018 5:51:52 PM CET Heikki Krogerus wrote:
> > Hi,
> >
> > This is the second version of my proposal for this helper. The
> > first version can be checked here:
> > https://lkml.org/lkml/2018/11/5/326
> >
On Tue, Nov 20, 2018 at 10:16 PM shuah wrote:
>
> Hi Rafael,
>
> Please pull the following update for Linux 4.20-rc4 or rc5 depending on
> your pm pull schedule to Linus.
>
> This cpupower update for Linux 4.20-rc4 consists of compile fixes to
> allow use of outside build flags and override of CFL
Quoting Hans Holmberg (2018-11-21 13:35:19)
> On Wed, Nov 21, 2018 at 11:10 AM Joonas Lahtinen
> wrote:
> >
> > Quoting Hans Holmberg (2018-11-21 11:54:23)
> > > From: Hans Holmberg
> > >
> > > There is no need to rebuild i915_gpu_error.o when the version string
> > > changes as the version is av
Hi,
On 2018년 11월 21일 21:05, Kamil Konieczny wrote:
> Add imem clock for exynos5433.
It is diffcult to understand the meaning of 'imem' without the description.
Please add more detailed description as the patch2 description.
>
> Signed-off-by: Kamil Konieczny
> ---
> drivers/clk/samsung/clk-ex
of_find_node_by_path() acquires a reference to the node returned
by it and that reference needs to be dropped by its caller.
bl_idle_init() doesn't do that, so fix it.
Signed-off-by: Yangtao Li
---
drivers/soc/bcm/brcmstb/common.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff -
of_find_node_by_path() acquires a reference to the node
returned by it and that reference needs to be dropped by its caller.
bl_idle_init() doesn't do that, so fix it.
Signed-off-by: Yangtao Li
---
drivers/soc/tegra/common.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a
Em Thu, Nov 15, 2018 at 04:14:42PM +0100, Jiri Olsa escreveu:
> On Thu, Nov 15, 2018 at 08:33:27AM -0500, Liang, Kan wrote:
> >
> >
> > On 11/15/2018 8:21 AM, Jiri Olsa wrote:
> > > On Wed, Nov 14, 2018 at 01:24:16PM -0800, kan.li...@linux.intel.com wrote:
> > > > From: Kan Liang
> > > >
> > >
On 21/11/2018 11:23, Wei Ni wrote:
>
>
> On 21/11/2018 4:55 PM, Daniel Lezcano wrote:
>> On 13/11/2018 11:06, Wei Ni wrote:
>>> Don't bail when a sensor fails to register with the
>>> thermal zone and allow other sensors to register.
>>> This allows other sensors to register with thermal
>>> fram
Em Wed, Nov 21, 2018 at 09:51:30AM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Thu, Nov 15, 2018 at 04:14:42PM +0100, Jiri Olsa escreveu:
> > On Thu, Nov 15, 2018 at 08:33:27AM -0500, Liang, Kan wrote:
> > >
> > >
> > > On 11/15/2018 8:21 AM, Jiri Olsa wrote:
> > > > On Wed, Nov 14, 2018 at 01
On November 21, 2018 1:41:37 PM GMT+01:00, Victoria Anosova
wrote:
>For v4.9 your first fix (
>https://lists.openwall.net/linux-kernel/2016/02/26/299) helped.
Can you please not top-post? Thx.
That old version is not quite right - see the commit message of the current fix.
HTH.
--
Sent from
This mostly looks good to me.
A few minor comments
> -Original Message-
> From: Joakim Zhang
> Sent: Wednesday, November 21, 2018 8:32 PM
> To: linux-...@vger.kernel.org; m...@pengutronix.de
> Cc: w...@grandegger.com; linux-kernel@vger.kernel.org; dl-linux-imx
> ; Aisheng DONG ; Joakim
> Z
> -Original Message-
> From: Aisheng DONG
> Sent: Wednesday, November 21, 2018 9:00 PM
> To: Joakim Zhang ; linux-...@vger.kernel.org;
> m...@pengutronix.de
> Cc: w...@grandegger.com; linux-kernel@vger.kernel.org; dl-linux-imx
>
> Subject: RE: [PATCH V4 1/1] can: flexcan: add self wakeup s
On Wed, Nov 21, 2018 at 09:54:08AM -0300, Arnaldo Carvalho de Melo wrote:
> Em Wed, Nov 21, 2018 at 09:51:30AM -0300, Arnaldo Carvalho de Melo escreveu:
> > Em Thu, Nov 15, 2018 at 04:14:42PM +0100, Jiri Olsa escreveu:
> > > On Thu, Nov 15, 2018 at 08:33:27AM -0500, Liang, Kan wrote:
> > > >
> > >
>>> On 21.11.18 at 12:55, wrote:
> From: Jan Beulich
>> Sent: 21 November 2018 10:11
>>
>> Add missing insn suffixes and use rmwcc.h just like was (more or less)
>> recently done for bitops.h as well.
>
> Why? bts (etc) on memory don't really have an 'operand size'.
Of course they do - dependin
of_find_node_by_path() acquires a reference to the node
returned by it and that reference needs to be dropped by its caller.
bl_idle_init() doesn't do that, so fix it.
Signed-off-by: Yangtao Li
---
drivers/ata/pata_macio.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/ata/pata_ma
On Mon, Nov 19, 2018 at 02:18:51PM +, Quentin Perret wrote:
> +static void sched_energy_start(int ndoms_new, cpumask_var_t doms_new[])
> +{
> + /*
> + * The conditions for EAS to start are checked during the creation of
> + * root domains. If one of them meets all conditions, it
Em Wed, Nov 21, 2018 at 02:02:02PM +0100, Jiri Olsa escreveu:
> On Wed, Nov 21, 2018 at 09:54:08AM -0300, Arnaldo Carvalho de Melo wrote:
> > Em Wed, Nov 21, 2018 at 09:51:30AM -0300, Arnaldo Carvalho de Melo escreveu:
> > > Em Thu, Nov 15, 2018 at 04:14:42PM +0100, Jiri Olsa escreveu:
> > > > On T
Em Wed, Nov 21, 2018 at 07:45:28AM +, Song Liu escreveu:
> Hi,
>
> I found perf-record --tail-synthesize without --overwrite breaks symbols
> for perf-script, perf-report, etc. For example:
>
> [root@]# ~/perf record -ag --tail-synthesize -- sleep 1
> [ perf record: Woken up 1 times to write
of_find_node_by_path() acquires a reference to the node
returned by it and that reference needs to be dropped by its caller.
bl_idle_init() doesn't do that, so fix it.
Signed-off-by: Yangtao Li
---
drivers/tty/sysrq.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/tty/sysrq.c b/dr
On Tue, Nov 20, 2018 at 07:03:17PM +, Will Deacon wrote:
> On Tue, Nov 20, 2018 at 06:28:54PM +, Will Deacon wrote:
> > On Sat, Nov 10, 2018 at 11:17:03AM +, Jan Glauber wrote:
> > > On Fri, Nov 09, 2018 at 03:58:56PM +, Will Deacon wrote:
> > > > On Fri, Nov 09, 2018 at 02:37:51PM
On Sun, 11 Nov 2018, Greg Kroah-Hartman wrote:
> 4.19-stable review patch. If anyone has any objections, please let me know.
Greg, please drop this patch from all -stable for now. Version that
wouldn't have such performance impact is being worked on.
--
Jiri Kosina
SUSE Labs
Hi Sakari,
On Mon, Nov 19, 2018 at 11:24:20PM +0200, Sakari Ailus wrote:
> Hi Maxime,
>
> On Tue, Nov 06, 2018 at 03:54:20PM +0100, Maxime Ripard wrote:
> > Cadence has designed a D-PHY that can be used by the, currently in tree,
> > DSI bridge (DRM), CSI Transceiver and CSI Receiver (v4l2) drive
On 11/13/18 7:22 PM, Vlastimil Babka wrote:
> On 11/12/18 10:55 AM, David Laight wrote:
>> From: Vlastimil Babka [mailto:vba...@suse.cz]
>>> Sent: 09 November 2018 19:16
>> ...
>>> This? Not terribly elegant, but I don't see a nicer way right now...
>>
>> Maybe just have two copies of the function
Josh,
On Mon, 19 Nov 2018, Josh Hunt wrote:
> We have a class of machines that appear to be exhausting the vector space on
> cpus 0 and 1 which causes some breakage later on when trying to set the
> affinity. The boxes are running the 4.14 LTS kernel.
>
> [ 39.531385] __assign_irq_vector: irq:5
of_find_node_by_path() acquires a reference to the node
returned by it and that reference needs to be dropped by its caller.
bl_idle_init() doesn't do that, so fix it.
Signed-off-by: Yangtao Li
---
drivers/input/misc/sparcspkr.c | 9 ++---
1 file changed, 6 insertions(+), 3 deletions(-)
dif
The patch
ASoC: sdm845: Add support for Secondary MI2S interface
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) an
The patch
regulator: wm8994: Don't use devres for enable GPIOs
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 ho
The patch
regulator: core: Only count load for enabled consumers
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24
The patch
ASoC: sdm845: Update slot_width for Quaternary TDM port
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) a
The patch
spi: spi-qcom-qspi: Fix remaining driver nits
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) an
On 21/11/2018 12:49, Yangtao Li wrote:
> of_find_node_by_path() acquires a reference to the node
> returned by it and that reference needs to be dropped by its caller.
> bl_idle_init() doesn't do that, so fix it.
>
> Signed-off-by: Yangtao Li
> ---
> drivers/soc/tegra/common.c | 5 -
> 1 f
The patch
regulator: core: Avoid propagating to supplies when possible
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the ne
help
On 11/20/18 11:36 PM, Ingo Molnar wrote:
>
> [ Cc:-ed a few other gents and lkml. ]
>
> * Jens Axboe wrote:
>
>> Hi,
>>
>> So this is a fun one... While I was doing the aio polled work, I noticed
>> that the submitting process spent a substantial amount of time copying
>> data to/from userspace
On Tue, Sep 11, 2018 at 11:24 PM, David Howells wrote:
> Stephen Rothwell wrote:
>
>> I will apply this fix until the proper fix arrives in the vfs tree:
>
> Thanks.
>
> David
This was fixed in September, but the Reported-by tag wasn't added and
nobody told syzbot that this is fixed. So the bug
On Wed, Nov 21, 2018 at 01:55:51PM +0900, Sergey Senozhatsky wrote:
> On (11/16/18 16:20), Minchan Kim wrote:
> > + zram_set_flag(zram, index, ZRAM_UNDER_WB);
> > + zram_slot_unlock(zram, index);
> > + if (zram_bvec_read(zram, &bvec, index, 0, NULL)) {
> > +
On Tue, 20 Nov 2018, Tim Chen wrote:
> diff --git a/arch/x86/kernel/process.c b/arch/x86/kernel/process.c
> index 74bef48..48fcd46 100644
> --- a/arch/x86/kernel/process.c
> +++ b/arch/x86/kernel/process.c
> @@ -406,6 +406,8 @@ static __always_inline void spec_ctrl_update_msr(unsigned
> long tifn)
On Wed, Nov 21, 2018 at 12:44:27PM +0100, Hans de Goede wrote:
> On 20-11-18 16:59, Andy Shevchenko wrote:
> > i2c_acpi_new_device() doesn't assign fwnode like it's done, for example,
> > in i2c_acpi_register_devices() path.
> >
> > Assign fwnode in i2c_acpi_new_device() as it's done elsewhere.
>
On Tue, 20 Nov 2018, Tim Chen wrote:
> #if defined(CONFIG_SMP) && defined(CONFIG_HOTPLUG_SMT)
> -extern enum cpuhp_smt_control cpu_smt_control;
> +DECLARE_STATIC_KEY_TRUE(cpu_smt_enabled);
> +#define cpu_use_smt_and_hotplug (static_branch_likely(&cpu_smt_enabled))
Errm. No. This looks like a
On 11/21/2018 02:32 PM, Jens Axboe wrote:
On 11/20/18 11:36 PM, Ingo Molnar wrote:
* Jens Axboe wrote:
So this is a fun one... While I was doing the aio polled work, I noticed
that the submitting process spent a substantial amount of time copying
data to/from userspace. For aio, that's iocb an
On Wed, 2018-11-21 at 06:32 -0700, Jens Axboe wrote:
> I did some more investigation yesterday, and found this:
>
> commit 236222d39347e0e486010f10c1493e83dbbdfba8
> Author: Paolo Abeni
> Date: Thu Jun 29 15:55:58 2017 +0200
>
> x86/uaccess: Optimize copy_user_enhanced_fast_string() for sh
On 11/20/2018 11:28 PM, Trent Piepho wrote:
> On Tue, 2018-11-20 at 21:42 +0100, Stefan Agner wrote:
>> On 20.11.2018 20:13, Trent Piepho wrote:
>>> It also seems to me that this doesn't need to be in the internal pci
>>> config access functions. The driver shouldn't be reading registers
>>> that
From: Jan Beulich
> Sent: 21 November 2018 13:03
>
> >>> On 21.11.18 at 12:55, wrote:
> > From: Jan Beulich
> >> Sent: 21 November 2018 10:11
> >>
> >> Add missing insn suffixes and use rmwcc.h just like was (more or less)
> >> recently done for bitops.h as well.
> >
> > Why? bts (etc) on memory
Hi Dave,
thanks for your patch set. Just some initial comments:
I think the three patches
[PATCH 2/6] lib/lzo: enable 64-bit CTZ on Arm
[PATCH 3/6] lib/lzo: 64-bit CTZ on Arm aarch64
[PATCH 4/6] lib/lzo: fast 8-byte copy on arm64
should be applied in any case - could you please make an e
On Tue, 20 Nov 2018, Tim Chen wrote:
> According to software guidance:
>
> "Setting ... STIBP ... on a logical processor prevents the predicted
> targets of indirect branches on any logical processor of that core
> from being controlled by software that executes (or executed
> previously) on anoth
On Wed, Nov 21, 2018 at 02:21:15PM +0100, Jiri Kosina wrote:
> On Sun, 11 Nov 2018, Greg Kroah-Hartman wrote:
>
> > 4.19-stable review patch. If anyone has any objections, please let me know.
>
> Greg, please drop this patch from all -stable for now. Version that
> wouldn't have such performanc
> -/*
> - * Free all functions' kobjects in the array up to some limit. When limit is
> - * NULL, all kobjects are freed.
> - */
> -static void klp_free_funcs_limited(struct klp_object *obj,
> -struct klp_func *limit)
> +static void klp_free_funcs(struct klp_object *
of_find_node_by_path() acquires a reference to the node returned by
it and that reference needs to be dropped by its caller.soc_is_tegra()
doesn't do that, so fix it.Call of_machine_is_compatible() to refactor
soc_is_tegra() whcih automatically manages the reference count.
Signed-off-by: Yangtao L
This device makes a loud buzzing sound when a headphone is inserted while
playing audio at full volume through the speaker.
Signed-off-by: Girija Kumar Kasinadhuni
---
sound/pci/hda/patch_realtek.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/sound/pci/hda/patch_realtek.c b/sound/pc
Hi guys,
On Wed, Nov 21, 2018 at 03:35:49PM +0200, Andy Shevchenko wrote:
> On Wed, Nov 21, 2018 at 12:44:27PM +0100, Hans de Goede wrote:
> > I see 2 possible solutions here:
> >
> > 1) Changing this patch so that i2c_acpi_new_device() does:
> >
> > /*
> > * The fwnode can not
On Wed, Nov 21, 2018 at 01:47:05PM +, Leonard Crestez wrote:
> On 11/20/2018 11:28 PM, Trent Piepho wrote:
> > On Tue, 2018-11-20 at 21:42 +0100, Stefan Agner wrote:
> >> On 20.11.2018 20:13, Trent Piepho wrote:
>
> >>> It also seems to me that this doesn't need to be in the internal pci
> >>>
On 11/21/18 11:14 AM, Mel Gorman wrote:
> The page allocator zone lists are iterated based on the watermarks
> of each zone which does not take anti-fragmentation into account. On
> x86, node 0 may have multiple zones while other nodes have one zone. A
> consequence is that tasks running on node 0
101 - 200 of 909 matches
Mail list logo
