[PATCH] lib: scatterlist: Fix to support no mapped sg

In function sg_split, the second sg_calculate_split will return -EINVAL when in_mapped_nents is 0. Indeed there is no need to do second sg_calculate_split and sg_split_mapped when in_mapped_nents is 0, as in_mapped_nents indicates no mapped entry in original sgl. Signed-off-by: Zhou Wang --- li

[PATCH 2/7] rtc: jz4740: switch to rtc_time64_to_tm/rtc_tm_to_time64

Call the 64bit versions of rtc_tm time conversion now that the range is enforced by the core. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-jz4740.c | 8 +++- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/drivers/rtc/rtc-jz4740.c b/drivers/rtc/rtc-jz4740.c index 079469

[PATCH 7/7] rtc: jz4740: convert to SPDX identifier

Use SPDX-License-Identifier instead of a verbose license text. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-jz4740.c | 11 +-- 1 file changed, 1 insertion(+), 10 deletions(-) diff --git a/drivers/rtc/rtc-jz4740.c b/drivers/rtc/rtc-jz4740.c index c9e16d857fa8..0e95282df525 100644

[PATCH 5/7] rtc: jz4740: use dev_pm_set_wake_irq() to simplify code

Use dev_pm_set_wake_irq() to set the RTC as a wakeup source for suspend. This allows to remove the whole dev_pm_ops structure. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-jz4740.c | 37 +++-- 1 file changed, 7 insertions(+), 30 deletions(-) diff --git a/

[PATCH 3/7] rtc: jz4740: remove useless check

rtc_time64_to_tm always returns a valid tm, it is not necessary to validate it. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-jz4740.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/rtc/rtc-jz4740.c b/drivers/rtc/rtc-jz4740.c index 15b6832f3931..a7e1a382cac5 1

[PATCH 4/7] rtc: jz4740: use .set_time

Use .set_time instead of the deprecated .set_mmss. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-jz4740.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/rtc/rtc-jz4740.c b/drivers/rtc/rtc-jz4740.c index a7e1a382cac5..91ccb45bb886 100644 --- a/drivers/rtc

[PATCH 6/7] rtc: jz4740: rework invalid time detection

The scratchpad register is used to detect an invalid time when power to the RTC has been lost. Instead of deleting that precious information and set the time to the UNIX epoch, forward it to userspace. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-jz4740.c | 21 + 1 fi

[PATCH 1/7] rtc: jz4740: set range

RTC_SEC is a 32-bit seconds counter. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-jz4740.c | 12 ++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/drivers/rtc/rtc-jz4740.c b/drivers/rtc/rtc-jz4740.c index d0a891777f44..079469627bd7 100644 --- a/drivers/rtc/rtc-j

Re: [RFC PATCH v4 4/4] x86/acrn: Add hypercall for ACRN guest

On Mon, Apr 15, 2019 at 10:00:57AM +0800, Zhao Yakui wrote: > When ACRN hypervisor is detected, the hypercall is needed so that the > ACRN guest can query/config some settings. For example: it can be used > to query the resources in hypervisor and manage the CPU/memory/device/ > interrupt for guest

Re: [PATCH V2 1/3] Calculate Thermal Pressure

