[PATCH] platform/x86: dell-laptop: don't register platform::micmute if the related tokens don't exist.

From: Koba Ko On dell G3-3590, error message is issued during boot up, "platform::micmute: Setting an LED's brightness failed (-19)", but there's no micmute led on the machine. Get the related tokens of SMBIOS, GLOBAL_MIC_MUTE_DISABLE/ENABLE. If one of two tokens doesn't exist, don't call

Re: compaction: VM_BUG_ON_PAGE(!zone_spans_pfn(page_zone(page), pfn))

On 05/05/20 at 09:20am, Qian Cai wrote: > > > > On May 5, 2020, at 8:43 AM, Baoquan He wrote: > > > > Hi, > > > > On 04/24/20 at 09:45am, Qian Cai wrote: > >> > >> > >>> On Apr 23, 2020, at 11:43 PM, Baoquan He wrote: > >>> > >>> On 04/23/20 at 05:25pm, Qian Cai wrote: > Compaction

Re: [PATCH] mm, compaction: Indicate when compaction is manually triggered by sysctl

On Fri, 8 May 2020, Guilherme Piccoli wrote: > On Fri, May 8, 2020 at 3:31 PM David Rientjes wrote: > > It doesn't make sense because it's only being done here for the entire > > system, there are also per-node sysfs triggers so you could do something > > like iterate over the nodemask of all

Re: [PATCH -next 0/2] sparc: use snprintf() in show() methods

Sorry, i made a mistake, should be scnprintf(). On 2020/5/9 19:40, Joe Perches wrote: > On Sat, 2020-05-09 at 17:18 +0800, Chen Zhou wrote: >> snprintf() returns the number of bytes that would be written, >> which may be greater than the the actual length to be written. > [] >> Chen Zhou (2): >>

Re: [PATCH V4] f2fs: Avoid double lock for cp_rwsem during checkpoint

On 2020/5/10 3:03, Jaegeuk Kim wrote: > On 05/09, Chao Yu wrote: >> On 2020/5/9 0:10, Jaegeuk Kim wrote: >>> Hi Sayali, >>> >>> In order to address the perf regression, how about this? >>> >>> >From 48418af635884803ffb35972df7958a2e6649322 Mon Sep 17 00:00:00 2001 >>> From: Jaegeuk Kim >>> Date:

Re: [RFC PATCH v2 1/7] block: Extand commit_rqs() to do batch processing

On Sun, May 10, 2020 at 12:44:53AM -0700, Sagi Grimberg wrote: > > > > > > You're mostly correct. This is exactly why an I/O scheduler may be > > > > > applicable here IMO. Mostly because I/O schedulers tend to optimize > > > > > for > > > > > something specific and always present tradeoffs.

Re: [PATCH] ASoC: rsnd: add interrupt support for SSI BUSIF buffer

Hi Yongbo Thank you for the patch > SSI BUSIF buffer is possible to overflow or underflow, especially in a > hypervisor environment. If there is no interrupt support, it will eventually > lead to errors in pcm data. > This patch adds overflow and underflow interrupt support for SSI BUSIF

Re: [PATCH -next] riscv: perf_event: Make some funciton static

On 2020/5/9 1:13, Palmer Dabbelt wrote: What's the "-next" for?  This seems appropriate for an RC to me, as it's a build fix. Thanks for your review, this patch and "[PATCH -next] riscv: perf: RISCV_BASE_PMU should be closeable", I fix the issue based on linux-next, so add the next

Re: [PATCH -next 0/2] sparc: use snprintf() in show() methods

On Mon, 2020-05-11 at 09:24 +0800, chenzhou wrote: > Sorry, i made a mistake, should be scnprintf(). No worries. But why do you think this is useful? Is it likely that either snprint length will exceed PAGE_SIZE? > > On 2020/5/9 19:40, Joe Perches wrote: > > On Sat, 2020-05-09 at 17:18 +0800,

Re: [pipe] f2af7d90e2: xfstests.btrfs.052.fail

On 5/11/20 9:16 AM, Matthew Wilcox wrote: On Mon, May 11, 2020 at 09:09:57AM +0800, kernel test robot wrote: --- tests/btrfs/095.out2020-04-09 10:45:28.0 +0800 +++ /lkp/benchmarks/xfstests/results//btrfs/095.out.bad2020-05-06 21:13:51.276485703 +0800 @@ -1,35

Re: [PATCH] extcon: adc-jack: Fix an error handling path in 'adc_jack_probe()'

On 5/10/20 6:53 PM, Christophe JAILLET wrote: > In some error handling paths, a call to 'iio_channel_get()' is not balanced > by a corresponding call to 'iio_channel_release()'. > > This can be achieved easily by using the devm_ variant of > 'iio_channel_get()'. > > This has the extra benefit to

[PATCH] bootconfig: Fix to prevent warning message if no bootconfig option

Commit de462e5f1071 ("bootconfig: Fix to remove bootconfig data from initrd while boot") causes a cosmetic regression on dmesg, which warns "no bootconfig data" message without bootconfig cmdline option. Fix setup_boot_config() by moving no bootconfig check after commandline option check. Fixes:

[PATCH] V2: platform/x86: dell-laptop: don't register platform::micmute if the related tokens don't exist.

