Declare Gx_charset[2] instead of G0_charset and G1_charset. It makes
the code simpler (without ternary operators).
Signed-off-by: Jiri Slaby
---
drivers/tty/vt/vt.c| 19 ---
include/linux/console_struct.h | 6 ++
2 files changed, 10 insertions(+), 15 deletions(-)
On Mon, Jun 15, 2020 at 09:15:40AM +0200, Krzysztof Kozlowski wrote:
> On Sun, Jun 14, 2020 at 06:48:04PM +0300, Vladimir Oltean wrote:
> > On Sun, 14 Jun 2020 at 13:57, Krzysztof Kozlowski wrote:
> > >
> > > If interrupt comes late, during probe error path or device remove (could
> > > be trigger
We continue cleaning up do_con_write. This (hopefully) makes the
inversion code obvious.
Signed-off-by: Jiri Slaby
---
drivers/tty/vt/vt.c | 24
1 file changed, 16 insertions(+), 8 deletions(-)
diff --git a/drivers/tty/vt/vt.c b/drivers/tty/vt/vt.c
index 5004242d601b..b
vc_translate is used only in vt.c, so move the definition from a header
there. Also, it used to be a macro, so be modern and make a static
inline from it. This makes the code actually readable.
And as a preparation for next patches, rename it to vc_translate_ascii.
vc_translate will be a wrapper f
Use bools for rescan and inverse. And true/false accordingly.
Use u8 for width instead of uint8_t.
Signed-off-by: Jiri Slaby
---
drivers/tty/vt/vt.c | 18 +-
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/drivers/tty/vt/vt.c b/drivers/tty/vt/vt.c
index b86639351dd
Now that we reordered the code and the label, we can eliminate the
translation into a separate function. We call it vc_translate here.
Signed-off-by: Jiri Slaby
---
drivers/tty/vt/vt.c | 26 --
1 file changed, 16 insertions(+), 10 deletions(-)
diff --git a/drivers/tty/vt
vc_tab_stop is used as a bitmap, but defined as an unsigned int array.
Switch it to bitmap and convert all users to the bitmap interface.
Note the difference in behavior! We no longer mask the top 24 bits away
from x, hence we do not wrap tabs at 256th column. Instead, we silently
drop attempts to
On Fri, Jun 12, 2020 at 05:41:21PM -0700, Fenghua Yu wrote:
> This series only provides simple and basic support for ENQCMD and the MSR:
> 1. Clean up type definitions (patch 1-3). These patches can be in a
>separate series.
>- Define "pasid" as "unsigned int" consistently (patch 1 and 2).
On 6/12/2020 11:19 PM, Vincent Guittot wrote:
Le vendredi 12 juin 2020 à 14:36:49 (+0800), Xing Zhengjun a écrit :
Hi Vincent,
We test the regression still existed in v5.7, do you have time to look at
it? Thanks.
The commit 070f5e860ee2 moveis some cases from the state "group has spar
On Sat, Jun 13, 2020 at 9:12 PM Mike Kravetz wrote:
>
> On 6/12/20 11:53 PM, Amir Goldstein wrote:
> As a hugetlbfs developer, I do not know of a use case for interoperability
> with overlayfs. So yes, I am not too interested in making them work well
> together. However, if there was an actual
On Fri, Jun 12, 2020 at 05:41:33PM -0700, Fenghua Yu wrote:
> @@ -447,6 +458,18 @@ dotraplinkage void do_general_protection(struct pt_regs
> *regs, long error_code)
> int ret;
>
> RCU_LOCKDEP_WARN(!rcu_is_watching(), "entry code didn't wake RCU");
> +
> + /*
> + * Perform th
Enable modular build of prime numbers and bitops test modules.
Signed-off-by: Geert Uytterhoeven
---
arch/m68k/configs/amiga_defconfig| 2 ++
arch/m68k/configs/apollo_defconfig | 2 ++
arch/m68k/configs/atari_defconfig| 2 ++
arch/m68k/configs/bvme6000_defconfig | 2 ++
arch/m68k/confi
On Fri, Jun 12, 2020 at 05:41:33PM -0700, Fenghua Yu wrote:
> +/*
> + * Apply some heuristics to see if the #GP fault was caused by a thread
> + * that hasn't had the IA32_PASID MSR initialized. If it looks like that
> + * is the problem, try initializing the IA32_PASID MSR. If the heuristic
> + *
On Sun, Jun 14, 2020 at 10:03 AM Dmitry Vyukov wrote:
> On Tue, Mar 10, 2020 at 9:10 AM Dmitry Vyukov wrote:
> > On Tue, Mar 10, 2020 at 7:15 AM Nathan Chancellor
> > wrote:
> > >
> > > On Mon, Mar 09, 2020 at 09:20:58AM +0100, Dmitry Vyukov wrote:
> > > > On Sun, Mar 8, 2020 at 7:35 PM 'Jann Ho
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: b3a9e3b9622ae10064826dccb4f7a52bd88c7407
commit: afe956c577b2d5a3d9834e4424587c1ebcf90c4c kbuild: Enable
-Wtautological-compare
date: 10 weeks ago
:: branch date: 2 hours ago
:: commit date: 10 wee
On Sun, 14 Jun 2020 19:10:05 +0200 Sebastian Andrzej Siewior
wrote:
> On 2020-06-14 14:12:18 [+0200], Stephen Berman wrote:
[...]
>> What am I supposed to do after "echo t > /proc/sysrq-trigger"? Both
>> before and after doing that I get an error trying to open the file:
>>
>> root [ ~ ]# cat
Move away from the deprecated API and return the shiny new ERRPTR where
useful.
Signed-off-by: Wolfram Sang
Reviewed-by: Andy Shevchenko
---
I'd like to push it via I2C for 5.8-rc2.
arch/x86/platform/intel-mid/sfi.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/
Move away from the deprecated API and return the shiny new ERRPTR where
useful.
Signed-off-by: Wolfram Sang
Reviewed-by: Daniel Thompson
---
I'd like to push it via I2C for 5.8-rc2.
drivers/video/backlight/tosa_lcd.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/driv
All in-tree users have been converted to the new i2c_new_client_device
function, so remove this deprecated one.
Signed-off-by: Wolfram Sang
---
I'd like to push it via I2C for 5.8-rc2.
drivers/i2c/i2c-core-base.c | 25 -
include/linux/i2c.h | 8 +++-
2 file
i2c_new_client() is deprecated, use the replacement
i2c_new_client_device(). Also, we have a helper to check if a driver is
bound. Use it to simplify the code. Note that this changes the errno for
a failed device creation from ENOMEM to ENODEV. No callers currently
interpret this errno, though, so
I want to remove the above API this cycle, and just a few patches have
not made it into 5.8-rc1. They have been reviewed and most had been
promised to get into linux-next, but well, things happen. So, I hope it
is okay for everyone to collect them like this and push them via I2C for
5.8-rc2.
One m
Move away from the deprecated API and advertise the new one.
Signed-off-by: Wolfram Sang
Cc: Mauro Carvalho Chehab
---
I'd like to push it via I2C for 5.8-rc2.
Documentation/driver-api/media/v4l2-subdev.rst| 2 +-
Documentation/userspace-api/media/conf_nitpick.py | 2 +-
2 files changed,
Fix typo: "triger" --> "trigger"
Signed-off-by: Flavio Suligoi
Acked-by: Guo Ren
---
v1: add Acked-by: Guo Ren
Documentation/devicetree/bindings/gpio/mediatek,mt7621-gpio.txt | 2 +-
.../devicetree/bindings/interrupt-controller/csky,mpintc.txt| 2 +-
Documentation/devicetree/bindings/tim
module_put() balances try_module_get(), not request_module(). Fix the
error path to match that.
Fixes: 2066facca4c7 ("drm/kms: slave encoder interface.")
Signed-off-by: Wolfram Sang
Reviewed-by: Emil Velikov
---
I'd like to push it via I2C for 5.8-rc2.
drivers/gpu/drm/drm_encoder_slave.c | 5
The cursor code used to use magic constants, ANDs, ORs, and some macros.
Redefine all this to make some sense.
In particular:
* Drop CUR_DEFAULT, which is CUR_UNDERLINE. CUR_DEFAULT was used only
for cur_default variable initialization, so use CUR_UNDERLINE there to
make obvious what's the def
bcm63xx-spi controller is present on several BMIPS SoCs (BCM6358, BCM6362,
BCM6368 and BCM63268).
Signed-off-by: Álvaro Fernández Rojas
---
drivers/spi/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/spi/Kconfig b/drivers/spi/Kconfig
index 8f1f8fca79e3..a9896e
bcm63xx arch resets the SPI controller at early boot. However, bmips arch
needs to perform a reset when probing the driver.
Signed-off-by: Álvaro Fernández Rojas
---
drivers/spi/spi-bcm63xx.c | 17 +
1 file changed, 17 insertions(+)
diff --git a/drivers/spi/spi-bcm63xx.c b/drive
BCM63xx SPI and HSSPI controller are present on several BMIPS SoCs (BCM6318,
BCM6328, BCM6358, BCM6362, BCM6368 and BCM63268).
Álvaro Fernández Rojas (4):
spi: bcm63xx-spi: add reset support
spi: bcm63xx-spi: allow building for BMIPS
spi: bcm63xx-hsspi: add reset support
spi: bcm63xx-hsspi
bcm63xx arch resets the HSSPI controller at early boot. However, bmips arch
needs to perform a reset when probing the driver.
Signed-off-by: Álvaro Fernández Rojas
---
drivers/spi/spi-bcm63xx-hsspi.c | 17 +
1 file changed, 17 insertions(+)
diff --git a/drivers/spi/spi-bcm63xx-h
bcm63xx-hsspi controller is present on several BMIPS SoCs (BCM6318, BCM6328,
BCM6362 and BCM63268).
Signed-off-by: Álvaro Fernández Rojas
---
drivers/spi/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/spi/Kconfig b/drivers/spi/Kconfig
index a9896e388355..5007
Hi Yamada-san,
On Sat, 13 Jun 2020, Linux Kernel Mailing List wrote:
Commit: a7f7f6248d9740d710fd6bd190293fe5e16410ac
Parent: e4a42c82e943b97ce124539fcd7a47445b43fa0d
Refname:refs/heads/master
Web:
https://git.kernel.org/torvalds/c/a7f7f6248d9740d710fd6bd190293fe5e164
pon., 15 cze 2020 o 08:47 Mauro Carvalho Chehab
napisał(a):
>
> There is one parameter with a wrong name at kernel-doc macro:
>
> ./include/linux/gpio/driver.h:499: warning: Function parameter or member 'gc'
> not described in 'gpiochip_add_data'
> ./include/linux/gpio/driver.h:499: warning: Exce
sob., 13 cze 2020 o 16:44 Jan Kiszka napisał(a):
>
> From: Jan Kiszka
>
> The PCAL9535 [1] is compatible to the PCA9535. Additionally, it comes
> with interrupt support and input latching. Other features are not
> supported by the GPIO subsystem.
>
> [1] https://www.nxp.com/docs/en/data-sheet/PCA
On Mon, Jun 15, 2020 at 03:43:09PM +0800, Jason Yan wrote:
>
>
> 在 2020/6/15 15:25, Gao Xiang 写道:
> > Hi Jason,
> >
> > On Mon, Jun 15, 2020 at 12:01:41PM +0800, Jason Yan wrote:
> > > This is an effort to eliminate the uninitialized_var() macro[1].
> > >
> > > The use of this macro is the wron
If interrupt comes late, during probe error path or device remove (could
be triggered with CONFIG_DEBUG_SHIRQ), the interrupt handler
dspi_interrupt() will access registers with the clock being disabled. This
leads to external abort on non-linefetch on Toradex Colibri VF50 module
(with Vybrid VF5x
pt., 12 cze 2020 o 10:05 Wang Qing napisał(a):
>
> Use kobj_to_dev() API instead of container_of().
>
> Signed-off-by: Wang Qing
> ---
> drivers/gpio/gpiolib-sysfs.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
> mode change 100644 => 100755 drivers/gpio/gpiolib-sysfs.c
>
> diff --gi
The interrupt handler calls completion and is IRQ requested before the
completion is initialized. Logically it should be the other way.
Fixes: 4f5ee75ea171 ("spi: spi-fsl-dspi: Replace interruptible wait queue with
a simple completion")
Cc:
Signed-off-by: Krzysztof Kozlowski
---
Changes sinc
Testing events during freeing of disabled shared interrupts
(CONFIG_DEBUG_SHIRQ) leads to false positives. The driver disabled
interrupts on purpose to be sure that they will not fire during device
removal.
Signed-off-by: Krzysztof Kozlowski
---
Changes since v1:
1. New patch.
---
kernel/irq/
If scsi_host_lookup() failes we will jump to put_host, which may
cause panic. Jump to exit_set_fnode to fix it.
Signed-off-by: Jing Xiangfeng
---
drivers/scsi/scsi_transport_iscsi.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/scsi/scsi_transport_iscsi.c
b/drivers
Hi Xing,
Le lundi 15 juin 2020 à 15:26:59 (+0800), Xing Zhengjun a écrit :
>
>
> On 6/12/2020 7:06 PM, Hillf Danton wrote:
> >
> > On Fri, 12 Jun 2020 14:36:49 +0800 Xing Zhengjun wrote:
...
> > --- a/kernel/sched/fair.c
> > +++ b/kernel/sched/fair.c
> > @@ -8215,12 +8215,8 @@ group_has_capac
On Fri 12-06-20 23:34:16, Amir Goldstein wrote:
> > > > So maybe it would be better to list all users of alloc_file_pseudo()
> > > > and say that they all should be opted out of fsnotify, without
> > > > mentioning
> > > > "internal mount"?
> > > >
> > >
> > > The users are DMA buffers, CXL, aio,
Hi Diego,
On Thu, May 28, 2020 at 10:47:11PM +0200, Diego Rondini wrote:
> Enable support for USB OTG port on Orange Pi Zero Plus 2 (both H3 and H5
> variants). As, according to the board schematics, the USB OTG port cannot
> provide power to external devices, we set dr_mode to peripheral.
>
> Si
Hi Álvaro,
On Mon, 2020-06-15 at 10:03 +0200, Álvaro Fernández Rojas wrote:
> bcm63xx arch resets the SPI controller at early boot. However, bmips arch
> needs to perform a reset when probing the driver.
>
> Signed-off-by: Álvaro Fernández Rojas
> ---
> drivers/spi/spi-bcm63xx.c | 17 ++
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: b3a9e3b9622ae10064826dccb4f7a52bd88c7407
commit: 113d4bc9048336ba7c3d2ad972dbad4aef6e148a objtool: Fix clang switch
table edge case
date: 4 months ago
config: x86_64-randconfig-m001-20200615 (attached as
On 6/15/2020 1:18 PM, Tao Zhou wrote:
Hi,
On Fri, Jun 12, 2020 at 03:59:31PM +0800, Xing Zhengjun wrote:
Hi,
I test the regression, it still existed in v5.7. If you have any fix
for it, please send it to me, I can verify it. Thanks.
When busiest group is group_fully_busy and local gr
On Thu, May 28, 2020 at 10:47:12PM +0200, Diego Rondini wrote:
> Add pwr and status leds configuration and turn on pwr led by default for
> Orange
> Pi Zero Plus 2 (both H3 and H5 variants).
>
> Signed-off-by: Diego Rondini
> ---
> .../boot/dts/sun8i-h3-orangepi-zero-plus2.dts| 16 +
czw., 11 cze 2020 o 12:43 Hui Song napisał(a):
>
> From: Song Hui
>
> Delete the interrupt IRQF_NO_THREAD flags in order to gpio interrupts
> can be threaded to allow high-priority processes to preempt.
>
> Signed-off-by: Song Hui
> ---
> drivers/gpio/gpio-mpc8xxx.c | 2 +-
> 1 file changed, 1
wt., 9 cze 2020 o 14:46 Kieran Bingham
napisał(a):
>
> The word 'descriptor' is misspelled throughout the tree.
>
> Fix it up accordingly:
> decriptors -> descriptors
>
> Signed-off-by: Kieran Bingham
> ---
> drivers/gpio/TODO | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff
On 6/15/20 10:07 AM, Krzysztof Kozlowski wrote:
> If interrupt comes late, during probe error path or device remove (could
> be triggered with CONFIG_DEBUG_SHIRQ), the interrupt handler
> dspi_interrupt() will access registers with the clock being disabled. This
> leads to external abort on non-li
On Sat, Jun 13, 2020 at 8:53 AM Amir Goldstein wrote:
> > I also looked at normal filesystem lower and hugetlbfs upper. Yes,
> > overlayfs
> > allows this. This is somewhat 'interesting' as write() is not supported in
> > hugetlbfs. Writing to files in the overlay actually ended up writing to
On 2020/6/15 12:02, Jason Yan wrote:
> This is an effort to eliminate the uninitialized_var() macro[1].
>
> The use of this macro is the wrong solution because it forces off ANY
> analysis by the compiler for a given variable. It even masks "unused
> variable" warnings.
>
> Quoted from Linus[2]:
FIX_EARLY_DEBUG_BASE reserves a 128k area for debuging.
When page size is 256k, the calculation results in a 0 number of
pages, leading to the following failure:
CC arch/powerpc/kernel/asm-offsets.s
In file included from ./arch/powerpc/include/asm/nohash/32/pgtable.h:77:0,
From: Colin Ian King
There is a spelling mistake in a couple of kvm_err messages. Fix them.
Signed-off-by: Colin Ian King
---
arch/mips/kvm/emulate.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/mips/kvm/emulate.c b/arch/mips/kvm/emulate.c
index 5ae82d925197..d3
From: Christian Brauner
> Sent: 12 June 2020 19:28
...
> > > if (size < 32)
> > > return -EINVAL;
> > > if (size > PAGE_SIZE)
> > > return -E2BIG;
> >
> > (Tanget: what was the reason for copy_struct_from_user() not including
> > the min/max check? I have a memory of Al obje
On Mon, Jun 15, 2020 at 08:46:52AM +0200, Mauro Carvalho Chehab wrote:
> There are some new broken doc links due to yaml renames
> at DT. Developers should really run:
>
> ./scripts/documentation-file-ref-check
>
> in order to solve those issues while submitting patches.
> This tool can eve
From: Colin Ian King
There is a spelling mistake in a comment. Fix it.
Signed-off-by: Colin Ian King
---
drivers/net/ethernet/xilinx/xilinx_axienet.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/ethernet/xilinx/xilinx_axienet.h
b/drivers/net/ethernet/xilinx/
On 2020/6/15 16:07, Gao Xiang wrote:
> On Mon, Jun 15, 2020 at 03:43:09PM +0800, Jason Yan wrote:
>>
>>
>> 鍦?2020/6/15 15:25, Gao Xiang 鍐欓亾:
>>> Hi Jason,
>>>
>>> On Mon, Jun 15, 2020 at 12:01:41PM +0800, Jason Yan wrote:
This is an effort to eliminate the uninitialized_var() macro[1].
>>
Hello.
On Mon, Jun 01, 2020 at 12:48:22PM -0700, Nitin Gupta wrote:
> For some applications, we need to allocate almost all memory as
> hugepages. However, on a running system, higher-order allocations can
> fail if the memory is fragmented. Linux kernel currently does on-demand
> compaction as we
(reduced the spam list)
On Mon, Jun 15, 2020 at 05:17:28PM +1000, Greg Ungerer wrote:
> Hi Mike,
>
> On 15/6/20 4:22 pm, Mike Rapoport wrote:
> > On Mon, Jun 15, 2020 at 01:53:42PM +1000, Greg Ungerer wrote:
> > > From: Mike Rapoport
> > > > Currently, architectures that use free_area_init() to
On Tue, Jun 09, 2020 at 02:43:13PM -0300, Thadeu Lima de Souza Cascardo wrote:
> When SRBDS is mitigated by TSX OFF, update_srbds_msr will still read and
Are you talking about this case in srbds_select_mitigation():
if ((ia32_cap & ARCH_CAP_MDS_NO) && !boot_cpu_has(X86_FEATURE_RTM))
> fix some memleaks in parse_events_term__sym_hw and parse_events_term__clone.
Can it be more appropriate to refer to the term “memory leak” in consistent
ways?
> v1 ==> v2
> 1. split into two patches
Corresponding development consequences can become more interesting.
> v2 ==> v3
> add more
On Sat, Jun 13, 2020 at 04:40:30PM -0700, Paul E. McKenney wrote:
> So Peter's patch is fully in the clear:
>
> Tested-by: Paul E. McKenney
Awesome!, now I get to explain how the lack of that leads to the
observed NULL pointer :-)
We have defined MPTCP_PM_ADDR_MAX in pm_netlink.c, so drop this duplicate macro.
Fixes: 1b1c7a0ef7f3 ("mptcp: Add path manager interface")
Signed-off-by: Geliang Tang
---
Changes in v2:
- change Subject from "mptcp: unify MPTCP_PM_MAX_ADDR and MPTCP_PM_ADDR_MAX"
---
net/mptcp/protocol.h | 2 -
From: Bolarinwa Olayemi Saheed
The PCIe capability accessors can return 0, -EINVAL, or any PCIBIOS_ error
code. PCIBIOS_ error codes have positive values. The PCI accessor on the
other hand can only return 0 or any PCIBIOS_ error code. This
inconsistency among these accessor makes it harder for c
From: Bolarinwa Olayemi Saheed
PATCH 1/8 to 7/8:
PCIBIOS_ error codes have positive values and they are passed down the
call heirarchy from accessors. For functions which are meant to return
only a negative value on failure, passing on this value is a bug.
To mitigate this, call pcibios_err_to_e
From: Bolarinwa Olayemi Saheed
pci_enable_pcie_error_reporting() return PCIBIOS_ error codes which were
passed on down the call heirarchy from PCIe capability accessors.
PCIBIOS_ error codes have positive values. Passing on these values is
inconsistent with functions which return only a negative
From: Bolarinwa Olayemi Saheed
pci_disable_pcie_error_reporting() returns PCIBIOS_ error code which were
passed down the call heirarchy from PCIe capability accessors.
PCIBIOS_ error codes have positive values. Passing on these values is
inconsistent with functions which return only a negative v
From: Bolarinwa Olayemi Saheed
restore_pci_variables() and save_pci_variables() return PCIBIOS_ error
codes from PCIe capability accessors.
PCIBIOS_ error codes have positive values. Passing on these values is
inconsistent with functions which return only a negative value on failure.
Before pas
From: Bolarinwa Olayemi Saheed
ioat3_dma_probe() returns PCIBIOS_ error codes from PCIe capability
accessors.
PCIBIOS_ error codes have positive values. Passing on these values is
inconsistent with functions which return only a negative value on failure.
Before passing on the return value of PC
From: Bolarinwa Olayemi Saheed
pqi_set_pcie_completion_timeout() return PCIBIOS_ error codes which were
passed on down the call heirarchy from PCIe capability accessors.
PCIBIOS_ error codes have positive values. Passing on these values is
inconsistent with functions which return only a negative
From: Bolarinwa Olayemi Saheed
Both pcie_set_readrq() and pcie_set_readrq() return PCIBIOS_ error codes
which were passed down the call heirarchy from PCIe capability accessors.
PCIBIOS_ error codes have positive values. Passing on these values is
inconsistent with functions which return only a
From: Bolarinwa Olayemi Saheed
pcie_speeds() returns PCIBIOS_ error codes from PCIe capability accessors.
PCIBIOS_ error codes have positive values. Passing on these values is
inconsistent with functions which return only a negative value on failure.
Before passing on the return value of PCIe c
On Mon, Jun 15, 2020 at 09:32:41AM +0200, Jann Horn wrote:
> On Thu, Jun 11, 2020 at 10:24 PM Linus Torvalds
> wrote:
> >
> > On Wed, Jun 10, 2020 at 9:05 PM kernel test robot
> > wrote:
> > >
> > > FYI, we noticed a 2158.6% improvement of stress-ng.vm-splice.ops_per_sec
> > > due to commit:
>
> > On 2020/06/12 17:34, Sungjong Seo wrote:
> > >> remove EXFAT_SB_DIRTY flag and related codes.
> > >>
> > >> This flag is set/reset in exfat_put_super()/exfat_sync_fs() to
> > >> avoid sync_blockdev().
> > >> However ...
> > >> - exfat_put_super():
> > >> Before calling this, the VFS has already
On 15.06.20 03:01, Jianqun Xu wrote:
> In some case the cma area could not be activated, but the cma_alloc be
> used under this case, then the kernel will crash caused by NULL pointer
> dereference.
>
> Add bitmap valid check in cma_alloc to avoid this issue.
>
> Signed-off-by: Jianqun Xu
> ---
Dexuan Cui writes:
>> From: linux-hyperv-ow...@vger.kernel.org
>> On Behalf Of Andy Lutomirski
>> Sent: Tuesday, April 7, 2020 2:01 PM
>> To: Christoph Hellwig
>> Cc: vkuznets ; x...@kernel.org;
>> linux-hyp...@vger.kernel.org; linux-kernel@vger.kernel.org; KY Srinivasan
>> ; Stephen Hemminger
On 2020/6/15 15:47, Richard Palethorpe wrote:
> It is possible to cause a division error and use-after-free by querying the
> nmem device before the driver data is fully initialised in nvdimm_probe. E.g
> by doing
>
> (while true; do
> cat /sys/bus/nd/devices/nmem*/available_slots 2>&1 > /dev
Use list_first_entry_or_null to simplify the code.
Signed-off-by: Geliang Tang
---
Changes in v2:
- Add "net-next" tag in Subject.
---
net/mptcp/protocol.h | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/net/mptcp/protocol.h b/net/mptcp/protocol.h
index 70ed698bd206..d
Em Mon, 15 Jun 2020 09:58:14 +0200
Wolfram Sang escreveu:
> Move away from the deprecated API and advertise the new one.
>
> Signed-off-by: Wolfram Sang
> Cc: Mauro Carvalho Chehab
> ---
>
> I'd like to push it via I2C for 5.8-rc2.
OK!
Reviewed-by: Mauro Carvalho Chehab
>
> Documentatio
在 2020/6/15 16:26, Chao Yu 写道:
On 2020/6/15 12:02, Jason Yan wrote:
This is an effort to eliminate the uninitialized_var() macro[1].
The use of this macro is the wrong solution because it forces off ANY
analysis by the compiler for a given variable. It even masks "unused
variable" warnings.
Hi Thierry,
On Thu, May 7, 2020 at 10:04 PM Thierry Reding wrote:
> On Wed, May 06, 2020 at 02:32:36PM +0200, Geert Uytterhoeven wrote:
> > The Tegra EMC scaling support code is not a clock provider, but merely a
> > clock consumer, and thus does not need to include
> > .
> >
> > Fixes: ec37a9a17
The pllb_arm clock was created at probe time, but was never removed if
something went wrong later in probe, or if the driver was ever removed from
the system.
Now that we are using clk_hw_register(), we can just use its managed variant
to take care of that for us.
Cc: Michael Turquette
Cc: Steph
The driver has really only supported one clock so far and has hardcoded the
ID used in communications with the firmware in all the functions
implementing the clock framework hooks. Let's store that in the clock data
structure so that we can support more clocks later on.
Cc: Michael Turquette
Cc:
The firmware clocks driver was previously probed through a platform_device
created by the firmware driver.
Since we will now have a node for that clocks driver, we need to create the
device only in the case where there's no node for it already.
Reviewed-by: Nicolas Saenz Julienne
Tested-by: Nico
The raspberrypi_register_pllb has been returning an integer so far to
notify whether the functions has exited successfully or not.
However, the OF provider functions in the clock framework require access to
the clk_hw structure so that we can expose those clocks to device tree
consumers.
Since we
The pllb_arm_lookup pointer in the struct raspberrypi_clk is not used for
anything but to store the returned pointer to clkdev_hw_create, and is not
used anywhere else in the driver.
Let's remove that global pointer from the structure.
Cc: Michael Turquette
Cc: linux-...@vger.kernel.org
Acked-by
The PLLB rate will be changed through the firmware clocks drivers and will
change behind this drivers' back, so we don't want to cache the rate.
Acked-by: Nicolas Saenz Julienne
Tested-by: Nicolas Saenz Julienne
Signed-off-by: Maxime Ripard
---
drivers/clk/bcm/clk-bcm2835.c | 5 +++--
1 file c
Now that we have a clock driver for the clocks exposed by the firmware,
let's add the device tree nodes for it.
Tested-by: Nicolas Saenz Julienne
Signed-off-by: Maxime Ripard
---
arch/arm/boot/dts/bcm2711-rpi-4-b.dts | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm/boot/dts/bcm
The pllb_arm clock is defined as a fixed factor clock with the pllb
clock as a parent. However, all its configuration is entirely static,
and thus we don't really need to call clk_hw_register_fixed_factor() but
can simply call clk_hw_register() with a static clk_fixed_factor
structure.
Cc: Michael
So far the driver has really only been providing a single clock, and stored
both the data associated to that clock in particular with the data
associated to the "controller".
Since we will change that in the future, let's decouple the clock data from
the provider data.
Cc: Michael Turquette
Cc:
Hi,
Since the whole DRM/HDMI support began to grow fairly big, I've chosen
to split away the two discussions between the firmware clocks and the
HDMI support.
Let me know what you think,
Maxime
Cc: bcm-kernel-feedback-l...@broadcom.com
Cc: devicet...@vger.kernel.org
Cc: Kamal Dasu
Cc: linux-...
The CPU clock has had so far a bunch of quirks to expose the clock tree
properly, but since we reverted to exposing them through the MMIO driver,
we can remove that code from the firmware driver.
Acked-by: Nicolas Saenz Julienne
Tested-by: Nicolas Saenz Julienne
Signed-off-by: Maxime Ripard
---
While some clock types allow for each clock to specify its own custom
flags, the PLLs can't. We will need this for the PLLB, so let's add it.
Acked-by: Nicolas Saenz Julienne
Tested-by: Nicolas Saenz Julienne
Signed-off-by: Maxime Ripard
---
drivers/clk/bcm/clk-bcm2835.c | 3 ++-
1 file change
The raspberrypi firmware clock driver has a min_rate / max_rate clamping by
storing the info it needs in a private structure.
However, the CCF already provides such a facility, so we can switch to it
to remove the boilerplate.
Reviewed-by: Nicolas Saenz Julienne
Tested-by: Nicolas Saenz Julienne
Since we don't care about retrieving the clk_lookup structure pointer
returned by clkdev_hw_create, we can just use the clk_hw_register_clkdev
function.
Cc: Michael Turquette
Cc: linux-...@vger.kernel.org
Acked-by: Nicolas Saenz Julienne
Reviewed-by: Stephen Boyd
Tested-by: Nicolas Saenz Julien
The clkdev lookup created for the cpufreq device is never removed if
there's an issue later in probe or at module removal time.
Let's convert to the managed variant of the clk_hw_register_clkdev function
to make sure it happens.
Cc: Michael Turquette
Cc: linux-...@vger.kernel.org
Acked-by: Nicol
This reverts commit 2256d89333bd17b8b56b42734a7e1046d52f7fc3. Since we
will be expanding the firmware clock driver, we'll need to remove the
quirks to deal with the PLLB. However, we still want to expose the clock
tree properly, so having that clock in the MMIO driver will allow that.
Acked-by: Ni
For the upcoming registration of the clocks provided by the firmware, make
sure it's exposed to the device tree providers.
Cc: Michael Turquette
Cc: linux-...@vger.kernel.org
Acked-by: Nicolas Saenz Julienne
Reviewed-by: Stephen Boyd
Tested-by: Nicolas Saenz Julienne
Signed-off-by: Maxime Ripa
From: Jan Kiszka
The PCAL9535 [1] is compatible to the PCA9535. Additionally, it comes
with interrupt support and input latching. Other features are not
supported by the GPIO subsystem.
[1] https://www.nxp.com/docs/en/data-sheet/PCAL9535A.pdf
Signed-off-by: Jan Kiszka
---
drivers/gpio/gpio-pc
The current firmware clock driver for the RaspberryPi can only be probed by
manually registering an associated platform_device.
While this works fine for cpufreq where the device gets attached a clkdev
lookup, it would be tedious to maintain a table of all the devices using
one of the clocks expos
101 - 200 of 1505 matches
Mail list logo
