‐‐‐ Original Message ‐‐‐
On Wednesday, October 31, 2018 9:29 AM, Hans de Goede
wrote:
> Hi,
>
> On 31-10-18 07:02, Mogens Jensen wrote:
>
> > ‐‐‐ Original Message ‐‐‐
> > On Tuesday, October 30, 2018 7:10 PM, Hans de Goede hdego...@redhat.com
> > wrote:
> >
> > > Hi,
> > > On 30
On 31 October 2018 at 16:56, Linus Walleij wrote:
> On Mon, Oct 22, 2018 at 9:44 AM Baolin Wang wrote:
>
>> This patch adds the Spreadtrum SC27XX serial PMICs fuel gauge support,
>> which is used to calculate the battery capacity.
>>
>> Original-by: Yuanjiang Yu
>> Signed-off-by: Baolin Wang
>>
Hi Arnd,
I guess you may have missed this pull request.
Thanks,
Chunyan
On Thu, 18 Oct 2018 at 17:19, Chunyan Zhang wrote:
>
> Hi Arnd,
>
> For 4.20-rc1 there's one patch only for sprd devicetree, please pull from my
> git tree:
>
> https://github.com/lyrazhang/linux.git m-v4.19-rc1
>
> Please
This patchset adds initial pinctrl support for Mediatek MT6797 SoC.
The pinctrl driver is based on the vendor binding as like MT6765 and
implements only GPIO and pinmux functionalities.
The devicetree binding document consists of pinmux, pinconf and
interrupt functionalities documented since the b
Add initial pinctrl driver for Mediatek MT6797 SoC supporting only
GPIO and pinmux configurations.
Tested-by: Matthias Brugger
Acked-by: Sean Wang
Signed-off-by: Manivannan Sadhasivam
---
drivers/pinctrl/mediatek/Kconfig |7 +
drivers/pinctrl/mediatek/Makefile |
Add devicetree bindings for Mediatek MT6797 SoC Pin Controller.
Signed-off-by: Manivannan Sadhasivam
---
.../bindings/pinctrl/pinctrl-mt6797.txt | 74 +
include/dt-bindings/pinctrl/mt6797-pinfunc.h | 1368 +
2 files changed, 1442 insertions(+)
create mode 100644 Documen
Add pinctrl support for Mediatek MT6797 SoC.
Signed-off-by: Manivannan Sadhasivam
---
arch/arm64/boot/dts/mediatek/mt6797.dtsi | 14 ++
1 file changed, 14 insertions(+)
diff --git a/arch/arm64/boot/dts/mediatek/mt6797.dtsi
b/arch/arm64/boot/dts/mediatek/mt6797.dtsi
index 4beaa71107
Add pinmux support for UART1 on MediatekX20 Development board based
on Mediatek MT6797 SoC.
Signed-off-by: Manivannan Sadhasivam
---
arch/arm64/boot/dts/mediatek/mt6797-x20-dev.dts | 2 ++
arch/arm64/boot/dts/mediatek/mt6797.dtsi| 7 +++
2 files changed, 9 insertions(+)
diff --git a
On Wed, Oct 31, 2018 at 03:40:02PM +, Pasha Tatashin wrote:
>
>
> On 10/17/18 7:54 PM, Alexander Duyck wrote:
> > This patch introduces a new iterator for_each_free_mem_pfn_range_in_zone.
> >
> > This iterator will take care of making sure a given memory range provided
> > is in fact contain
This patch adds a DT binding documentation for the MT8183 soc.
Signed-off-by: Leilk Liu
---
.../devicetree/bindings/spi/spi-mt65xx.txt |1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/spi/spi-mt65xx.txt
b/Documentation/devicetree/bindings/spi/spi-
>From 44b1c34bc19d9bfdc736664439c0530fbb2c75b8 Mon Sep 17 00:00:00 2001
From: Leilk Liu
Date: Thu, 1 Nov 2018 11:48:20 +0800
Subject: [PATCH 0/2] add SPI driver support for mt8183
This series are based on 4.19-rc1 and provide two patches to support mt8183 IC.
Leilk Liu (2):
spi: mediatek: Add
this patch add support for mt8183 IC.
Signed-off-by: Leilk Liu
---
drivers/spi/spi-mt65xx.c |9 +
1 file changed, 9 insertions(+)
diff --git a/drivers/spi/spi-mt65xx.c b/drivers/spi/spi-mt65xx.c
index 0c2867d..9ee1fe9 100644
--- a/drivers/spi/spi-mt65xx.c
+++ b/drivers/spi/spi-mt65x
On 1 November 2018 at 08:44, Nathan Chancellor wrote:
> Clang warns when one enumerated type is implicitly converted to another:
>
> drivers/pinctrl/sprd/pinctrl-sprd.c:845:19: warning: implicit conversion
> from enumeration type 'enum sprd_pinconf_params' to different
> enumeration type 'enum pin
On 31/10/18 18:58, Daniel Bristot de Oliveira wrote:
> On 10/31/18 5:40 PM, Juri Lelli wrote:
> > On 31/10/18 17:18, Daniel Bristot de Oliveira wrote:
> >> On 10/30/18 12:08 PM, luca abeni wrote:
> >>> Hi Peter,
> >>>
> >>> On Tue, 30 Oct 2018 11:45:54 +0100
> >>> Peter Zijlstra wrote:
> >>> [...]
Hello Greg, Linus,
Greg, I didn't get your feedback on v10 of the i3c patchset [1] where I
was asking if you'd agree to have this framework merged in 4.20 (I know
you were busy with the 4.19 release and after that the Kernel Summit, so
that's not a surprise), so I'm sending this PR. It's really no
Please pull this to fixup dtb Kbuild rules for csky subsystem.
The following changes since commit ac435075892e3e651c667b4a9f2267cf3ef1d5a2:
Merge tag 'csky-for-linus-4.20' of https://github.com/c-sky/csky-linux
(2018-10-29 08:25:00 -0700)
are available in the git repository at:
https://git
The printk timestamps are very useful information to visually see
where kernel is spending time during boot. It also helps us see
the timing of hotplug events at runtime.
This patch enables printk timestamps in RISC-V defconfig so that
we have it enabled by default (similar to other architectures
This patch updates defconfig using savedefconfig on Linux-4.19.
Signed-off-by: Anup Patel
---
arch/riscv/configs/defconfig | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/arch/riscv/configs/defconfig b/arch/riscv/configs/defconfig
index 36473d7dbaac..07fa9ea7
+ Chandan from Display Port team,
On 10/30/2018 10:03 PM, Stephen Boyd wrote:
Quoting Taniya Das (2018-10-29 23:01:44)
On 10/30/2018 12:13 AM, Stephen Boyd wrote:
Quoting Taniya Das (2018-10-28 03:34:55)
On 2018-10-19 16:04, Taniya Das wrote:
On 10/10/2018 2:04 AM, Stephen Boyd wrote:
Quoti
On Wed, Oct 31, 2018 at 11:17:48AM -0700, Paul E. McKenney wrote:
> On Tue, Oct 30, 2018 at 06:11:19PM -0700, Joel Fernandes wrote:
> > Hi Paul,
> >
> > On Tue, Oct 30, 2018 at 04:43:36PM -0700, Paul E. McKenney wrote:
> > > On Tue, Oct 30, 2018 at 03:26:49PM -0700, Joel Fernandes wrote:
> > > > H
On Wed, Oct 31, 2018 at 9:23 AM Jann Horn wrote:
>
> +linux-api, Andy Lutomirski, Eric Biederman
>
> On Wed, Oct 31, 2018 at 3:12 AM Daniel Colascione wrote:
> > Add a simple proc-based kill interface. To use /proc/pid/kill, just
> > write the signal number in base-10 ASCII to the kill file of th
Hi Adrian,
my fix is evidently incomplete - I just crashed elgar trying to remove
the pata_buddha module, sorry. Must've done something silly.
So no, can't post a patch to add module_exit just yet.
Cheers,
Michael
Am 31.10.2018 um 23:06 schrieb John Paul Adrian Glaubitz:
Hi!
On 1
On Thu, Nov 1, 2018 at 4:20 AM Olof Johansson wrote:
>
> On Wed, Oct 31, 2018 at 1:42 PM Palmer Dabbelt wrote:
> >
> > On Wed, 31 Oct 2018 12:20:40 PDT (-0700), Olof Johansson wrote:
> > > On Tue, Oct 30, 2018 at 5:37 AM Anup Patel wrote:
> > >>
> > >> The printk timestamps are very useful infor
Hi all,
On Thu, 1 Nov 2018 09:13:07 +0800 kernel test robot
wrote:
>
> Greetings,
>
> 0day kernel testing robot got the below dmesg and the first bad commit is
>
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
>
> commit b179f0826c6a13563c5ce0554c6da6748a1fa699
>
On Thu, Nov 1, 2018 at 3:59 AM James Bottomley
wrote:
>
> On Tue, 2018-10-16 at 11:52 +0200, Laurent Vivier wrote:
> > Hi,
> >
> > Any comment on this last version?
> >
> > Any chance to be merged?
>
> I've got a use case for this: I went to one of the Graphene talks in
> Edinburgh and it struck
Hi all,
Please do not add any v4.21/v5.1 code to your linux-next included trees
until after the merge window closes.
Changes since 20181031:
My fixes tree contains this:
"drivers: net: include linux/ip.h for iphdr"
Non-merge commits (relative to Linus' tree): 790
953 files
Hi Arnd,
On Thu, Nov 1, 2018 at 6:42 AM Arnd Bergmann wrote:
>
> On 10/31/18, Randy Dunlap wrote:
> > On 10/30/18 8:59 PM, Stephen Rothwell wrote:
> >> Hi all,
> >>
> >> Please do not add any v4.21/v5.1 code to your linux-next included trees
> >> until after the merge window closes.
> >>
> >> C
Em qua, 2018-10-31 às 20:24 -0300, Leonardo Bras escreveu:
> Em seg, 2018-10-29 às 01:42 +0900, Masahiro Yamada escreveu:
> > On Wed, Oct 24, 2018 at 1:05 PM Leonardo Bras
> > wrote:
> > > Changes the parameter name to avoid shadowing a variable.
> > >
> > > Signed-off-by: Leonardo Bras
> >
> >
Refactors the code to accept the modules list as a parameter in
the functions that need it, and moves the variable from the
global scope to the main function scope.
This also fixes the parameter shadowing of add_depends.
Signed-off-by: Leonardo Bras
---
scripts/mod/modpost.c | 39 ++
On Wed, Oct 31, 2018 at 2:10 AM, Peter Zijlstra wrote:
> On Tue, Oct 30, 2018 at 04:28:16PM +, Will Deacon wrote:
>> On Tue, Oct 30, 2018 at 04:58:41PM +0100, Peter Zijlstra wrote:
>> > Like mentioned elsewhere; if you do write_enable() + write_disable()
>> > thingies, it all becomes:
>> >
>>
On 18-10-31 18:15:39, Peter Zijlstra wrote:
> On Wed, Oct 31, 2018 at 11:07:22AM -0400, Waiman Long wrote:
> > On 10/31/2018 10:10 AM, Peter Zijlstra wrote:
> > > On Wed, Oct 31, 2018 at 09:54:17AM +0800, Yi Sun wrote:
> > >> On 18-10-23 17:33:28, Yi Sun wrote:
> > >>> On 18-10-23 10:51:27, Peter Z
Hi Larry,
I still have a few tiny comments for your patch, please refer to them.
On 2018/11/1 5:28, Andrew Morton wrote:
>
> Folks, could we please review this patch for upstream inclusion?
>
> Thanks.
>
>
> From: Larry Chen
> Subject: ocfs2: fix deadlock caused by ocfs2_defrag_extent
>
> o
Refactors the code to accept the modules list as a parameter in
the functions that need it, and moves the variable from the
global scope to the main function scope.
This also fixes the parameter shadowing of add_depends.
Signed-off-by: Leonardo Bras
---
scripts/mod/modpost.c | 39 ++
From: Long Li
On a large system with multiple devices of the same class (e.g. NVMe disks,
using managed IRQs), the kernel tends to concentrate their IRQs on several
CPUs.
The issue is that when NVMe calls irq_matrix_alloc_managed(), the assigned
CPU tends to be the first several CPUs in the cpum
Hi Linus,
This tag has a few merge conflicts with some x86/cpu id changes. Stephen
Rothwell's merge in next/master is correct, and I have provided an
example here as well:
git://git.infradead.org/linux-platform-drivers-x86.git pdx86-v4.20-1-merge
Thanks,
Darren Hart
VMware Open Source Technol
On Tue, 2018-10-16 at 11:52 +0200, Laurent Vivier wrote:
> Hi,
>
> Any comment on this last version?
>
> Any chance to be merged?
I've got a use case for this: I went to one of the Graphene talks in
Edinburgh and it struck me that we seem to keep reinventing the type of
sandboxing that qemu-use
Starting with GCC 8, a lot of unlikely code was moved out of line to
"cold" subfunctions in .text.unlikely.
For example, the unlikely bits of:
irq_do_set_affinity()
are moved out to the following subfunction:
irq_do_set_affinity.cold.49()
Starting with GCC 9, the numbered suffix has been r
Em Thu, 1 Nov 2018 08:28:20 +1100
Stephen Rothwell escreveu:
> Hi all,
>
> Building Linus' tree, today's linux-next build (x86_64 allmodconfig)
> produced this warning:
>
> ./usr/include/linux/v4l2-controls.h:1105: found __[us]{8,16,32,64} type
> without #include
>
> Introduced by commit
>
Fixes gcc '-Wunused-but-set-variable' warning:
drivers/firewire/net.c:488:9: warning:
variable ‘guid’ set but not used [-Wunused-but-set-variable]
It not used anymore after commit 6752c8db8e0c ("firewire net, ipv4 arp:
Extend hardware address and remove driver-level packet inspection.")
Signed
Fixes gcc '-Wunused-but-set-variable' warning:
drivers/edac/i82975x_edac.c:378:16: warning:
variable ‘dtype’ set but not used [-Wunused-but-set-variable]
It never used since introduction in commit
084a4fccef39 ("edac: move dimm properties to struct dimm_info")
Signed-off-by: YueHaibing
---
dr
Hi Rob,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 5b7449810ae6d652629c550d3974c8453836d229
commit: 37c8a5fafa3bb7dcdd51774be353be6cb2912b86 kbuild: consolidate Devicetree
dtb build rules
date: 4 weeks ago
co
On Wed, Oct 31, 2018 at 07:21:15PM +0100, Thomas Gleixner wrote:
> The SPDX identifier defines the license of the file already. No need for
> the boilerplate.
>
> Signed-off-by: Thomas Gleixner
> Cc: Richard Cochran
> ---
>
> @Richard: This file is (C) OMICRON, but I don't have a contact
> anym
On 2018/10/31 22:00, Peter Zijlstra wrote:
On Wed, Oct 31, 2018 at 02:53:20PM +0100, Peter Zijlstra wrote:
On Wed, Oct 31, 2018 at 02:01:20PM +0800, Zhenzhong Duan wrote:
On 2018/10/30 16:36, Peter Zijlstra wrote:
On Mon, Oct 29, 2018 at 11:55:06PM -0700, Zhenzhong Duan wrote:
Since CONFIG_RE
From: Marcel Ziswiler
As UARTB and VFIR share their clock enable bit it is rather unwise for
the kernel to turn off the VFIR one should that be unused (and
potentially vice versa but so far there anyway is no VFIR driver).
Without this patch trying to use UARTB with the regular 8250 driver
will
From: Marcel Ziswiler
Fix a few spelling mistakes I stumbled upon while debugging a customers
UART issues.
Signed-off-by: Marcel Ziswiler
---
drivers/tty/serial/serial-tegra.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/drivers/tty/serial/serial-tegra.c
b/
From: Marcel Ziswiler
Get rid of 3 duplicate defines.
Signed-off-by: Marcel Ziswiler
---
drivers/clk/tegra/clk-tegra-periph.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/clk/tegra/clk-tegra-periph.c
b/drivers/clk/tegra/clk-tegra-periph.c
index 38c4eb28c8bf..cc5275ec2c01 10
This series features some UART related clock issue fix and clean-up.
Marcel Ziswiler (3):
clk: tegra: get rid of duplicate defines
clk: tegra: ignore unused vfir clock shared with uartb
serial: tegra: fix some spelling mistakes
drivers/clk/tegra/clk-tegra-periph.c | 5 +
drivers/tt
On (10/31/18 13:27), Petr Mladek wrote:
> >
> > Signed-off-by: Sergey Senozhatsky
>
> The patch makes sense to me. The locks should stay busted also for
> console_flush_on_panic().
>
> With the added #include :
>
> Reviewed-by: Petr Mladek
Thanks!
Since there are no objections - how shall w
Two small fixes, please pull.
Thanks!
The following changes since commit 4b42745211af552f170f38a1b97f4a112b5da6b2:
Merge tag 'armsoc-soc' of
git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc (2018-10-29 15:37:33
-0700)
are available in the Git repository at:
git://git.kernel.or
CC Philip, current kbuild test robot maintainer.
On Wed, Oct 31, 2018 at 12:12:21PM -0600, Logan Gunthorpe wrote:
On 2018-10-31 11:52 a.m., Olof Johansson wrote:
I've migrated machines to a new system and that CI is up and running.
Right now the emails don't go anywhere but me, but let me know
made minor cleanup to patch 1 and 2, added Ronnie's reviewed to patch
3, and tentatively merged to cifs-2.6.git for-next
On Wed, Oct 31, 2018 at 5:16 PM Long Li wrote:
>
> From: Long Li
>
> With direct read/write functions implemented, add them to file_operations.
>
> Dircet I/O is used under two
On Thu, Nov 01, 2018 at 01:27:08AM +0100, Alexandre Belloni wrote:
Hello,
On 31/10/2018 19:12:06-0400, Sasha Levin wrote:
- m->rtc = rtc_device_register(DRIVER_NAME,
- &m->client->dev,
- &menelaus_rtc_ops, THIS_MODULE);
- if (IS_ERR(m->rtc
Randomize address space after each fork
~~
I might be entirely wrong with what I write
and the solution proposed thereafter, yet I
want to raise awareness that with current linux
kernels it is possible to leak (at least) heap
addresses in an attempt to weake
Hi Peter,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 5b7449810ae6d652629c550d3974c8453836d229
commit: 7aa54be2976550f17c11a1c3e3630002dea39303 locking/qspinlock, x86:
Provide liveness guarantee
date: 2 weeks
On 10/31/18 5:48 PM, kbuild test robot wrote:
> Hi Rakesh,
>
> FYI, the error/warning still remains.
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> master
> head: 5b7449810ae6d652629c550d3974c8453836d229
> commit: 6bae5ea9498926440ffc883f3dbceb0adc65e492 ASoC:
Hi Arnd,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 5b7449810ae6d652629c550d3974c8453836d229
commit: 21924765862a0871908a35cb0e53e2e1c169b888 SUNRPC: use cmpxchg64() in
gss_seq_send64_fetch_and_inc()
date: 4
Clang warns when one enumerated type is implicitly converted to another:
drivers/pinctrl/pinctrl-zynq.c:985:18: warning: implicit conversion from
enumeration type 'enum zynq_pin_config_param' to different enumeration
type 'enum pin_config_param' [-Wenum-conversion]
{"io-standard", PIN_CONF
On Wed, Oct 31, 2018 at 07:17:45AM -0700, Christoph Hellwig wrote:
> On Wed, Oct 31, 2018 at 04:46:10PM +0530, Anup Patel wrote:
> > I agree that we need a place for vendor-specific ISA extensions and
> > having vendor-specific directories is also good.
>
> The only sensible answer is that we shou
Clang warns when one enumerated type is implicitly converted to another:
drivers/rtc/rtc-omap.c:574:21: warning: implicit conversion from
enumeration type 'enum rtc_pin_config_param' to different enumeration
type 'enum pin_config_param' [-Wenum-conversion]
{"ti,active-high", PIN_CONFIG_ACT
Clang warns when one enumerated type is implicitly converted to another:
drivers/pinctrl/pinctrl-lpc18xx.c:643:29: warning: implicit conversion
from enumeration type 'enum lpc18xx_pin_config_param' to different
enumeration type 'enum pin_config_param' [-Wenum-conversion]
{"nxp,gpio-pin-int
Clang warns when one enumerated type is implicitly converted to another:
drivers/pinctrl/pinctrl-max77620.c:56:12: warning: implicit conversion
from enumeration type 'enum max77620_pinconf_param' to different
enumeration type 'enum pin_config_param' [-Wenum-conversion]
.param = MAX
On 10/31/18 2:02 PM, Fenghua Yu wrote:
> resctrl tests will be implemented. README is added for the tool first.
>
> Signed-off-by: Fenghua Yu
Hi,
> ---
> tools/testing/selftests/resctrl/README | 53
> ++
> 1 file changed, 53 insertions(+)
> create mode 100644
Hi Rakesh,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 5b7449810ae6d652629c550d3974c8453836d229
commit: 6bae5ea9498926440ffc883f3dbceb0adc65e492 ASoC: hdac_hda: add asoc
extension for legacy HDA codec drivers
da
Clang warns when one enumerated type is implicitly converted to another:
drivers/pinctrl/bcm/pinctrl-bcm2835.c:707:40: warning: implicit
conversion from enumeration type 'enum bcm2835_pinconf_param' to
different enumeration type 'enum pin_config_param' [-Wenum-conversion]
configs[0] = pinc
Clang warns when one enumerated type is implicitly converted to another:
drivers/pinctrl/sprd/pinctrl-sprd.c:845:19: warning: implicit conversion
from enumeration type 'enum sprd_pinconf_params' to different
enumeration type 'enum pin_config_param' [-Wenum-conversion]
{"sprd,control", SPRD
On Oct 30, 2018, at 9:39 PM, Vasily Averin wrote:
>
> On 10/31/2018 04:30 AM, Andreas Dilger wrote:
>> Could you please explain your statement below that on-stack
>> initialization does not zero unspecified fields? According
>> to documents I found, for example:
>>
>> https://gcc.gnu.org/online
IRQ_MATRIX_SIZE is the number of longs needed for a bitmap,
multiplied by the size of a long, yielding a byte count. But
it is used as the size of an array of longs, which is way more
memory than is needed. Change IRQ_MATRIX_SIZE so it is just the
number of longs needed and the arrays come out the
Hello,
On 31/10/2018 19:12:06-0400, Sasha Levin wrote:
> - m->rtc = rtc_device_register(DRIVER_NAME,
> - &m->client->dev,
> - &menelaus_rtc_ops, THIS_MODULE);
> - if (IS_ERR(m->rtc)) {
> + err = rtc_register_device(m->rtc);
This appeared in v4.1
ldsem_down_read() will sleep if there is pending writer in the queue.
If the writer times out, readers in the queue should be woken up,
otherwise they may miss a chance to acquire the semaphore until the last
active reader will do ldsem_up_read().
There was a couple of reports where there was one
From: Peter Zijlstra
For some reason ldsem has its own lockdep wrappers, make them go away.
Cc: Greg Kroah-Hartman
Cc: Jiri Slaby
Signed-off-by: Peter Zijlstra (Intel)
Signed-off-by: Dmitry Safonov
---
drivers/tty/tty_ldsem.c | 51 +++--
1 file changed, 1
As notted by Jiri, tty_ldisc_reinit() shouldn't rely on tty counter.
Simplify math by increasing the counter after reinit success.
Cc: Greg Kroah-Hartman
Cc: Jiri Slaby
Link: lkml.kernel.org/r/<20180829022353.23568-2-d...@arista.com>
Suggested-by: Jiri Slaby
Reviewed-by: Jiri Slaby
Tested-by:
Make sure under CONFIG_LOCKDEP that each change to line discipline
is done with held write semaphor.
Otherwise potential reader will have a good time dereferencing
incomplete/uninitialized ldisc.
An exception here is tty_ldisc_open(), as it's called without ldisc_sem
locked by tty_init_dev() => tt
It seems like when ldsem_down_read() fails with timeout, it misses
update for sem->wait_readers. By that reason, when writer finally
releases write end of the semaphore __ldsem_wake_readers() does adjust
sem->count with wrong value:
sem->wait_readers * (LDSEM_ACTIVE_BIAS - LDSEM_WAIT_BIAS)
I.e, if
There might be situations where tty_ldisc_lock() has blocked, but there
is already IO on tty and it prevents line discipline changes.
It might theoretically turn into dead-lock.
Basically, provide more priority to pending tty_ldisc_lock() than to
servicing reads/writes over tty.
User-visible issu
tty_ldisc_reinit() doesn't race with neither tty_ldisc_hangup()
nor set_ldisc() nor tty_ldisc_release() as they use tty lock.
But it races with anyone who expects line discipline to be the same
after hoding read semaphore in tty_ldisc_ref().
We've seen the following crash on v4.9.108 stable:
BUG:
Hi all,
Here are fixes that worth to have in the @stable, as they were hit by
different people, including Arista on v4.9 stable.
And for linux-next - adding lockdep asserts for line discipline changing
code, verifying that write ldisc sem will be held forthwith.
Mikulas, can you add your tested-
When the OS registers to handle events from the display off hotkey the
EC will send a notification with 0x35 for every key press, independent
of the backlight state.
The behavior of this key on Windows, with the ATKACPI driver from Asus
installed, is turning off the backlight of all connected disp
According to Asus firmware engineers, the meaning of these codes is only
to notify the OS that the screen brightness has been turned on/off by
the EC. This does not match the meaning of KEY_DISPLAYTOGGLE /
KEY_DISPLAY_OFF, where userspace is expected to change the display
brightness.
Signed-off-by
Asus laptops have a hotkey function on the F7 key to turn the display
backlight OFF, labeled with a screen with a X inside, as shown on
https://dlcdnimgs.asus.com/websites/global/products/Xep1ZcSY8dyWXK11/images/keyboard.png
This hotkey worked on very few Asus models, where the EC acts on the
back
In the past, Asus firmwares would change the panel backlight directly
through the EC when the display off hotkey (Fn+F7) was pressed, and
only notify the OS of such change, with 0x33 when the LCD was ON and
0x34 when the LCD was OFF. These are currently mapped to
KEY_DISPLAYTOGGLE and KEY_DISPLAY_O
Quoting Lina Iyer (2018-10-31 09:46:50)
> On Wed, Oct 31 2018 at 01:05 -0600, Stephen Boyd wrote:
> >Hi Lina,
> >
> >Quoting Lina Iyer (2018-10-10 17:29:58)
> >> QCOM SoC's that have Power Domain Controller (PDC) chip in the always-on
> >> domain can wakeup the SoC, when interrupts and GPIOs are ro
From: Jonathan Marek
This patch adds an of_match for the usb-otg-vbus regulator to
bq24190_charger.
Signed-off-by: Jonathan Marek
Signed-off-by: Brian Masney
---
drivers/power/supply/bq24190_charger.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/power/supply/bq24190_charger.c
Add support for the ti,bq24192 variant and a child node for the
usb-otg-vbus regulator.
Signed-off-by: Brian Masney
---
.../devicetree/bindings/power/supply/bq24190.txt | 9 +
1 file changed, 9 insertions(+)
diff --git a/Documentation/devicetree/bindings/power/supply/bq24190.txt
This adds the gpio-ranges property to pm8941_gpios so that the GPIO
pins are initialized by the GPIO framework and not pinctrl. This fixes
a circular dependency so GPIO hogging can be used on this board.
Signed-off-by: Brian Masney
---
arch/arm/boot/dts/qcom-pm8941.dtsi | 1 +
1 file changed, 1
Add extcon support so that we can notify USB drivers of cable state
changes. Based on work from Jonathan Marek. USB OTG was tested on a LG
Nexus 5 (hammerhead) phone.
Signed-off-by: Brian Masney
---
drivers/power/supply/bq24190_charger.c | 37 +-
1 file changed, 36 insert
Add the device tree bindings for USB OTG support. Driver was tested
using on a LG Nexus 5 (hammerhead) phone. This patch is based on work
from Jonathan Marek and from the other msm8974 devices.
Signed-off-by: Brian Masney
---
.../qcom-msm8974-lge-nexus5-hammerhead.dts| 60 +++
From: Jonathan Marek
This patch adds support for the bq24192 variant to bq24190_charger.
Signed-off-by: Jonathan Marek
[masn...@onstation.org: Changed if statement to a switch based on
feedback from Sebastian Reichel.]
Signed-off-by: Brian Masney
---
drivers/power/supply/bq24190_charger.c | 1
When attempting to setup up a gpio hog, device probing would repeatedly
fail with -EPROBE_DEFERED errors. It was caused by a circular dependency
between the gpio and pinctrl frameworks. If the gpio-ranges property is
present in device tree, then the gpio framework will handle the gpio pin
registrat
This patch set adds USB OTG support for the LG Nexus 5 (hammerhead)
phone.
Changes in v2:
- Reworked patches to use gpio hogging as suggested in the bq24190
device tree documentation.
- bq24190_charger: changed to use a switch instead of an if as requested
by Sebastian Reichel.
- bq24190_charg
On Wed, Oct 31, 2018 at 02:33:24PM +0100, Linus Walleij wrote:
> On Thu, Oct 25, 2018 at 11:04 PM Nathan Chancellor
> wrote:
>
> > In my opinion, there are enough of these warnings to warrant changing
> > the type of param globally (arm64 allyesconfig):
>
> Yeah as it is from the compiler, sure
On 31/10/18 23:10, Douglas Gilbert wrote:
> On 2018-10-31 4:57 p.m., Boaz Harrosh wrote:
>> On 30/10/18 09:45, Christoph Hellwig wrote:
>>> On Mon, Oct 29, 2018 at 02:42:12PM -0600, Jens Axboe wrote:
LGTM, for both:
>>>
>>> I also have this one on top as requested by Martin. The core block
>>
On 31-10-18, Pierre-Louis Bossart wrote:
>
> > Just thought it worth mentioning, this new patch that fixes sound
> > again, seems to have ressurected an old issue with PLL unlock. I'm
> > seeing journal entries after fresh boot ..
> >
> > ```
> > picard kernel: max98090 i2c-193C9890:00: PLL
Hi,
On Tue, Oct 30, 2018 at 10:23 AM Raju P.L.S.S.S.N
wrote:
>
> Add device bindings for cpuidle states for cpu devices.
>
> Cc:
> Signed-off-by: Raju P.L.S.S.S.N
> ---
> Changes in v2
> - Address comments from Doug
> ---
> ---
> arch/arm64/boot/dts/qcom/sdm845.dtsi | 62
> ++
From: Eric Dumazet
[ Upstream commit 4c16128b6271e70c8743178e90cccee147858503 ]
At least UDP / TCP stacks can now cook skbs with a tstamp using
MONOTONIC base (or arbitrary values with SCM_TXTIME)
Since loopback driver does not call (directly or indirectly)
skb_scrub_packet(), we need to clear
From: Omar Sandoval
[ Upstream commit 71327f547ee3a46ec5c39fdbbd268401b2578d0e ]
Move queue allocation next to disk allocation to fix a couple of issues:
- If add_disk() hasn't been called, we should clear disk->queue before
calling put_disk().
- If we fail to allocate a request queue, we sti
From: Waiman Long
[ Upstream commit 9506a7425b094d2f1d9c877ed5a78f416669269b ]
It was found that when debug_locks was turned off because of a problem
found by the lockdep code, the system performance could drop quite
significantly when the lock_stat code was also configured into the
kernel. For
From: Omar Sandoval
[ Upstream commit 1448a2a5360ae06f25e2edc61ae070dff5c0beb4 ]
If we fail to allocate the request queue for a disk, we still need to
free that disk, not just the previous ones. Additionally, we need to
cleanup the previous request queues.
Signed-off-by: Omar Sandoval
Signed-o
From: Ryan C Goodfellow
[ Upstream commit 5948185b97fa1f83d7855e638a72982a1073ebf5 ]
This commit makes it possible to use devlink to split the 100G CXP
Netronome into two 40G interfaces. Currently when you ask for 2
interfaces, the math in src/nfp_devlink.c:nfp_devlink_port_split
calculates that
From: Haiyang Zhang
[ Upstream commit 005479556197f80139771960dda0dfdcd2d2aad5 ]
The VF device's serial number is saved as a string in PCI slot's
kobj name, not the slot->number. This patch corrects the netvsc
driver, so the VF device can be successfully paired with synthetic
NIC.
Fixes: 00d7dd
From: Javier González
[ Upstream commit 44cdbdc657b23f75736eca3e88b781f009104363 ]
pblk exposes a sysfs interface that represents its internal state. Part
of this state is the map bitmap for the current open line, which should
be protected by the line lock to avoid a race when freeing the line
m
1 - 100 of 1021 matches
Mail list logo