From: Koba Ko On dell G3-3590, error message is issued during boot up, "platform::micmute: Setting an LED's brightness failed (-19)", but there's no micmute led on the machine. Get the related tokens of SMBIOS, GLOBAL_MIC_MUTE_DISABLE/ENABLE. If one of two tokens doesn't exist, don't call

[PATCH v2] sched/debug: Fix requested task uclamp values shown in procfs

The intention of commit 96e74ebf8d59 ("sched/debug: Add task uclamp values to SCHED_DEBUG procfs") was to print requested and effective task uclamp values. The requested values printed are read from p->uclamp, which holds the last effective values. Fix this by printing the values from

Re: linux-next: manual merge of the vfs tree with the parisc-hd tree

On 2020/5/11 9:11, Stephen Rothwell wrote: Hi all, Today's linux-next merge of the vfs tree got a conflict in: kernel/sysctl.c between commit: b6522fa409cf ("parisc: add sysctl file interface panic_on_stackoverflow") from the parisc-hd tree and commit: f461d2dcd511 ("sysctl: avoid

Re: [PATCH] sched/debug: Fix requested task uclamp values shown in procfs

On Sun, May 10, 2020 at 05:16:28PM +0100, Valentin Schneider wrote: > > On 10/05/20 13:56, Pavankumar Kondeti wrote: > > The intention of commit 96e74ebf8d59 ("sched/debug: Add task uclamp > > values to SCHED_DEBUG procfs") was to print requested and effective > > task uclamp values. The

Re: [PATCH 05/18] mm: memcontrol: convert page cache to a new mem_cgroup_charge() API

On Fri, May 08, 2020 at 12:01:22PM -0400, Johannes Weiner wrote: > On Thu, Apr 23, 2020 at 02:25:06PM +0900, Joonsoo Kim wrote: > > On Wed, Apr 22, 2020 at 08:09:46AM -0400, Johannes Weiner wrote: > > > On Wed, Apr 22, 2020 at 03:40:41PM +0900, Joonsoo Kim wrote: > > > > On Mon, Apr 20, 2020 at

RE: [RFC] Issue in final aggregate value, in case of multiple events present in metric expression

> -Original Message- > From: Jin, Yao > Sent: 2020年5月11日 9:12 > To: kajoljain ; Joakim Zhang > ; a...@kernel.org; Jiri Olsa ; > Andi Kleen > Cc: linux-kernel@vger.kernel.org; linux-perf-us...@vger.kernel.org; Kan Liang > ; Madhavan Srinivasan > ; Anju T Sudhakar ; > Ravi Bangoria >

Re: [PATCH v11 33/56] Input: atmel_mxt_ts - delay enabling IRQ when not using regulators

Hello Dmitry Thanks for your comment and test, can you let me know which platform (board) you are using for test, and DTS changes if you have added any. Thanks, Jiada On 2020/05/11 10:05, Dmitry Osipenko wrote: 08.05.2020 08:56, Jiada Wang пишет: The path of enabling the IRQ in the probe

Re: [PATCH net v2] hinic: fix a bug of ndo_stop

Will fix. Thanks. On 2020/5/10 6:37, Jakub Kicinski wrote: On Fri, 8 May 2020 20:19:33 + Luo bin wrote: if some function in ndo_stop interface returns failure because of hardware fault, must go on excuting rest steps rather than return failure directly, otherwise will cause memory leak.And

Re: [PATCH v2 4/6] dmaengine: dw: Print warning if multi-block is unsupported

Hello Mark On Fri, May 08, 2020 at 12:53:34PM +0100, Mark Brown wrote: > On Fri, May 08, 2020 at 02:26:04PM +0300, Andy Shevchenko wrote: > > On Fri, May 08, 2020 at 01:53:02PM +0300, Serge Semin wrote: > > > > Multi-block support provides a way to map the kernel-specific SG-table so > > > the

[PATCH v8 00/10] exynos-ufs: Add support for UFS HCI

This patch-set introduces UFS (Universal Flash Storage) host controller support for Samsung family SoC. Mostly, it consists of UFS PHY and host specific driver. - Changes since v7: * fixed review comments from Rob and Kishon * Addeded reviwed-by tags * rebased on top of v5.7-rc4 - Changes since

[PATCH v8 04/10] scsi: ufs: introduce UFSHCD_QUIRK_PRDT_BYTE_GRAN quirk

Some UFS host controllers like Exynos uses granularities of PRDT length and offset as bytes, whereas others uses actual segment count. Reviewed-by: Avri Altman Signed-off-by: Kiwoong Kim Signed-off-by: Alim Akhtar --- drivers/scsi/ufs/ufshcd.c | 30 +++---

[PATCH v8 03/10] scsi: ufs: add quirk to enable host controller without hce

Some host controllers don't support host controller enable via HCE. Reviewed-by: Can Guo Reviewed-by: Avri Altman Signed-off-by: Seungwon Jeon Signed-off-by: Alim Akhtar --- drivers/scsi/ufs/ufshcd.c | 76 +-- drivers/scsi/ufs/ufshcd.h | 6 2 files

[PATCH v8 02/10] scsi: ufs: add quirk to disallow reset of interrupt aggregation