On Tuesday 16 Apr 2019 at 15:38:39 (-0400), Thara Gopinath wrote: > +/** > + * Function to update thermal pressure from cooling device > + * or any framework responsible for capping cpu maximum > + * capacity. > + */ > +void sched_update_thermal_pressure(struct cpumask *cpus, > +

[PATCH] char/ipmi: fix spelling mistake "receieved_messages" -> "received_messages"

From: Colin Ian King There is a spelling mistake in the documentation. Fix it. Signed-off-by: Colin Ian King --- Documentation/ABI/testing/sysfs-devices-platform-ipmi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/ABI/testing/sysfs-devices-platform-ipmi b/Do

Re: [PATCH V2 3/3] regulator: slg51000: add slg51000 regulator driver

On Thu, Apr 18, 2019 at 03:09:44PM +0900, Eric Jeong wrote: > I updated regulator_ops structure to use use the helper function > which is regulator_is_enabled_regmap() instead reading status bits > for is_enabled() operation. > v2: use regulator helper function for is_enabled() There's also the

[PATCH v2 2/5] clone: add CLONE_PIDFD

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. Linus originally suggested to implement this as a new flag to clone() instead of making it a separate system call. As spotted by Linus, there

[PATCH v2 4/5] signal: support CLONE_PIDFD with pidfd_send_signal

Let pidfd_send_signal() use pidfds retrieved via CLONE_PIDFD. With this patch pidfd_send_signal() becomes independent of procfs. This fullfils the request made when we merged the pidfd_send_signal() patchset. The pidfd_send_signal() syscall is now always available allowing for it to be used by user

[PATCH v2 3/5] signal: use fdget() since we don't allow O_PATH

As stated in the original commit for pidfd_send_signal() we don't allow to signal processes through O_PATH file descriptors since it is semantically equivalent to a write on the pidfd. We already correctly error out right now and return EBADF if an O_PATH fd is passed. This is because we use file->

[PATCH v2 0/5] clone: add CLONE_PIDFD

Hey, /* v2 summary */ Move put_user() into copy process before clone's point of no return so that we can handle put_user() errors as suggested by Oleg. The good news is that this again allows us to make the patch smaller. /* v1 summary */ As suggested by Oleg, have pidfds returned in the fourth a

[PATCH v2 1/5] Make anon_inodes unconditional

From: David Howells Make the anon_inodes facility unconditional so that it can be used by core VFS code and pidfd code. Signed-off-by: David Howells Signed-off-by: Al Viro [christ...@brauner.io: adapt commit message to mention pidfds] Signed-off-by: Christian Brauner --- /* changelog */ v1: p

[PATCH v2 5/5] samples: show race-free pidfd metadata access

This is a sample program showing userspace how to get race-free access to process metadata from a pidfd. It is rather easy to do and userspace can actually simply reuse code that currently parses a process's status file in procfs. The program can easily be extended into a generic helper suitable fo

Re: Linux Testing Microconference at LPC

Hi, On Thursday, April 11, 2019 14:37 -03, Dhaval Giani wrote: > Hi Folks, > > This is a call for participation for the Linux Testing microconference > at LPC this year. > > For those who were at LPC last year, as the closing panel mentioned, > testing is probably the next big push needed

Applied "ASoC: sprd: Add reserved DMA memory support" to the asoc tree

The patch ASoC: sprd: Add reserved DMA memory support has been applied to the asoc tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-5.2 All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and se

Applied "MAINTAINERS: slg51000 updates to the Dialog Semiconductor search terms" to the regulator tree

The patch MAINTAINERS: slg51000 updates to the Dialog Semiconductor search terms has been applied to the regulator tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-5.2 All being well this means that it will be integrated into the linux-next tree (usually s

Applied "dt-bindings: regulator: add document bindings for slg51000" to the regulator tree

The patch dt-bindings: regulator: add document bindings for slg51000 has been applied to the regulator tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-5.2 All being well this means that it will be integrated into the linux-next tree (usually sometime in t

Applied "regulator: core: do not report EPROBE_DEFER as error but as debug" to the regulator tree

The patch regulator: core: do not report EPROBE_DEFER as error but as debug has been applied to the regulator tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-5.2 All being well this means that it will be integrated into the linux-next tree (usually someti

Applied "spi: expand mode support" to the spi tree

The patch spi: expand mode support has been applied to the spi tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-5.2 All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during the

Re: [PATCH 18/57] docs: kbuild: convert it to ReST output

Em Thu, 18 Apr 2019 18:25:45 +0900 Masahiro Yamada escreveu: > On Tue, Apr 16, 2019 at 12:01 PM Mauro Carvalho Chehab > wrote: > > > > The kbuild documentation clearly shows that the documents > > there are written at different times: some use markdown, > > some use their own peculiar logic to s

Applied "regulator: slg51000: add slg51000 regulator driver" to the regulator tree

The patch regulator: slg51000: add slg51000 regulator driver has been applied to the regulator tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-5.2 All being well this means that it will be integrated into the linux-next tree (usually sometime in the next

[PATCH 0/3] PM / Domains: Improve support for multi PM domains

It's been a while since the introduction for the support for multi PM domains per device in genpd. In this small series, a couple of different improvement are being made to this code in genpd. Ulf Hansson (3): PM / Domains: Don't kfree() the virtual device in the error path PM / Domains: Allow

[PATCH 1/3] PM / Domains: Don't kfree() the virtual device in the error path

It's not correct to call kfree(dev) when device_register(dev) has failed. Fix this by calling put_device(dev) instead. Fixes: 3c095f32a92b ("PM / Domains: Add support for multi PM domains per device to genpd") Signed-off-by: Ulf Hansson --- drivers/base/power/domain.c | 2 +- 1 file changed, 1

[PATCH 2/3] PM / Domains: Allow OF lookup for multi PM domain case from ->attach_dev()

A genpd provider that uses the ->attach_dev() callback to lookup resources for a device, fails to do so when the device has multiple PM domains. This is because when genpd invokes the ->attach_dev() callback, it passes the allocated virtual device as the in-parameter. To address this problem, let'

[PATCH 3/3] PM / Domains: Enable genpd_dev_pm_attach_by_id|name() for single PM domain

If a call to dev_pm_domain_attach() succeeds to attach a device to its single PM domain, the important point is to prevent following calls to dev_pm_domain_attach_by_name|id() to fail. This is managed by checking the dev->pm_domain pointer and then return -EEXIST, rather than continue calling genpd

Re: Issues with i.MX SPI DMA transfers

[ Trimming recipients list ] On 03/04/2019 17:51, Igor Plyatov wrote: > 2) I want to improve description and replace magic numbers by constants > in Device Tree for SDMA. I mean strings like "dmas = <&sdma 11 7 1>, > <&sdma 12 7 2>;"? > > So, finally Device Tree will have strings like > > dma

[PATCH RFC] staging: vc04_services: handle kzalloc failure

The kzalloc here was being used without checking the return - if the kzalloc fails return VCHIQ_ERROR. The call-site of vchiq_platform_init_state() vchiq_init_state() was not responding to an allocation failure so checks for != VCHIQ_SUCCESS and pass VCHIQ_ERROR up to vchiq_platform_init() which th

Re: [PATCH] char/ipmi: fix spelling mistake "receieved_messages" -> "received_messages"

On 4/18/2019 3:45 PM, Colin King wrote: From: Colin Ian King There is a spelling mistake in the documentation. Fix it. Signed-off-by: Colin Ian King Reviewed-by: Mukesh Ojha Cheers, -Mukesh --- Documentation/ABI/testing/sysfs-devices-platform-ipmi | 2 +- 1 file changed, 1 insertion(

Re: [PATCH v2] panic: add an option to replay all the printk message in buffer

On (04/18/19 09:45), Petr Mladek wrote: > The following functions are currently called from panic_print_sys_info(): > > + show_state(): > printk(KERN_INFO > " taskPC stack pid father\n"); > + show_mem(): > printk("Mem-Info:\n"); > > + sysrq_tim

Re: [PATCH] pci/switchtec: fix stream_open.cocci warnings (fwd)

On Thu, Apr 18, 2019 at 07:31:02AM +0200, Julia Lawall wrote: > > > On Wed, 17 Apr 2019, Bjorn Helgaas wrote: > > > On Sat, Apr 13, 2019 at 06:50:57PM +0200, Julia Lawall wrote: > > > Hello, > > > > > > Kirill will explain about this issue. > > > > > > julia > > > > > > -- Forwarded mess

Re: [PATCH v2] panic: add an option to replay all the printk message in buffer

On Thu 2019-04-18 17:00:44, Feng Tang wrote: > Hi Petr, > > On Thu, Apr 18, 2019 at 09:45:52AM +0200, Petr Mladek wrote: > > On Thu 2019-04-18 09:00:14, Sergey Senozhatsky wrote: > > > I think that PANIC_PRINT_ALL_PRINTK_MSG is a debugging option; a quite > > > specific one. So people who ask the

Re: WARNING in notify_change

On Tue 16-04-19 00:54:28, Al Viro wrote: > 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 clea

Re: [PATCH v2] moduleparam: Save information about built-in modules in separate file

On Sat, Apr 6, 2019 at 9:15 PM Alexey Gladkov wrote: > > Problem: > > When a kernel module is compiled as a separate module, some important > information about the kernel module is available via .modinfo section of > the module. In contrast, when the kernel module is compiled into the > kernel, t

Re: [PATCH v4 1/2] mm: refactor __vunmap() to avoid duplicated call to find_vm_area()

On Wed, Apr 17, 2019 at 02:58:27PM -0700, Andrew Morton wrote: > On Wed, 17 Apr 2019 12:40:01 -0700 Roman Gushchin wrote: > > +static struct vm_struct *__remove_vm_area(struct vmap_area *va) > > +{ > > + struct vm_struct *vm = va->vm; > > + > > + might_sleep(); > > Where might __remove_vm_are

[PATCH] kbuild: re-enable int-in-bool-context warning

This warning was disabled by commit bd664f6b3e37 ("disable new gcc-7.1.1 warnings for now") just because it was too noisy. Thanks to Arnd Bergmann, (almost) all warnings have been fixed. We are now ready to re-enable it. Signed-off-by: Masahiro Yamada Cc: Arnd Bergmann --- Makefile | 1 - 1 f

Re: [PATCH 2/2] arm64: dts: allwinner: a64-amarula-relic: Add OV5640 camera node

Hi, On Thu, Apr 18, 2019 at 02:08:13PM +0530, Jagan Teki wrote: > Amarula A64-Relic board by default bound with OV5640 camera, > so add support for it with below pin information. > > - PE13, PE12 via i2c-gpio bitbanging > - CLK_CSI_MCLK as external clock > - PE1 as external clock pin muxing > - AL

Re: [PATCH 1/2] arm64: dts: allwinner: a64: Add pinmux setting for CSI MCLK on PE1

On Thu, Apr 18, 2019 at 02:08:12PM +0530, Jagan Teki wrote: > Some camera modules have the SoC feeding a master clock to the sensor > instead of having a standalone crystal. This clock signal is generated > from the clock control unit and output from the CSI MCLK function of > pin PE1. > > Add a pi

Re: [PATCH v2 2/2] arm64: dts: allwinner: a64-oceanic-5205-5inmfd: Enable GT911 CTP

On Thu, Apr 18, 2019 at 02:05:43PM +0530, Jagan Teki wrote: > Goodix GT911 CTP is bound with Oceanic 5205 5inMFD board. > > The CTP connected to board with, > - SDA, SCK from i2c0 > - GPIO-LD0 as AVDD28 supply > - PH4 gpio as interrupt pin > - PH11 gpio as reset pin > - X axis is inverted > - Y axi

Re: [PATCH v2 1/2] arm64: dts: allwinner: a64-amarula-relic: Add GT5663 CTP node

On Thu, Apr 18, 2019 at 02:05:42PM +0530, Jagan Teki wrote: > Add Goodix GT5663 capacitive touch controller node on > Amarula A64-Relic board. > > The CTP connected to board with, > - SDA, SCK from i2c1 > - GPIO-LD0 as AVDD28 supply > - PH4 gpio as interrupt pin > - PH8 gpio as reset pin > - X axis

[tip:irq/core] irq_work: Do not raise an IPI when queueing work on the local CPU

Commit-ID: 3ab68397950772b0dccf565b1294d929f573a8a2 Gitweb: https://git.kernel.org/tip/3ab68397950772b0dccf565b1294d929f573a8a2 Author: Nicholas Piggin AuthorDate: Tue, 9 Apr 2019 19:34:03 +1000 Committer: Ingo Molnar CommitDate: Thu, 18 Apr 2019 12:48:49 +0200 irq_work: Do not raise a

[tip:locking/core] locking/lockdep: Move valid_state() inside CONFIG_TRACE_IRQFLAGS && CONFIG_PROVE_LOCKING

Commit-ID: 0d2cc3b3453254f1c56f9456ba03e092ed4cfb72 Gitweb: https://git.kernel.org/tip/0d2cc3b3453254f1c56f9456ba03e092ed4cfb72 Author: Frederic Weisbecker AuthorDate: Tue, 2 Apr 2019 18:02:41 +0200 Committer: Ingo Molnar CommitDate: Thu, 18 Apr 2019 12:50:17 +0200 locking/lockdep: Mov

Re: [PATCH] x86/boot: This program cannot be run in DOS mode.$

* Pavel Machek wrote: > On Mon 2019-04-08 20:08:09, Pali Rohár wrote: > > On Monday 08 April 2019 20:04:22 Pavel Machek wrote: > > > On Mon 2019-04-01 12:24:34, Pali Rohár wrote: > > > > Every EFI binary is in PE format. And we know that PE format needs to > > > > have > > > > MZ MS-DOS header

[tip:locking/core] locking/lockdep: Map remaining magic numbers to lock usage mask names

Commit-ID: c902a1e8d9c9b47cd8faa16892710247cdda9b02 Gitweb: https://git.kernel.org/tip/c902a1e8d9c9b47cd8faa16892710247cdda9b02 Author: Frederic Weisbecker AuthorDate: Tue, 2 Apr 2019 18:02:42 +0200 Committer: Ingo Molnar CommitDate: Thu, 18 Apr 2019 12:50:17 +0200 locking/lockdep: Map

Re: [PATCH] The patch solves the type error of the parameter “off” in syscall mmap on the ARM64 platform.

[adding linux-arch and relevant folk] On Wed, Apr 17, 2019 at 08:35:25PM +0800, Boyang Zhou wrote: > The error information is that “offset value too large for defined data type”. > Reason: > On the X86 platform, the data type of “off" is unsigned long; but on the > ARM64 platform, the data type i

[tip:locking/core] locking/lockdep: Use expanded masks on find_usage_*() functions

Commit-ID: 627f364d24c009b61c9199b2c75006e35c294675 Gitweb: https://git.kernel.org/tip/627f364d24c009b61c9199b2c75006e35c294675 Author: Frederic Weisbecker AuthorDate: Tue, 2 Apr 2019 18:02:43 +0200 Committer: Ingo Molnar CommitDate: Thu, 18 Apr 2019 12:50:17 +0200 locking/lockdep: Use

[PATCH] livepatch: Convert error about unsupported reliable stacktrace into a warning

The commit d0807da78e11d46f ("livepatch: Remove immediate feature") caused that any livepatch was refused when reliable stacktraces were not supported on the given architecture. The limitation is too strong. User space processes are safely migrated even when entering or leaving the kernel. Kthread

Re: [PATCH v1 1/1] thermal: rcar_gen3_thermal: request IRQ after device initialization

Hi Daniel Thanks for your comments On 2019/04/17 17:05, Daniel Lezcano wrote: On 17/04/2019 05:01, Jiada Wang wrote: Hi Daniel On 2019/04/17 4:22, Daniel Lezcano wrote: On 11/04/2019 12:03, Jiada Wang wrote: Currently IRQ is remain enabled after .remove, later if device is probed, IRQ is re

Re: [PATCH] ACPI / LPSS: Don't skip late system PM ops for hibernate on BYT/CHT

Hello Robert, On 11-04-19 21:50, Robert R. Howell wrote: On 4/8/19 2:16 AM, Hans de Goede wrote:> Hmm, interesting so you have hibernation working on a T100TA (with 5.0 + 02e45646d53b reverted), right ? Hi Hans and Kai-Heng First, apologies for how long it took me to reply to both your inqu

[PATCH 2/3] regulator: ltc3589: Get rid of struct ltc3589_regulator

After converting to use simplified DT parsing, the struct ltc3589_regulator only has a desc member. So let's remove struct ltc3589_regulator and use struct regulator_desc instead. Signed-off-by: Axel Lin --- drivers/regulator/ltc3589.c | 69 + 1 file changed,

[PATCH 3/3] regulator: ltc3589: Switch to SPDX identifier

Signed-off-by: Axel Lin --- drivers/regulator/ltc3589.c | 24 ++-- 1 file changed, 6 insertions(+), 18 deletions(-) diff --git a/drivers/regulator/ltc3589.c b/drivers/regulator/ltc3589.c index 077e73715514..9a037fdc5fc5 100644 --- a/drivers/regulator/ltc3589.c +++ b/drivers/r

[PATCH 1/3] regulator: ltc3589: Convert to use simplified DT parsing

Use regulator core's simplified DT parsing code to simplify the driver implementation. Signed-off-by: Axel Lin --- drivers/regulator/ltc3589.c | 194 +++- 1 file changed, 58 insertions(+), 136 deletions(-) diff --git a/drivers/regulator/ltc3589.c b/drivers/regula

Re: [PATCH] ext4: add cond_resched() to ext4_mb_init_backend()

On Mon 15-04-19 19:59:34, Khazhismel Kumykov wrote: > on non-preempt kernels for filesystems with large number of groups we > may take a long time (>50 ticks) initializing all the groups. > > Signed-off-by: Khazhismel Kumykov Thanks for the patch. I'm not opposed to this but I'm just wondering:

Re: [PATCH] ext4: fix use-after-free race with debug_want_extra_isize

On Mon 15-04-19 17:19:45, Barret Rhoden wrote: > 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+f584efa0a

[tip:locking/core] locking/lockdep: Avoid bogus Clang warning

Commit-ID: 3771b0fe9dfc3801eac0142d1af6ba94dee83c6c Gitweb: https://git.kernel.org/tip/3771b0fe9dfc3801eac0142d1af6ba94dee83c6c Author: Arnd Bergmann AuthorDate: Mon, 25 Mar 2019 13:57:57 +0100 Committer: Ingo Molnar CommitDate: Thu, 18 Apr 2019 14:01:17 +0200 locking/lockdep: Avoid bo

Re: [RFC PATCH 54/62] ext4: make use of ->free_inode()

On Tue 16-04-19 18:53:32, Al Viro wrote: > From: Al Viro > > the rest of this ->destroy_inode() instance could probably be folded > into ext4_evict_inode() > > Signed-off-by: Al Viro Looks good to me. You can add: Reviewed-by: Jan Kara You're right about the possibility of moving the check

[tip:perf/core] watchdog: Fix typo in comment

Commit-ID: 76e1552466ff2da8b909df0fff3600ec1c27edcc Gitweb: https://git.kernel.org/tip/76e1552466ff2da8b909df0fff3600ec1c27edcc Author: Arash Fotouhi AuthorDate: Fri, 22 Mar 2019 19:28:32 -0700 Committer: Ingo Molnar CommitDate: Thu, 18 Apr 2019 14:05:51 +0200 watchdog: Fix typo in com

[tip:irq/core] irq_work: Do not raise an IPI when queueing work on the local CPU

Commit-ID: 471ba0e686cb13752bc1ff3216c54b69a2d250ea Gitweb: https://git.kernel.org/tip/471ba0e686cb13752bc1ff3216c54b69a2d250ea Author: Nicholas Piggin AuthorDate: Tue, 9 Apr 2019 19:34:03 +1000 Committer: Ingo Molnar CommitDate: Thu, 18 Apr 2019 14:07:52 +0200 irq_work: Do not raise a

Re: [PATCH] nvme: determine the number of IO queues

On 4/18/19 3:21 PM, Aaron Ma wrote: On 4/18/19 1:33 AM, Maxim Levitsky wrote: On Wed, 2019-04-17 at 20:32 +0300, Maxim Levitsky wrote: On Wed, 2019-04-17 at 22:12 +0800, Aaron Ma wrote: Some controllers support limited IO queues, when over set the number, it will return invalid field error. Th

Re: [RFC PATCH 49/62] dax: make use of ->free_inode()

On Tue 16-04-19 18:53:27, Al Viro wrote: > From: Al Viro > > we might want to drop ->destroy_inode() there - it's used only for > WARN_ON() now, and AFAICS that could be moved to ->evict_inode() > if we had one... > > Signed-off-by: Al Viro > --- > drivers/dax/super.c | 7 ++- > 1 file cha

Re: [PATCH] asm/io: Correct output operand specification of the MMIO write* routines

Hi, On Wed, 17 Apr 2019, Linus Torvalds wrote: > So I see no upside to changing it. As long as the memory clobber stays (and it can't be removed in the general case, as you say) the change has no practical effect. It does have a psychological upside, though: people won't continue to wonder w

[tip:timers/urgent] tiemrs/sched_clock: Prevent generic sched_clock wrap caused by tick_freeze()

Commit-ID: fe4a9a665de982b9eeb4a5e61f9c1c1abe80fb51 Gitweb: https://git.kernel.org/tip/fe4a9a665de982b9eeb4a5e61f9c1c1abe80fb51 Author: Chang-An Chen AuthorDate: Fri, 29 Mar 2019 10:59:09 +0800 Committer: Thomas Gleixner CommitDate: Thu, 18 Apr 2019 14:16:31 +0200 tiemrs/sched_clock: P

Re: [PATCH v4 01/26] ALSA: line6: Avoid polluting led_* namespace

On Thu 2019-04-18 07:17:54, Takashi Iwai wrote: > On Wed, 17 Apr 2019 22:54:14 +0200, > Jacek Anaszewski wrote: > > > > led_colors clashes with the array of the same name being added > > to the LED class. Do the following amendments to fix this issue > > and the other prospective one. > > > > led

[PATCH] staging: rtl8723bs: hal: fix spelling mistake "singal" -> "signal"

From: Colin Ian King There are multiple spelling mistakes in variable names, fix these. Signed-off-by: Colin Ian King --- drivers/staging/rtl8723bs/hal/hal_com.c | 18 +- drivers/staging/rtl8723bs/include/rtw_recv.h | 4 ++-- 2 files changed, 11 insertions(+), 11 deletion

Re: [PATCH v4 01/26] ALSA: line6: Avoid polluting led_* namespace

On Thu, 18 Apr 2019 14:21:35 +0200, Pavel Machek wrote: > > On Thu 2019-04-18 07:17:54, Takashi Iwai wrote: > > On Wed, 17 Apr 2019 22:54:14 +0200, > > Jacek Anaszewski wrote: > > > > > > led_colors clashes with the array of the same name being added > > > to the LED class. Do the following amend

[tip:sched/core] sched/core: Make some functions static

Commit-ID: 16e671afb70f28eb189136d1395c59dafecd270a Gitweb: https://git.kernel.org/tip/16e671afb70f28eb189136d1395c59dafecd270a Author: YueHaibing AuthorDate: Fri, 22 Mar 2019 22:31:53 +0800 Committer: Ingo Molnar CommitDate: Thu, 18 Apr 2019 14:19:25 +0200 sched/core: Make some functi

Re: [linux-sunxi] Re: [PATCH v3 1/7] ARM: dts: sun8i: r40: bananapi-m2-ultra: Tie GMAC regulators to the PIO

El 17/4/19 a las 07:17, Maxime Ripard escribió: Hi, On Wed, Apr 17, 2019 at 06:20:56AM -0300, Pablo Greco wrote: When the GMAC support was added to the bananapi-m2-ultra, regulators weren't tied to the pinctrl. Fix that. Signed-off-by: Pablo Greco --- arch/arm/boot/dts/sun8i-r40-bananapi-

[PATCH 2/6] arm64: dts: meson: libretech-cc: switch eMMC to 1.8v

While some 3.3v eMMC 4.0 are available from libretech, Only the 1.8v 5.0 modules are recommended and supported for the aml-s905x-cc. the 1.8v is provided by LDOs on the eMMC card, from vcc 3.3v Signed-off-by: Jerome Brunet --- .../boot/dts/amlogic/meson-gxl-s905x-libretech-cc.dts | 11 +++--

[PATCH 5/6] arm64: dts: meson: vim2: add missing clk-gate pinctrl

For some reason the vim2 is missing the clk-gate pinctrl setting all the other board have. Just add this missing bit Signed-off-by: Jerome Brunet --- arch/arm64/boot/dts/amlogic/meson-gxm-khadas-vim2.dts | 9 ++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/arch/arm64/boot

[PATCH 1/6] arm64: dts: meson: libretech-cc: set eMMC as removable

The eMMC on this board is add-on module which is not mandatory. Removing 'non-removable' property should prevent some errors when booting a board w/o an eMMC module present. Fixes: 72fb2c852188 ("ARM64: dts: meson-gxl-s905x-libretech-cc: fixup board definition") Signed-off-by: Jerome Brunet ---

[PATCH 4/6] arm64: dts: meson: fix mmc v2 chips max frequencies

According the datasheets, emmc v2 chips (gxbb and gxl) don't support more that 100Mhz in UHS-1 SD modes and HS in SDIO. Align the max-frequency to 100MHz for UHS-1 and 50MHz for HS Signed-off-by: Jerome Brunet --- arch/arm64/boot/dts/amlogic/meson-gx-p23x-q20x.dtsi | 4 ++-- arch/arm64

[PATCH 0/6] arm64: dts: meson: mmc clean-up

The patchset is bunch of clean-up found while debugging meson mmc. * The first 2 patches address the libretech-cc which actually uses 1.8v eMMC modules. * Patch 3 is a pin bias fixup depending on mmc pins. * Patch 4 lower the mmc max frequencies on gx chips. It was not easy to spot but, accord

[PATCH 6/6] arm64: dts: meson: vim2: remove sd hs and hs400 modes from emmc

sd highspeed mode make no sense for an eMMC and HS400 is not working at the moment. Signed-off-by: Jerome Brunet --- arch/arm64/boot/dts/amlogic/meson-gxm-khadas-vim2.dts | 2 -- 1 file changed, 2 deletions(-) diff --git a/arch/arm64/boot/dts/amlogic/meson-gxm-khadas-vim2.dts b/arch/arm64/boot

[PATCH 3/6] arm64: dts: meson: fix mmc pin bias

Clk pin does not require bias, data strobe should be pulled low. The rest of the pin (data and cmd) are pulled up. Signed-off-by: Jerome Brunet --- .../arm64/boot/dts/amlogic/meson-axg-s400.dts | 4 +-- arch/arm64/boot/dts/amlogic/meson-axg.dtsi| 31 arch/arm64/boot/dts/aml

Re: [PATCH v4 11/26] dt-bindings: lp8860: Add function and color properties

Jacek On 4/17/19 3:54 PM, Jacek Anaszewski wrote: > Refer to new "function" and "color" properties and mark "label" > as deprecated. > > Signed-off-by: Jacek Anaszewski > Cc: Dan Murphy I gave reviewed-by for DT docs and tested-by for code for the TI parts affected. Dan

[PATCH -v5.1] x86/kvm: Implement HWCR support

Hi all, ok here's v5.1 with most of Sean's feedback addressed. The function checking whether HWCR[18] is set, I've renamed to can_set_mci_status() and left it to return bool because it really is used in boolean context, answering the question "Can I set MCi_STATUS MSRs?" And now it all looks simp

Re: [PATCH v2 1/2] arm64: dts: allwinner: a64-amarula-relic: Add GT5663 CTP node

On Thu, Apr 18, 2019 at 4:54 PM Maxime Ripard wrote: > > On Thu, Apr 18, 2019 at 02:05:42PM +0530, Jagan Teki wrote: > > Add Goodix GT5663 capacitive touch controller node on > > Amarula A64-Relic board. > > > > The CTP connected to board with, > > - SDA, SCK from i2c1 > > - GPIO-LD0 as AVDD28 sup

Re: [PATCH v4 2/2] x86/boot/KASLR: skip the specified crashkernel region

On Thu, Apr 18, 2019 at 03:56:09PM +0800, Pingfan Liu wrote: > Then in my case, either no @offset or invalid argument will keep > "*crash_base = 0", and KASLR does not care about either of them. Ok. > It is not elegant. Will try a separate patch to fix it firstly. That's appreciated, thanks. It

Re: [PATCH RFC] staging: vc04_services: handle kzalloc failure

On 18.04.19 12:29, Nicholas Mc Guire wrote: > The kzalloc here was being used without checking the return - if the > kzalloc fails return VCHIQ_ERROR. The call-site of > vchiq_platform_init_state() vchiq_init_state() was not responding > to an allocation failure so checks for != VCHIQ_SUCCESS > and

Re: ext4: avoid drop reference to iloc.bh twice

On Thu 18-04-19 16:31:18, Pan Bian wrote: > The reference to iloc.bh has been dropped in ext4_mark_iloc_dirty. > However, the reference is dropped again if error occurs during > ext4_handle_dirty_metadata, which may result in use-after-free bugs. > > Fixes: fb265c9cb49e("ext4: add ext4_sb_bread()

Re: [PATCH] pci/switchtec: fix stream_open.cocci warnings (fwd)

On Thu, Apr 18, 2019 at 10:38:02AM +, Kirill Smelkov wrote: > On Thu, Apr 18, 2019 at 07:31:02AM +0200, Julia Lawall wrote: > > On Wed, 17 Apr 2019, Bjorn Helgaas wrote: > > > On Sat, Apr 13, 2019 at 06:50:57PM +0200, Julia Lawall wrote: > > > > Hello, > > > > > > > > Kirill will explain about

[GIT PULL rcu/next + tools/memory-model] RCU and LKMM commits for 5.2

Hello, Ingo, This pull request contains the following changes: 1. An LKMM commit adding support for synchronize_srcu_expedited(). http://lkml.kernel.org/r/20190326234133.24962-8-paul...@linux.ibm.com 2. A couple of straggling RCU flavor consolidation updates. http://l

Re: [PATCH 1/3] RISC-V: Add DT documentation for SiFive L2 Cache Controller

On Mon, Apr 15, 2019 at 05:10:41PM +0530, Yash Shah wrote: > This patch adds device tree bindings for SiFive FU540 L2 cache controller > driver Avoid having "This patch" or "This commit" in the commit message. It is tautologically useless. Also, do $ git grep 'This patch' Documentation/process

[tip:timers/urgent] timers/sched_clock: Prevent generic sched_clock wrap caused by tick_freeze()

Commit-ID: 3f2552f7e9c5abef2775c53f7af66532f8bf65bc Gitweb: https://git.kernel.org/tip/3f2552f7e9c5abef2775c53f7af66532f8bf65bc Author: Chang-An Chen AuthorDate: Fri, 29 Mar 2019 10:59:09 +0800 Committer: Thomas Gleixner CommitDate: Thu, 18 Apr 2019 14:34:53 +0200 timers/sched_clock: P

Re: [PATCH-tip 0/2] locking/rwsem: Rwsem rearchitecture part 2 follow-up patches

On 04/18/2019 04:02 AM, Ingo Molnar wrote: > * Waiman Long wrote: > >> As the part2 patches are still being actively modified, it doesn't look >> like it will make the next merge window. I am fine with postponing it >> to 5.3. However, I would like to request the merging of just patch 1 of >> t

[tip:x86/urgent] x86/mpx: Fix recursive munmap() corruption

Commit-ID: 508b8482ea2227ba8695d1cf8311166a455c2ae0 Gitweb: https://git.kernel.org/tip/508b8482ea2227ba8695d1cf8311166a455c2ae0 Author: Dave Hansen AuthorDate: Mon, 1 Apr 2019 07:15:49 -0700 Committer: Thomas Gleixner CommitDate: Thu, 18 Apr 2019 14:39:08 +0200 x86/mpx: Fix recursive m

[tip:x86/urgent] x86/mpx: Fix recursive munmap() corruption

Commit-ID: 9d812ad8fce2c556538f6efe8ab1ae78ab59ae8f Gitweb: https://git.kernel.org/tip/9d812ad8fce2c556538f6efe8ab1ae78ab59ae8f Author: Dave Hansen AuthorDate: Mon, 1 Apr 2019 07:15:49 -0700 Committer: Thomas Gleixner CommitDate: Thu, 18 Apr 2019 14:37:04 +0200 x86/mpx: Fix recursive m

Avoiding merge conflicts while adding new docs - Was: Re: [PATCH 00/57] Convert files to ReST

Jon, Em Mon, 15 Apr 2019 23:55:25 -0300 Mauro Carvalho Chehab escreveu: > I have a separate patch series with do the actual rename and > adjustment of references. I opted to submit this first, as it > sounds easier to merge this way, as each subsystem maintainer > can apply the conversion direct

Re: [PATCH] staging: rtl8723bs: hal: fix spelling mistake "singal" -> "signal"

On 4/18/2019 5:50 PM, Colin King wrote: From: Colin Ian King There are multiple spelling mistakes in variable names, fix these. Signed-off-by: Colin Ian King Well, this one a bit sensitive to touch. Reviewed-by: Mukesh Ojha Cheers, -Mukesh --- drivers/staging/rtl8723bs/hal/hal_com.

Re: [GIT PULL rcu/next + tools/memory-model] RCU and LKMM commits for 5.2

* Paul E. McKenney wrote: > Hello, Ingo, > > This pull request contains the following changes: > > 1.An LKMM commit adding support for synchronize_srcu_expedited(). > > http://lkml.kernel.org/r/20190326234133.24962-8-paul...@linux.ibm.com > > 2.A couple of straggling RCU flavo

[PATCH v2 1/4] dt-bindings: pinctrl: add a 'drive-strength-uA' property

This property allow drive-strength parameter in uA instead of mA. Signed-off-by: Guillaume La Roque --- Documentation/devicetree/bindings/pinctrl/pinctrl-bindings.txt | 3 +++ 1 file changed, 3 insertions(+) diff --git a/Documentation/devicetree/bindings/pinctrl/pinctrl-bindings.txt b/Document

[PATCH v2 2/4] pinctrl: generic: add new 'drive-strength-uA' property support

Add drive-strength-uA property support to allow drive strength in uA Signed-off-by: Guillaume La Roque --- drivers/pinctrl/pinconf-generic.c | 2 ++ include/linux/pinctrl/pinconf-generic.h | 3 +++ 2 files changed, 5 insertions(+) diff --git a/drivers/pinctrl/pinconf-generic.c b/drivers/

[PATCH v2 0/4] Add drive-strength in Meson pinctrl driver

The purpose of this patchset is to add drive-strength support in meson pinconf driver. This is a new feature that was added on the g12a. It is critical for us to support this since many functions are failing with default pad drive-strength. The value achievable by the SoC are 0.5mA, 2.5mA, 3mA an

[PATCH v2 4/4] pinctrl: meson: add support of drive-strength-uA

drive-strength-uA is a new feature needed for G12A SoC. the default DS setting after boot is usually 500uA and it is not enough for many functions. We need to be able to set the drive strength to reliably enable things like MMC, I2C, etc ... Signed-off-by: Guillaume La Roque --- drivers/pinctrl/

[PATCH v2 3/4] dt-bindings: pinctrl: meson: Add drive-strength-uA property

Add optional drive-strength-uA property Signed-off-by: Guillaume La Roque --- Documentation/devicetree/bindings/pinctrl/meson,pinctrl.txt | 3 +++ 1 file changed, 3 insertions(+) diff --git a/Documentation/devicetree/bindings/pinctrl/meson,pinctrl.txt b/Documentation/devicetree/bindings/pinctr

Re: [tip:sched/core] sched/core: Make some functions static

* tip-bot for YueHaibing wrote: > Commit-ID: 16e671afb70f28eb189136d1395c59dafecd270a > Gitweb: > https://git.kernel.org/tip/16e671afb70f28eb189136d1395c59dafecd270a > Author: YueHaibing > AuthorDate: Fri, 22 Mar 2019 22:31:53 +0800 > Committer: Ingo Molnar > CommitDate: Thu, 18 Ap

<    1   2   3   4   5   6   7   8   9   10   >