Some host controllers support interrupt aggregation but don't allow resetting counter and timer in software. Reviewed-by: Avri Altman Signed-off-by: Seungwon Jeon Signed-off-by: Alim Akhtar --- drivers/scsi/ufs/ufshcd.c | 3 ++- drivers/scsi/ufs/ufshcd.h | 6 ++ 2 files changed, 8

Re: [PATCH V2] arm64/cpufeature: Validate hypervisor capabilities during CPU hotplug

On 05/09/2020 04:29 PM, Marc Zyngier wrote: > On Fri, 08 May 2020 03:52:38 +0100, > Anshuman Khandual wrote: >> >> This validates hypervisor capabilities like VMID width, IPA range for any >> hot plug CPU against system finalized values. While here, it factors out >> get_vmid_bits() for

[PATCH v8 06/10] dt-bindings: phy: Document Samsung UFS PHY bindings

This patch documents Samsung UFS PHY device tree bindings Reviewed-by: Rob Herring Signed-off-by: Alim Akhtar Tested-by: Paweł Chmiel --- .../bindings/phy/samsung,ufs-phy.yaml | 75 +++ 1 file changed, 75 insertions(+) create mode 100644

[PATCH v8 07/10] phy: samsung-ufs: add UFS PHY driver for samsung SoC

This patch introduces Samsung UFS PHY driver. This driver supports to deal with phy calibration and power control according to UFS host driver's behavior. Reviewed-by: Kiwoong Kim Signed-off-by: Seungwon Jeon Signed-off-by: Alim Akhtar Cc: Kishon Vijay Abraham I Tested-by: Paweł Chmiel ---

[PATCH v8 09/10] scsi: ufs-exynos: add UFS host support for Exynos SoCs

This patch introduces Exynos UFS host controller driver, which mainly handles vendor-specific operations including link startup, power mode change and hibernation/unhibernation. Reported-by: kbuild test robot Reported-by: Julia Lawall [robot: drivers/scsi/ufs/ufs-exynos.c:931:8-10: WARNING:

[PATCH v8 08/10] dt-bindings: ufs: Add DT binding documentation for ufs

This patch adds DT binding for samsung ufs hci Signed-off-by: Alim Akhtar --- .../bindings/ufs/samsung,exynos-ufs.yaml | 92 +++ 1 file changed, 92 insertions(+) create mode 100644 Documentation/devicetree/bindings/ufs/samsung,exynos-ufs.yaml diff --git

[PATCH v8 01/10] scsi: ufs: add quirk to fix mishandling utrlclr/utmrlclr

In the right behavior, setting the bit to '0' indicates clear and '1' indicates no change. If host controller handles this the other way, UFSHCI_QUIRK_BROKEN_REQ_LIST_CLR can be used. Reviewed-by: Can Guo Reviewed-by: Avri Altman Signed-off-by: Seungwon Jeon Signed-off-by: Alim Akhtar ---

[PATCH v8 05/10] scsi: ufs: add quirk to fix abnormal ocs fatal error

From: Kiwoong Kim Some controller like Exynos determines if FATAL ERROR (0x7) in OCS field in UTRD occurs for values other than GOOD (0x0) in STATUS field in response upiu as well as errors that a host controller can't cover. This patch is to prevent from reporting command results in those

[PATCH v8 10/10] arm64: dts: Add node for ufs exynos7

Adding dt node foe UFS and UFS-PHY for exynos7 SoC. Signed-off-by: Alim Akhtar Tested-by: Paweł Chmiel --- .../boot/dts/exynos/exynos7-espresso.dts | 4 ++ arch/arm64/boot/dts/exynos/exynos7.dtsi | 44 ++- 2 files changed, 46 insertions(+), 2 deletions(-) diff

[PATCH 05/10] riscv: Disable ARCH_HAS_DEBUG_WX if NOMMU

DEBUG_WX is only useful when MMU enabled, diable it if nommu and fix the build error. Reported-by: Hulk Robot Signed-off-by: Kefeng Wang --- arch/riscv/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/riscv/Kconfig b/arch/riscv/Kconfig index

[PATCH 00/10] riscv: make riscv build happier

When add RISCV arch to huawei build test, there are some build issue, let's fix them to make riscv build happier :) Those patches is rebased on next-20200508. Kefeng Wang (10): riscv: Fix unmet direct dependencies built based on SOC_VIRT riscv: stacktrace: Fix undefined reference to

[PATCH 03/10] riscv: Add pgprot_writecombine/device and PAGE_SHARED defination if NOMMU

Some drivers use PAGE_SHARED, pgprot_writecombine()/pgprot_device(), add the defination to fix build error if NOMMU. Reported-by: Hulk Robot Signed-off-by: Kefeng Wang --- arch/riscv/include/asm/mmio.h| 2 ++ arch/riscv/include/asm/pgtable.h | 1 + 2 files changed, 3 insertions(+) diff

[PATCH 02/10] riscv: stacktrace: Fix undefined reference to `walk_stackframe'

Drop static declaration to fix following build error if FRAME_POINTER disabled, riscv64-linux-ld: arch/riscv/kernel/perf_callchain.o: in function `.L0': perf_callchain.c:(.text+0x2b8): undefined reference to `walk_stackframe' Reported-by: Hulk Robot Signed-off-by: Kefeng Wang ---

[PATCH 08/10] riscv: pgtable: Fix __kernel_map_pages build error if NOMMU

riscv64-none-linux-gnu-ld: mm/page_alloc.o: in function `.L0 ': page_alloc.c:(.text+0xd34): undefined reference to `__kernel_map_pages' riscv64-none-linux-gnu-ld: page_alloc.c:(.text+0x104a): undefined reference to `__kernel_map_pages' riscv64-none-linux-gnu-ld: mm/page_alloc.o: in function

[PATCH 01/10] riscv: Fix unmet direct dependencies built based on SOC_VIRT

Fix unmet direct dependencies Warning and fix Kconfig indent. WARNING: unmet direct dependencies detected for POWER_RESET_SYSCON Depends on [n]: POWER_RESET [=n] && OF [=y] && HAS_IOMEM [=y] Selected by [y]: - SOC_VIRT [=y] WARNING: unmet direct dependencies detected for

[PATCH] kdb: Make the internal env 'KDBFLAGS' undefinable

'KDBFLAGS' is an internal variable of kdb, it is combined by 'KDBDEBUG' and state flags. But the user can define an environment variable named 'KDBFLAGS' too, so let's make it undefinable to avoid confusion. Signed-off-by: Wei Li --- kernel/debug/kdb/kdb_main.c | 3 ++- 1 file changed, 2

[PATCH 04/10] riscv: Fix print_vm_layout build error if NOMMU

arch/riscv/mm/init.c: In function ‘print_vm_layout’: arch/riscv/mm/init.c:68:37: error: ‘FIXADDR_START’ undeclared (first use in this function); arch/riscv/mm/init.c:69:20: error: ‘FIXADDR_TOP’ undeclared arch/riscv/mm/init.c:70:37: error: ‘PCI_IO_START’ undeclared arch/riscv/mm/init.c:71:20:

[PATCH 09/10] timer-riscv: Fix undefined riscv_time_val

ERROR: modpost: "riscv_time_val" [crypto/tcrypt.ko] undefined! Reported-by: Hulk Robot Signed-off-by: Kefeng Wang --- drivers/clocksource/timer-riscv.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/clocksource/timer-riscv.c b/drivers/clocksource/timer-riscv.c index

[PATCH 07/10] riscv: Make SYS_SUPPORTS_HUGETLBFS depends on MMU

HUGETLBFS only used when MMU enabled, add the dependence. Reported-by: Hulk Robot Signed-off-by: Kefeng Wang --- arch/riscv/Kconfig | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/riscv/Kconfig b/arch/riscv/Kconfig index 494e670520ae..d0010ed8e0f4 100644 --- a/arch/riscv/Kconfig +++

[PATCH 06/10] riscv: Disable ARCH_HAS_DEBUG_VIRTUAL if NOMMU

DEBUG_VIRTUAL should only used when MMU enabled, add the dependence. Signed-off-by: Kefeng Wang --- arch/riscv/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/riscv/Kconfig b/arch/riscv/Kconfig index 7da0a36a8df0..494e670520ae 100644 --- a/arch/riscv/Kconfig +++

[PATCH v2 0/3] kasan: memorize and print call_rcu stack

This patchset improves KASAN reports by making them to have call_rcu() call stack information. It is useful for programmers to solve use-after-free or double-free memory issue. The KASAN report was as follows(cleaned up slightly): BUG: KASAN: use-after-free in kasan_rcu_reclaim+0x58/0x60 Freed

[PATCH 10/10] riscv: mmiowb: Fix implicit declaration of function 'smp_processor_id'

In file included from ./../include/linux/compiler_types.h:68, from : ../include/asm-generic/mmiowb.h: In function ‘mmiowb_set_pending’: ../include/asm-generic/percpu.h:34:38: error: implicit declaration of function ‘smp_processor_id’; did you mean ‘raw_smp_processor_id’?

[PATCH v2 1/3] rcu/kasan: record and print call_rcu() call stack

This feature will record first and last call_rcu() call stack and print two call_rcu() call stack in KASAN report. When call_rcu() is called, we store the call_rcu() call stack into slub alloc meta-data, so that KASAN report can print rcu stack. It doesn't increase the cost of memory

[PATCH v2 2/3] kasan: record and print the free track

In order not to enlarge slub meta-data size, so we move free track from slub meta-data (struct kasan_alloc_meta) into freed object. Modification of struct kasan_alloc_meta: - add two call_rcu() stack into kasan_alloc_meta, size is 8 bytes. - remove free track from kasan_alloc_meta, size is 8

[PATCH v2 3/3] kasan: update documentation for generic kasan

Generic KASAN will support to record first and last call_rcu() call stack and print them in KASAN report. so we update documentation. Signed-off-by: Walter Wu Cc: Andrey Ryabinin Cc: Dmitry Vyukov Cc: Alexander Potapenko Cc: Jonathan Corbet --- Documentation/dev-tools/kasan.rst | 6 ++

Re: [PATCH 3/3] power: supply: max17040: Set rcomp value

Hi Sebastian, On 2020-05-10 1:08 p.m., Sebastian Reichel wrote: > Hi, > > On Mon, May 04, 2020 at 03:13:00PM -0700, Jonathan Bakker wrote: >> According to the datasheet (1), the rcomp parameter can >> vary based on the typical operating temperature and the >> battery chemistry. If provided,

[PATCH net v3] hinic: fix a bug of ndo_stop

if some function in ndo_stop interface returns failure because of hardware fault, must go on excuting rest steps rather than return failure directly, otherwise will cause memory leak.And bump the timeout for SET_FUNC_STATE to ensure that cmd won't return failure when hw is busy. Otherwise hw may

Re: [PATCH RFC tip/core/rcu 09/16] rcu-tasks: Add an RCU-tasks rude variant

On Mon, May 11, 2020 at 08:06:29AM +0800, Lai Jiangshan wrote: > On Sun, May 10, 2020 at 11:49 PM Paul E. McKenney wrote: > > > > On Sun, May 10, 2020 at 05:59:27PM +0800, Lai Jiangshan wrote: > > > On Tue, Mar 17, 2020 at 6:03 AM Steven Rostedt > > > wrote: > > > > > > > > On Mon, 16 Mar 2020

Re: [PATCH v2 3/3] iio: cros_ec_light: Add support for RGB sensor

Hi Gwendal, Thank you for the patch! Yet something to improve: [auto build test ERROR on iio/togreg] [also build test ERROR on chrome-platform-linux/for-next linus/master v5.7-rc5 next-20200508] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system.

Re: [PATCH net-next 3/5] net: hns3: provide .get_cmdq_stat interface for the client

On Mon, 11 May 2020 08:13:06 +0800 tanhuazhong wrote: > On 2020/5/10 4:48, Jakub Kicinski wrote: > > On Sat, 9 May 2020 17:27:39 +0800 Huazhong Tan wrote: > >> diff --git a/drivers/net/ethernet/hisilicon/hns3/hnae3.h > >> b/drivers/net/ethernet/hisilicon/hns3/hnae3.h > >> index 5602bf2..7506cab

Re: [PATCH net-next 0/5] net: hns3: misc updates for -next

On Sat, 9 May 2020 17:27:36 +0800 Huazhong Tan wrote: > This patchset includes some misc updates for the HNS3 ethernet driver. > > #1 & #2 add two cleanups. > #3 provides an interface for the client to query the CMDQ's status. > #4 adds a little optimization about debugfs. > #5 prevents 1000M

[PATCH][V3] arm64: perf: Get the wrong PC value in REGS_ABI_32 mode

Modified the patch subject and the change description. PC value is get from regs[15] in REGS_ABI_32 mode, but correct PC is regs->pc(regs[PERF_REG_ARM64_PC]) in arm64 kernel, which caused that perf can not parser the backtrace of app with dwarf mode in the 32bit system and 64bit kernel.

Re: [PATCH] drm: vmwgfx: include linux/highmem.h

On Sat, May 09, 2020 at 12:01:31AM +0200, Arnd Bergmann wrote: > In order to call kmap_atomic() etc, we need to include linux/highmem.h: > > drivers/gpu/drm/vmwgfx/vmwgfx_blit.c: In function 'vmw_bo_cpu_blit_line': > drivers/gpu/drm/vmwgfx/vmwgfx_blit.c:377:4: error: implicit declaration of >

[PATCH v5 02/16] powerpc/watchpoint: Add SPRN macros for second DAWR

Power10 is introducing second DAWR. Add SPRN_ macros for the same. Signed-off-by: Ravi Bangoria Reviewed-by: Michael Neuling --- arch/powerpc/include/asm/reg.h | 2 ++ 1 file changed, 2 insertions(+) diff --git a/arch/powerpc/include/asm/reg.h b/arch/powerpc/include/asm/reg.h index

[PATCH v5 01/16] powerpc/watchpoint: Rename current DAWR macros

Power10 is introducing second DAWR. Use real register names from ISA for current macros: s/SPRN_DAWR/SPRN_DAWR0/ s/SPRN_DAWRX/SPRN_DAWRX0/ Signed-off-by: Ravi Bangoria Reviewed-by: Michael Neuling --- arch/powerpc/include/asm/reg.h | 4 ++-- arch/powerpc/kernel/dawr.c

[PATCH v5 05/16] powerpc/watchpoint: Provide DAWR number to set_dawr

Introduce new parameter 'nr' to set_dawr() which indicates which DAWR should be programed. Signed-off-by: Ravi Bangoria Reviewed-by: Michael Neuling --- arch/powerpc/include/asm/hw_breakpoint.h | 4 ++-- arch/powerpc/kernel/dawr.c | 15 ++-

[PATCH v5 06/16] powerpc/watchpoint: Provide DAWR number to __set_breakpoint

Introduce new parameter 'nr' to __set_breakpoint() which indicates which DAWR should be programed. Also convert current_brk variable to an array. Signed-off-by: Ravi Bangoria Reviewed-by: Michael Neuling --- arch/powerpc/include/asm/debug.h | 2 +-

[PATCH v5 04/16] powerpc/watchpoint/ptrace: Return actual num of available watchpoints

User can ask for num of available watchpoints(dbginfo.num_data_bps) using ptrace(PPC_PTRACE_GETHWDBGINFO). Return actual number of available watchpoints on the machine rather than hardcoded 1. Signed-off-by: Ravi Bangoria Reviewed-by: Michael Neuling ---

[PATCH v5 00/16] powerpc/watchpoint: Preparation for more than one watchpoint

So far, powerpc Book3S code has been written with an assumption of only one watchpoint. But Power10[1] is introducing second watchpoint register (DAWR). Even though this patchset does not enable 2nd DAWR, it makes the infrastructure ready so that enabling 2nd DAWR should just be a matter of

[PATCH v5 03/16] powerpc/watchpoint: Introduce function to get nr watchpoints dynamically

So far we had only one watchpoint, so we have hardcoded HBP_NUM to 1. But Power10 is introducing 2nd DAWR and thus kernel should be able to dynamically find actual number of watchpoints supported by hw it's running on. Introduce function for the same. Also convert HBP_NUM macro to HBP_NUM_MAX,

[PATCH v5 07/16] powerpc/watchpoint: Get watchpoint count dynamically while disabling them

Instead of disabling only one watchpoint, get num of available watchpoints dynamically and disable all of them. Signed-off-by: Ravi Bangoria Reviewed-by: Michael Neuling --- arch/powerpc/include/asm/hw_breakpoint.h | 16 1 file changed, 8 insertions(+), 8 deletions(-) diff

[PATCH v5 12/16] powerpc/watchpoint: Use builtin ALIGN*() macros

Currently we calculate hw aligned start and end addresses manually. Replace them with builtin ALIGN_DOWN() and ALIGN() macros. So far end_addr was inclusive but this patch makes it exclusive (by avoiding -1) for better readability. Suggested-by: Christophe Leroy Signed-off-by: Ravi Bangoria

[PATCH v5 11/16] powerpc/watchpoint: Introduce is_ptrace_bp() function

Introduce is_ptrace_bp() function and move the check inside the function. It will be utilize more in later set of patches. Signed-off-by: Ravi Bangoria Reviewed-by: Michael Neuling --- arch/powerpc/kernel/hw_breakpoint.c | 7 ++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git

[PATCH v5 14/16] powerpc/watchpoint: Don't allow concurrent perf and ptrace events

With Book3s DAWR, ptrace and perf watchpoints on powerpc behaves differently. Ptrace watchpoint works in one-shot mode and generates signal before executing instruction. It's ptrace user's job to single-step the instruction and re-enable the watchpoint. OTOH, in case of perf watchpoint, kernel

[PATCH v5 08/16] powerpc/watchpoint: Disable all available watchpoints when !dawr_force_enable

Instead of disabling only first watchpoint, disable all available watchpoints while clearing dawr_force_enable. Callback function is used only for disabling watchpoint, rename it to disable_dawrs_cb(). And null_brk parameter is not really required while disabling watchpoint, remove it.

linux-next: manual merge of the ipsec-next tree with Linus' tree

Hi all, Today's linux-next merge of the ipsec-next tree got conflicts in: net/ipv4/xfrm4_output.c net/ipv6/xfrm6_output.c between commit: 0c922a4850eb ("xfrm: Always set XFRM_TRANSFORMED in xfrm{4,6}_output_finish") from Linus' tree and commit: 2ab6096db2f1 ("xfrm: remove

[PATCH v5 16/16] powerpc/watchpoint/xmon: Support 2nd DAWR

Add support for 2nd DAWR in xmon. With this, we can have two simultaneous breakpoints from xmon. Signed-off-by: Ravi Bangoria Reviewed-by: Michael Neuling --- arch/powerpc/xmon/xmon.c | 101 ++- 1 file changed, 69 insertions(+), 32 deletions(-) diff --git

[PATCH v5 09/16] powerpc/watchpoint: Convert thread_struct->hw_brk to an array

So far powerpc hw supported only one watchpoint. But Power10 is introducing 2nd DAWR. Convert thread_struct->hw_brk into an array. Signed-off-by: Ravi Bangoria Reviewed-by: Michael Neuling --- arch/powerpc/include/asm/processor.h | 2 +- arch/powerpc/kernel/process.c | 60

[PATCH v5 15/16] powerpc/watchpoint/xmon: Don't allow breakpoint overwriting

Xmon allows overwriting breakpoints because it's supported by only one DAWR. But with multiple DAWRs, overwriting becomes ambiguous or unnecessary complicated. So let's not allow it. Signed-off-by: Ravi Bangoria Reviewed-by: Michael Neuling --- arch/powerpc/xmon/xmon.c | 4 1 file

[PATCH v5 10/16] powerpc/watchpoint: Use loop for thread_struct->ptrace_bps

ptrace_bps is already an array of size HBP_NUM_MAX. But we use hardcoded index 0 while fetching/updating it. Convert such code to loop over array. ptrace interface to use multiple watchpoint remains same. eg: two PPC_PTRACE_SETHWDEBUG calls will create two watchpoint if underneath hw supports it.

[PATCH v5 13/16] powerpc/watchpoint: Prepare handler to handle more than one watcnhpoint

Currently we assume that we have only one watchpoint supported by hw. Get rid of that assumption and use dynamic loop instead. This should make supporting more watchpoints very easy. With more than one watchpoint, exception handler needs to know which DAWR caused the exception, and hw currently

linux-next: build warning after merge of the ipsec-next tree

Hi all, After merging the ipsec-next tree, today's linux-next build (arm multi_v7_defconfig) produced this warning: net/ipv4/xfrm4_output.c: In function '__xfrm4_output': net/ipv4/xfrm4_output.c:19:21: warning: unused variable 'x' [-Wunused-variable] 19 | struct xfrm_state *x =

Re: [PATCH net v3] hinic: fix a bug of ndo_stop

On Sun, 10 May 2020 19:01:08 + Luo bin wrote: > if some function in ndo_stop interface returns failure because of > hardware fault, must go on excuting rest steps rather than return > failure directly, otherwise will cause memory leak.And bump the > timeout for SET_FUNC_STATE to ensure that

Re: [PATCH v2 00/91] drm/vc4: Support BCM2711 Display Pipelin

Jian-Hong Pan 於 2020年5月8日 週五 下午2:20寫道： > > Maxime Ripard 於 2020年5月8日 週五 上午1:22寫道： > > > > On Mon, May 04, 2020 at 02:35:08PM +0800, Jian-Hong Pan wrote: > > > Maxime Ripard 於 2020年4月29日 週三 上午12:21寫道： > > > > > > > > Hi, > > > > > > > > On Mon, Apr 27, 2020 at 03:23:42PM +0800, Jian-Hong Pan

Re: [PATCH v8 09/10] scsi: ufs-exynos: add UFS host support for Exynos SoCs

On 5/10/20 7:00 PM, Alim Akhtar wrote: > diff --git a/drivers/scsi/ufs/Kconfig b/drivers/scsi/ufs/Kconfig > index e2005aeddc2d..cc7e29c8c24f 100644 > --- a/drivers/scsi/ufs/Kconfig > +++ b/drivers/scsi/ufs/Kconfig > @@ -160,3 +160,15 @@ config SCSI_UFS_BSG > > Select this if you need a

Re: [PATCH v2 4/6] dmaengine: dw: Print warning if multi-block is unsupported

On Fri, May 08, 2020 at 10:06:22PM +0300, Andy Shevchenko wrote: > On Fri, May 08, 2020 at 12:53:34PM +0100, Mark Brown wrote: > > On Fri, May 08, 2020 at 02:26:04PM +0300, Andy Shevchenko wrote: > > > On Fri, May 08, 2020 at 01:53:02PM +0300, Serge Semin wrote: > > > > > > Multi-block support

Re: [PATCH 2/5] exec: Directly call security_bprm_set_creds from __do_execve_file

On Sat, May 09, 2020 at 02:41:17PM -0500, Eric W. Biederman wrote: > > Now that security_bprm_set_creds is no longer responsible for calling > cap_bprm_set_creds, security_bprm_set_creds only does something for > the primary file that is being executed (not any interpreters it may > have).

Re: [PATCH V3 2/3] mm/hugetlb: Define a generic fallback for is_hugepage_only_range()

On 05/09/2020 03:52 AM, Mike Kravetz wrote: > On 5/7/20 8:07 PM, Anshuman Khandual wrote: >> There are multiple similar definitions for is_hugepage_only_range() on >> various platforms. Lets just add it's generic fallback definition for >> platforms that do not override. This help reduce code

Re: [PATCH V2 6/8] phy: tegra: xusb: Add support for charger detect

On 04-05-2020 21:20, Thierry Reding wrote: On Mon, May 04, 2020 at 02:32:51PM +0530, Nagarjuna Kristam wrote: On 28-04-2020 16:25, Thierry Reding wrote: On Wed, Apr 15, 2020 at 01:55:06PM +0530, Nagarjuna Kristam wrote: [...] diff --git a/drivers/phy/tegra/xusb-tegra-cd.c

linux-next: manual merge of the crypto tree with Linus' tree

Hi all, Today's linux-next merge of the crypto tree got conflicts in: crypto/lrw.c crypto/xts.c between commit: 1a263ae60b04 ("gcc-10: avoid shadowing standard library 'free()' in crypto") from Linus' tree and commit: d099ea6e6fde ("crypto - Avoid free() namespace collision") from

Re: [PATCH v2 0/5] mtd: spi-nor: Add support for Octal 8D-8D-8D mode

Hi Vignesh, > >>> > >>> Our mx25uw51245g supports BFPT DWORD-18,19 and 20 data and xSPI > > profile > >>> 1.0, > >>> and it comply with BFPT DWORD-19, octal mode enable sequences by write > > CFG > >>> Reg2 > >>> with instruction 0x72. Therefore, I can't apply your patches. > >> > >> I

Re: [PATCH v6 5/9] w1_therm: adding resolution sysfs entry

Hi, The kernel-doc comment changes look good. Thanks for doing that. On 5/10/20 7:17 AM, Akira Shimahara wrote: > diff --git a/drivers/w1/slaves/w1_therm.c b/drivers/w1/slaves/w1_therm.c > index 08579dc..b1734ae 100644 > --- a/drivers/w1/slaves/w1_therm.c > +++ b/drivers/w1/slaves/w1_therm.c

Re: [PATCH v6 1/9] w1_therm: adding code comments and code reordering

Hi, A few more comments here (inline): On 5/10/20 7:15 AM, Akira Shimahara wrote: > drivers/w1/slaves/w1_therm.c | 398 --- > 1 file changed, 232 insertions(+), 166 deletions(-) > > diff --git a/drivers/w1/slaves/w1_therm.c b/drivers/w1/slaves/w1_therm.c >

[PATCH] driver/hwmon/nct6775: Use kobj_to_dev() API

Use kobj_to_dev() API instead of container_of(). Signed-off-by: zhouchuangao --- drivers/hwmon/nct6775.c | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/drivers/hwmon/nct6775.c b/drivers/hwmon/nct6775.c index 7efa6bf..e7e1ddc 100644 --- a/drivers/hwmon/nct6775.c

linux-next: build warning after merge of the drm tree

Hi all, After merging the drm tree, today's linux-next build (x86_64 allmodconfig) produced this warning: WARNING: modpost: missing MODULE_LICENSE() in drivers/gpu/drm/panel/panel-visionox-rm69299.o Introduced by commit c7f66d32dd43 ("drm/panel: add support for rm69299 visionox panel") --

[PATCH 1/2] kbuild: add this-makefile as a shorthand for $(lastword $(MAKEFILE_LIST))

Make it clearer, and self-documenting. Signed-off-by: Masahiro Yamada --- Makefile | 6 -- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/Makefile b/Makefile index 119a08c90abb..1a4977ad7cd9 100644 --- a/Makefile +++ b/Makefile @@ -157,12 +157,14 @@ MAKEFLAGS +=

[PATCH 2/2] kbuild: error out if targets prefixed with '__' are directly run

Some targets are internal-use only. It is tedious to care about "what if __build_one_by_one is contained in $(MAKECMDGOALS)?" etc. Prefix internal targets with double underscores. Stop parsing Makefile if they are directly run. Signed-off-by: Masahiro Yamada --- Makefile | 23

Re: [PATCH V3 1/3] arm64/mm: Drop __HAVE_ARCH_HUGE_PTEP_GET

On 05/09/2020 03:39 AM, Mike Kravetz wrote: > On 5/7/20 8:07 PM, Anshuman Khandual wrote: >> Platform specific huge_ptep_get() is required only when fetching the huge >> PTE involves more than just dereferencing the page table pointer. This is >> not the case on arm64 platform. Hence

Re: linux-next: build warning after merge of the drm tree

On 5/10/20 8:47 PM, Stephen Rothwell wrote: > Hi all, > > After merging the drm tree, today's linux-next build (x86_64 allmodconfig) > produced this warning: > > WARNING: modpost: missing MODULE_LICENSE() in > drivers/gpu/drm/panel/panel-visionox-rm69299.o > > Introduced by commit > >

Re: [LKP] Re: [pipe] f2af7d90e2: xfstests.btrfs.052.fail

Hi Matthew with a quick look into the dmesg looks this commit broke the preparation of LKP tests [   32.677588] install debs round two: dpkg -i --force-confdef --force-depends /opt/deb/gawk_1%3a4.1.4+dfsg-1_amd64.deb [ 32.677593]- [   32.697180] tar: ./control: Cannot write: Invalid argument

[PATCH] kbuild: make module name conflict fatal error

I think all the warnings have been fixed by now. Make it a fatal error. Check it before modpost because we need to stop building *.ko files. Also, pass modules.order via a script parameter. Signed-off-by: Masahiro Yamada --- Makefile | 7 +-- scripts/modules-check.sh | 16

linux-next: build failure after merge of the block tree

Hi all, After merging the block tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/block/aoe/aoeblk.c: In function 'aoeblk_gdalloc': drivers/block/aoe/aoeblk.c:410:21: error: 'struct backing_dev_info' has no member named 'name' 410 | q->backing_dev_info->name =

Re: [patch V4 part 3 12/29] x86/entry/common: Provide idtentry_enter/exit()

On Tue, May 5, 2020 at 7:15 AM Thomas Gleixner wrote: > > Provide functions which handle the low level entry and exit similiar to > enter/exit from user mode. > > + > +/** > + * idtentry_exit - Common code to handle return from exceptions > + * @regs: Pointer to pt_regs (exception entry

[PATCH] vfio/pci: fix memory leaks of eventfd ctx

Finished a qemu-kvm (-device vfio-pci,host=0001:01:00.0) triggers a few memory leaks after a while because vfio_pci_set_ctx_trigger_single() calls eventfd_ctx_fdget() without the matching eventfd_ctx_put() later. Fix it by calling eventfd_ctx_put() for those memory in vfio_pci_release() before

[RFC][PATCHES] uaccess-related stuff in net/*

Assorted uaccess-related work in net/*. First, there's getting rid of compat_alloc_user_space() mess in MCAST_... [gs]etsockopt() - no need to play with copying to/from temporary object on userland stack, etc., when ->compat_[sg]etsockopt() instances in question can easly do everything

[PATCH 02/19] compat_ip{,v6}_setsockopt(): enumerate MCAST_... options explicitly

From: Al Viro We want to check if optname is among the MCAST_... ones; do that as an explicit switch. Signed-off-by: Al Viro --- net/ipv4/ip_sockglue.c | 10 +- net/ipv6/ipv6_sockglue.c | 10 +- 2 files changed, 18 insertions(+), 2 deletions(-) diff --git

<    1   2   3   4   5   6   >