Re: [PATCH v4 4/6] drm/sprd: add Unisoc's drm display controller driver

Hi, On Fri, Apr 09, 2021 at 09:35:07PM +0800, Kevin Tang wrote: > > > > > + } > > > > > + > > > > > + return MODE_OK; > > > > > +} > > > > > + > > > > > +static void sprd_crtc_atomic_enable(struct drm_crtc *crtc, > > > > > +struct drm_atomic_state *state) >

Re: [PATCH 2/7] stm class: Replace uuid_t with plain u8 uuid[16]

On Thu, Apr 15, 2021 at 11:48:48AM +0300, Andy Shevchenko wrote: > On Thu, Apr 15, 2021 at 11:35 AM Greg Kroah-Hartman > wrote: > > > > On Wed, Apr 14, 2021 at 10:14:34PM +0300, Alexander Shishkin wrote: > > > Greg Kroah-Hartman writes: > > > > > > >> Using raw buffer APIs against uuid_t /

[PATCH] stm class: Use correct UUID APIs

From: Andy Shevchenko It appears that the STM code didn't manage to accurately decypher the delicate inner workings of an alternative thought process behind the UUID API and directly called generate_random_uuid() that clearly needs to be a static function in lib/uuid.c. At the same time, said

Re: [PATCH v2 3/6] dt-bindings: phy: Add binding for TI TCAN104x CAN transceivers

On 15.04.2021 14:41:57, Aswath Govindraju wrote: > +++ b/Documentation/devicetree/bindings/phy/ti,tcan104x-can.yaml > > Can you create a maintainers entry for this file with your address? > > I don't see this being done for other phy yamls in the > Documentation/devicetree/bindings/phy

[PATCH] infiniband: ulp: Remove unnecessary struct declaration

struct ipoib_cm_tx is defined at 245th line. And the definition is independent on the MACRO. The declaration here is unnecessary. Remove it. Signed-off-by: Wan Jiabing --- drivers/infiniband/ulp/ipoib/ipoib.h | 2 -- 1 file changed, 2 deletions(-) diff --git

Re: [PATCH v18 2/2] ufs: sysfs: Resume the proper scsi device

On 14/04/21 9:58 pm, Asutosh Das wrote: > Resumes the actual scsi device the unit descriptor of which > is being accessed instead of the hba alone. > > Reviewed-by: Can Guo > Signed-off-by: Asutosh Das Reviewed-by: Adrian Hunter > --- > drivers/scsi/ufs/ufs-sysfs.c | 24

[PATCH v2 2/2] phy: nxp-c45: add driver for tja1103

Add driver for tja1103 driver and for future NXP C45 PHYs. Signed-off-by: Radu Pirea (NXP OSS) --- MAINTAINERS | 6 + drivers/net/phy/Kconfig | 6 + drivers/net/phy/Makefile | 1 + drivers/net/phy/nxp-c45-tja11xx.c | 607

[PATCH v2 1/2] net: phy: add genphy_c45_pma_suspend/resume

Add generic PMA suspend and resume callback functions for C45 PHYs. Signed-off-by: Radu Pirea (NXP OSS) --- drivers/net/phy/phy-c45.c | 43 +++ include/linux/phy.h | 2 ++ 2 files changed, 45 insertions(+) diff --git a/drivers/net/phy/phy-c45.c

Re: [PATCH 2/2] iommu/amd: Remove performance counter pre-initialization test

David, On 4/14/2021 10:33 PM, David Coe wrote: Hi Suravee! I've re-run your revert+update patch on Ubuntu's latest kernel 5.11.0-14 partly to check my mailer's 'mangling' hadn't also reached the code! There are 3 sets of results in the attachment, all for the Ryzen 2400G. The as-distributed

[PATCH v2 0/2] TJA1103 driver

Hi, This small series adds the TJA1103 PHY driver. Changes in v2: - implemented genphy_c45_pma_suspend/genphy_c45_pma_suspend - set default internal delays set to 2ns(90 degrees) - added "VEND1_" prefix to the register definitions - disable rxid in case of txid - disable txid in case of

Re:Re: [PATCH V3] watchdog: mtk: support pre-timeout when the bark irq is available

>On 4/14/21 4:48 AM, Wang Qing wrote: >> Use the bark interrupt as the pretimeout notifier if available. >> >> By default, the pretimeout notification shall occur one second earlier >> than the timeout. >> >> V2: >> - panic() by default if WATCHDOG_PRETIMEOUT_GOV is not enabled. >> >> V3: >> -

[PATCH net-next] net: ethernet: mediatek: fix typo in offload code

.key_offset was assigned to .head_offset instead. Fix the typo. Fixes: 502e84e2382d ("net: ethernet: mtk_eth_soc: add flow offloading support") Signed-off-by: DENG Qingfang --- drivers/net/ethernet/mediatek/mtk_ppe_offload.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

Re: [PATCH v2 1/3] mmc: sdhci-s3c: simplify getting of_device_id match data

On 15.04.2021 10:44, Krzysztof Kozlowski wrote: Use of_device_get_match_data() to make the code slightly smaller and to remove the of_device_id table forward declaration. Signed-off-by: Krzysztof Kozlowski Reviewed-by: Sylwester Nawrocki

Re: [PATCH bpf-next v3 6/6] selftests/bpf: Add a series of tests for bpf_snprintf

On Thu, Apr 15, 2021 at 12:16 AM Andrii Nakryiko wrote: > > On Wed, Apr 14, 2021 at 2:21 AM Florent Revest wrote: > > > > On Wed, Apr 14, 2021 at 1:21 AM Andrii Nakryiko > > wrote: > > > > > > On Mon, Apr 12, 2021 at 8:38 AM Florent Revest > > > wrote: > > > > > > > > This exercises most of

Re: [RFC v4 net-next 1/4] net: phy: add MediaTek PHY driver

On Tue, Apr 13, 2021 at 02:12:59PM +0100, Russell King - ARM Linux admin wrote: > On Tue, Apr 13, 2021 at 11:59:20AM +0800, DENG Qingfang wrote: > > Within 12 hours, I got some spontaneous link down/ups when EEE is enabled: > > > > [16334.236233] mt7530 mdio-bus:1f wan: Link is Down > >

Re: [PATCH] coresight: add support to enable more coresight paths

Hi On 15/04/2021 10:33, Tao Zhang wrote: Current coresight implementation only supports enabling source ETMs or STM. This patch adds support to enable more kinds of coresight source to sink paths. We build a path from source to sink when any source is enabled and store it in a list. When the

[PATCH 03/13] ARM: dts: stm32: fix timer nodes on STM32 MCU to prevent warnings

Prevent warning seen with "make dtbs_check W=1" command: Warning (avoid_unnecessary_addr_size): /soc/timers@40001c00: unnecessary address-cells/size-cells without "ranges" or child "reg" property Signed-off-by: Alexandre Torgue diff --git a/arch/arm/boot/dts/stm32f429.dtsi

[PATCH 05/13] ARM: dts: stm32: update pinctrl node name on STM32 MCU to prevent warnings

Update node name to avoid a DT schema validation issue seen with "make dtbs_check W=1". It also cleans picntrl dtsi files for f429/f469 MCU. Signed-off-by: Alexandre Torgue diff --git a/arch/arm/boot/dts/stm32f4-pinctrl.dtsi b/arch/arm/boot/dts/stm32f4-pinctrl.dtsi index

[PATCH 04/13] dt-bindings: mfd: stm32-timers: remove #address/size cells from required properties

address-cells and size-cells can't be declared as "required" properties as they are not needed if subnodes don't have a "reg" entry. Signed-off-by: Alexandre Torgue diff --git a/Documentation/devicetree/bindings/mfd/st,stm32-timers.yaml

[PATCH 07/13] ARM: dts: stm32: move stmmac axi config in ethernet node on stm32mp15

It fixes the following warning seen running "make dtbs_check W=1" Warning (simple_bus_reg): /soc/stmmac-axi-config: missing or empty reg/ranges property Signed-off-by: Alexandre Torgue diff --git a/arch/arm/boot/dts/stm32mp151.dtsi b/arch/arm/boot/dts/stm32mp151.dtsi index

[PATCH 08/13] dt-bindings: net: document ptp_ref clk in dwmac

ptp_ref clk has been added in DT but not documented which makes yaml validation failed: ethernet@5800a000: clocks: [[6, 105], [6, 103], [6, 104], [6, 123], [6, 169], [6, 112]] is too long ethernet@5800a000: clock-names: ['stmmaceth', 'mac-clk-tx', 'mac-clk-rx', 'eth-ck', 'ptp_ref', 'ethstp'] is

[PATCH 12/13] ARM: dts: stm32: fix DSI port node on STM32MP15

Running "make dtbs_check W=1", some warnings are reported concerning DSI. This patch reorder DSI nodes to avoid: soc/dsi@5a00: unnecessary #address-cells/#size-cells without "ranges" or child "reg" property Signed-off-by: Alexandre Torgue diff --git a/arch/arm/boot/dts/stm32mp157.dtsi

[PATCH 06/13] ARM: dts: stm32: fix i2c node name on stm32f746 to prevent warnings

Replace upper case by lower case in i2c nodes name. Signed-off-by: Alexandre Torgue diff --git a/arch/arm/boot/dts/stm32f746.dtsi b/arch/arm/boot/dts/stm32f746.dtsi index 72c1b76684b6..014b416f57e6 100644 --- a/arch/arm/boot/dts/stm32f746.dtsi +++ b/arch/arm/boot/dts/stm32f746.dtsi @@ -360,9

[PATCH 10/13] dt-bindings: mfd: add vref_ddr-supply to st,stpmic1 yaml

Add vref_ddr-supply to the STPMIC1 regulators supplies pattern list. Signed-off-by: Alexandre Torgue diff --git a/Documentation/devicetree/bindings/mfd/st,stpmic1.yaml b/Documentation/devicetree/bindings/mfd/st,stpmic1.yaml index 305123e74a58..ffc32d209496 100644 ---

[PATCH 02/13] ARM: dts: stm32: fix RCC node name on stm32f429 MCU

This prevent warning observed with "make dtbs_check W=1" Warning (simple_bus_reg): /soc/rcc@40023810: simple-bus unit address format error, expected "40023800" Signed-off-by: Alexandre Torgue diff --git a/arch/arm/boot/dts/stm32f429.dtsi b/arch/arm/boot/dts/stm32f429.dtsi index

[PATCH 00/13] ARM: dts: stm32: fix "make dtbs_check W=1" round1

Hi, First round to cleanup warnings and yaml validation issues seen running "make dtbs_check W=1" command for STM32 platform. It concerns all SoC (MCU: f429/429, f746/769, h743, MPU) and all boards (ST reference boards, DH, Engicam, LxA ...). Main fixes are done in device tree files but some

[PATCH 09/13] ARM: dts: stm32: fix stpmic node for stm32mp1 boards

On some STM32 MP15 boards, stpmic node is not correct which generates warnings running "make dtbs_check W=1" command. Issues are: -"regulator-active-discharge" is not a boolean but an uint32. -"regulator-over-current-protection" is not a valid entry for vref_ddr. -LDO4 has a fixed voltage (3v3)

[PATCH 13/13] ARM: dts: stm32: fix ltdc pinctrl on microdev2.0-of7

It prevents the following warning: pin-controller@50002000: 'ltdc' does not match any of the regexes: '-[0-9]*$', '^gpio@[0-9a-f]*$', 'pinctrl-[0-9]+' Signed-off-by: Alexandre Torgue diff --git a/arch/arm/boot/dts/stm32mp157a-microgea-stm32mp1-microdev2.0-of7.dts

[PATCH 01/13] ARM: dts: stm32: fix gpio-keys node on STM32 MCU boards

Fix following warning observed with "make dtbs_check W=1" command. It concerns f429 eval and disco boards, f769 disco board. Warning (unit_address_vs_reg): /gpio_keys/button@0: node has a unit name, but no reg or ranges property Signed-off-by: Alexandre Torgue diff --git

[PATCH 11/13] ARM: dts: stm32: fix LTDC port node on STM32 MCU ad MPU

Running "make dtbs_check W=1", some warnings are reported concerning LTDC port subnode: /soc/display-controller@5a001000/port: unnecessary #address-cells/#size-cells without "ranges" or child "reg" property /soc/display-controller@5a001000/port: graph node has single child node 'endpoint',

[PATCH v8 7/7] mm,page_alloc: Drop unnecessary checks from pfn_range_valid_contig

pfn_range_valid_contig() bails out when it finds an in-use page or a hugetlb page, among other things. We can drop the in-use page check since __alloc_contig_pages can migrate away those pages, and the hugetlb page check can go too since isolate_migratepages_range is now capable of dealing with

[PATCH v8 6/7] mm: Make alloc_contig_range handle in-use hugetlb pages

alloc_contig_range() will fail if it finds a HugeTLB page within the range, without a chance to handle them. Since HugeTLB pages can be migrated as any LRU or Movable page, it does not make sense to bail out without trying. Enable the interface to recognize in-use HugeTLB pages so we can migrate

[PATCH v8 5/7] mm: Make alloc_contig_range handle free hugetlb pages

alloc_contig_range will fail if it ever sees a HugeTLB page within the range we are trying to allocate, even when that page is free and can be easily reallocated. This has proved to be problematic for some users of alloc_contic_range, e.g: CMA and virtio-mem, where those would fail the call even

[PATCH v8 1/7] mm,page_alloc: Bail out earlier on -ENOMEM in alloc_contig_migrate_range

Currently, __alloc_contig_migrate_range can generate -EINTR, -ENOMEM or -EBUSY, and report them down the chain. The problem is that when migrate_pages() reports -ENOMEM, we keep going till we exhaust all the try-attempts (5 at the moment) instead of bailing out. migrate_pages() bails out right

[PATCH v8 2/7] mm,compaction: Let isolate_migratepages_{range,block} return error codes

Currently, isolate_migratepages_{range,block} and their callers use a pfn == 0 vs pfn != 0 scheme to let the caller know whether there was any error during isolation. This does not work as soon as we need to start reporting different error codes and make sure we pass them down the chain, so they

[PATCH v8 3/7] mm,hugetlb: Drop clearing of flag from prep_new_huge_page

Pages allocated after boot get its private field cleared by means of post_alloc_hook(). Pages allocated during boot, that is directly from the memblock allocator, get cleared by paging_init()->..->memmap_init_zone->..->__init_single_page() before any memblock allocation. Based on this ground, let

[PATCH v8 0/7] Make alloc_contig_range handle Hugetlb pages

So, after Mike's work [1] has gone in, here is a new version of top. NOTE: If you are going to try out this patchset, be aware of [2]. You should fix that up before any testing. [1] https://patchwork.kernel.org/project/linux-mm/cover/20210409205254.242291-1-mike.krav...@oracle.com/ [2]

[PATCH v8 4/7] mm,hugetlb: Split prep_new_huge_page functionality

Currently, prep_new_huge_page() performs two functions. It sets the right state for a new hugetlb, and increases the hstate's counters to account for the new page. Let us split its functionality into two separate functions, decoupling the handling of the counters from initializing a hugepage. The

[PATCH v3 04/24] ARM: at91: pm: check for different controllers in at91_pm_modes_init()

at91_pm_modes_init() checks for proper nodes in device tree and maps them accordingly. Up to SAMA7G5 all AT91 SoCs had the same mapping b/w power saving modes and different controllers needed in the final/first steps of suspend/resume. SAMA7G5 is not aligned with the old SoCs thus the code is

[PATCH v3 05/24] ARM: at91: pm: do not initialize pdev

There is no need to initialize pdev. Signed-off-by: Claudiu Beznea --- arch/arm/mach-at91/pm.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/arm/mach-at91/pm.c b/arch/arm/mach-at91/pm.c index 5a6ce1d88971..65e13769cf50 100644 --- a/arch/arm/mach-at91/pm.c +++

[PATCH v3 07/24] ARM: at91: pm: avoid push and pop on stack while memory is in self-refersh

For the previous AT91 RAM controller and self-refresh procedure this had no side effects. However, for SAMA7G5 the self-refresh procedure doesn't allow this anymore as the RAM controller ports are closed before switching it to self-refresh. This commits prepares the code for the following ones

[PATCH v3 00/24] ARM: at91: pm: add support for sama7g5

Hi, This series adds PM support for SAMA7G5. The standby, ulp0, ulp1, and backup modes are supported. Thank you, Claudiu Beznea Changes in v3: - drop: status = "okay" in patch 16/24 Changes in v2: - keep only the generic sama7_dt in patch 22/24 and adapt patch 23/24 - collected tags Claudiu

[PATCH v3 08/24] ARM: at91: pm: s/CONFIG_SOC_SAM9X60/CONFIG_HAVE_AT91_SAM9X60_PLL/g

Replace CONFIG_SOC_SAM9X60 with CONFIG_HAVE_AT91_SAM9X60_PLL as the SAM9X60's PLL is also present on SAMA7G5. Signed-off-by: Claudiu Beznea --- arch/arm/mach-at91/pm_suspend.S | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/arch/arm/mach-at91/pm_suspend.S

[PATCH v3 01/24] ARM: at91: pm: move pm_bu to soc_pm data structure

Move pm_bu to soc_pm data structure. Signed-off-by: Claudiu Beznea --- arch/arm/mach-at91/pm.c | 34 +- 1 file changed, 21 insertions(+), 13 deletions(-) diff --git a/arch/arm/mach-at91/pm.c b/arch/arm/mach-at91/pm.c index 90dcdfe3b3d0..e13ceef7ac9a 100644 ---

[PATCH v3 03/24] ARM: at91: pm: document at91_soc_pm structure

Document at91_soc_pm structure. Signed-off-by: Claudiu Beznea --- arch/arm/mach-at91/pm.c | 8 1 file changed, 8 insertions(+) diff --git a/arch/arm/mach-at91/pm.c b/arch/arm/mach-at91/pm.c index 3742a1fb76db..3029351ec78e 100644 --- a/arch/arm/mach-at91/pm.c +++

[PATCH v3 02/24] ARM: at91: pm: move the setup of soc_pm.bu->suspended

Move the setup of soc_pm.bu->suspended in platform_suspend::begin function so that the PMC code in charge with clocks suspend/resume to differentiate b/w standard PM mode and backup mode. Signed-off-by: Claudiu Beznea Reviewed-by: Alexandre Belloni --- arch/arm/mach-at91/pm.c | 15

[PATCH v3 06/24] ARM: at91: pm: use r7 instead of tmp1

Use r7 instead of tmp1 in macros. This prepares the filed for next commits. Signed-off-by: Claudiu Beznea --- arch/arm/mach-at91/pm_suspend.S | 18 -- 1 file changed, 12 insertions(+), 6 deletions(-) diff --git a/arch/arm/mach-at91/pm_suspend.S b/arch/arm/mach-at91/pm_suspend.S

Re: [PATCH v7 1/3] bio: limit bio max size

> On 4/12/21 7:55 PM, Changheun Lee wrote: > > +unsigned int bio_max_size(struct bio *bio) > > +{ > > + struct request_queue *q = bio->bi_bdev->bd_disk->queue; > > + > > + if (blk_queue_limit_bio_size(q)) > > + return blk_queue_get_max_sectors(q, bio_op(bio)) > > +

[gustavoars-linux:testing/warray-bounds] BUILD SUCCESS WITH WARNING 4695107c157dd670a5fc1b1d3ccbfdc440caca24

-at-cmd-is-out-of-the-bounds-of-referenced-subobject-feature-with-type-unsigned-char-at-offset |-- parisc-randconfig-r014-20210415 | `-- net-core-flow_dissector.c:warning:memcpy-offset-from-the-object-at-flow_keys-is-out-of-the-bounds-of-referenced-subobject-ipv6_src-with-type-__u32-aka-unsigned-int

Re: [PATCH v4 2/3] mm/slub, kunit: add a KUnit test for SLUB debugging functionality

On Thu, 15 Apr 2021 at 12:38, Vlastimil Babka wrote: > > On 4/15/21 12:10 PM, Oliver Glitta wrote: > > ut 13. 4. 2021 o 15:54 Marco Elver napísal(a): > >> > >> On Tue, 13 Apr 2021 at 12:07, wrote: > >> > From: Oliver Glitta > >> > > >> > SLUB has resiliency_test() function which is hidden

Re: [PATCH v2 1/1] mfd: intel_quark_i2c_gpio: Don't play dirty trick with const

On Wed, Apr 14, 2021 at 10:19:16PM +0100, Lee Jones wrote: > On Wed, 14 Apr 2021, Andy Shevchenko wrote: > > On Wed, Apr 14, 2021 at 06:13:19PM +0100, Lee Jones wrote: > > > On Fri, 26 Mar 2021, Lee Jones wrote: ... > > > Am I still missing patches from you Andy? > > > > Patches for fixes

Re: [PATCH v2 1/3] Drivers: hv: vmbus: Introduce and negotiate VMBus protocol version 5.3

> > @@ -234,6 +234,7 @@ static inline u32 hv_get_avail_to_write_percent( > > * 5 . 0 (Newer Windows 10) > > * 5 . 1 (Windows 10 RS4) > > * 5 . 2 (Windows Server 2019, RS5) > > + * 5 . 3 (Windows Server 2021) // FIXME: use proper version number/name > > The official name is now public

[PATCH v5 2/3] dt-bindings: pinctrl: Add binding for ZynqMP pinctrl driver

Adding documentation and dt-bindings file which contains MIO pin configuration defines for Xilinx ZynqMP pinctrl driver. Signed-off-by: Sai Krishna Potthuri Reviewed-by: Rob Herring --- .../bindings/pinctrl/xlnx,zynqmp-pinctrl.yaml | 336 ++

[PATCH v5 3/3] pinctrl: Add Xilinx ZynqMP pinctrl driver support

Adding pinctrl driver for Xilinx ZynqMP platform. This driver queries pin information from firmware and registers pin control accordingly. Signed-off-by: Sai Krishna Potthuri --- drivers/pinctrl/Kconfig | 14 + drivers/pinctrl/Makefile | 1 + drivers/pinctrl/pinctrl-zynqmp.c

[PATCH v5 1/3] firmware: xilinx: Add pinctrl support

Adding pinctrl support to query platform specific information (pins) from firmware. Signed-off-by: Sai Krishna Potthuri Acked-by: Michal Simek --- drivers/firmware/xilinx/zynqmp.c | 114 +++ include/linux/firmware/xlnx-zynqmp.h | 90 + 2 files

[PATCH v5 0/3] Add ZynqMP pinctrl driver

Add support for Xilinx ZynqMP pinctrl driver and also update the Xilinx firmware driver to support pinctrl functionality. This driver queries the pin information from the firmware and allow configuring the pins as per the request. changes in v5: - Used generic property 'power-source' instead of

[PATCH v5 3/6] KVM: arm64: Add mm_ops member for structure stage2_attr_data

Also add a mm_ops member for structure stage2_attr_data, since we will move I-cache maintenance for guest stage-2 to the permission path and as a result will need mm_ops for address transformation. Signed-off-by: Yanan Wang --- arch/arm64/kvm/hyp/pgtable.c | 10 ++ 1 file changed, 6

[PATCH v5 4/6] KVM: arm64: Provide invalidate_icache_range at non-VHE EL2

We want to move I-cache maintenance for the guest to the stage-2 page table code for performance improvement. Before it can work, we should first make function invalidate_icache_range available to non-VHE EL2 to avoid compiling or program running error, as pgtable.c is now linked into the non-VHE

[PATCH v5 5/6] KVM: arm64: Move I-cache flush to the fault handlers

In this patch, we move invalidation of I-cache to the fault handlers to avoid unnecessary I-cache maintenances. On the map path, invalidate the I-cache if we are going to create an executable stage-2 mapping for guest. And on the permission path, invalidate the I-cache if we are going to add an

[PATCH v5 6/6] KVM: arm64: Distinguish cases of memcache allocations completely

With a guest translation fault, the memcache pages are not needed if KVM is only about to install a new leaf entry into the existing page table. And with a guest permission fault, the memcache pages are also not needed for a write_fault in dirty-logging time if KVM is only about to update the

Re: [PATCH 3/5] s390: Get rid of oprofile leftovers

On Thu, Apr 15, 2021 at 11:47:26AM +0100, Marc Zyngier wrote: > On Thu, 15 Apr 2021 11:38:52 +0100, > Heiko Carstens wrote: > > > > On Wed, Apr 14, 2021 at 02:44:07PM +0100, Marc Zyngier wrote: > > > perf_pmu_name() and perf_num_counters() are unused. Drop them. > > > > > > Signed-off-by: Marc

Re: [PATCH v2 7/9] sched,debug: Convert sysctl sched_domains to debugfs

On 15/04/2021 11:06, Peter Zijlstra wrote: > On Tue, Apr 13, 2021 at 03:55:15PM +0100, Valentin Schneider wrote: >> On 12/04/21 12:14, Peter Zijlstra wrote: >>> Stop polluting sysctl, move to debugfs for SCHED_DEBUG stuff. >>> >>> Signed-off-by: Peter Zijlstra (Intel) >>> Reviewed-by: Dietmar

Re: [PATCH v3 5/5] mm/memcg: Optimize user context object stock access

On Thu, Apr 15, 2021 at 11:44:55AM +0200, Christoph Lameter wrote: > Would you please stop quoting the whole patch when you have nothing to say > about the details? It is enough to just respond without quoting. I was > looking through this trying to find something you said about individual >

Re: [PATCH 12/13] ARM: dts: stm32: fix DSI port node on STM32MP15

Hi Ahmad On 4/15/21 12:43 PM, Ahmad Fatoum wrote: Hi, On 15.04.21 12:10, Alexandre Torgue wrote: Running "make dtbs_check W=1", some warnings are reported concerning DSI. This patch reorder DSI nodes to avoid: soc/dsi@5a00: unnecessary #address-cells/#size-cells without "ranges" or child

Re: [PATCH v3] USB: Don't set USB_PORT_FEAT_SUSPEND on WD19's Realtek Hub

On Thu, Apr 15, 2021 at 07:48:56PM +0800, chris.c...@canonical.com wrote: > From: Chris Chiu > > Realtek Hub (0bda:5487) in Dell Dock WD19 sometimes fails to work > after the system resumes from suspend with remote wakeup enabled > device connected: > [ 1947.640907] hub 5-2.3:1.0:

Re: [PATCH v7 5/7] mm: Make alloc_contig_range handle free hugetlb pages

On Tue, Apr 13, 2021 at 03:40:18PM +0200, Michal Hocko wrote: > > + /* > > +* Call __prep_new_huge_page() to construct the hugetlb page, > > and > > +* enqueue it then to place it in the freelists. After this, > > +* counters are back on track. Free

Re: [PATCH] arm64: dts: marvell: armada-37xx: Set linux,pci-domain to zero

On Tuesday 13 April 2021 13:17:29 Rob Herring wrote: > On Mon, Apr 12, 2021 at 7:41 AM Pali Rohár wrote: > > > > Since commit 526a76991b7b ("PCI: aardvark: Implement driver 'remove' > > function and allow to build it as module") PCIe controller driver for > > Armada 37xx can be dynamically loaded

[PATCH] rtc: remove unused function

Fix the following clang warning: drivers/rtc/rtc-ds1511.c:108:1: warning: unused function 'rtc_write_alarm' [-Wunused-function]. Reported-by: Abaci Robot Signed-off-by: Jiapeng Chong --- drivers/rtc/rtc-ds1511.c | 6 -- 1 file changed, 6 deletions(-) diff --git a/drivers/rtc/rtc-ds1511.c

[PATCH][next] can: etas_es58x: Fix missing null check on netdev pointer

From: Colin Ian King There is an assignment to *netdev that is can potentially be null but the null check is checking netdev and not *netdev as intended. Fix this by adding in the missing * operator. Addresses-Coverity: ("Dereference before null check") Fixes: 8537257874e9 ("can: etas_es58x:

[PATCH] drm/rockchip: remove unused function

Fix the following clang warning: drivers/gpu/drm/rockchip/dw-mipi-dsi-rockchip.c:320:20: warning: unused function 'dsi_set' [-Wunused-function]. Reported-by: Abaci Robot Signed-off-by: Jiapeng Chong --- drivers/gpu/drm/rockchip/dw-mipi-dsi-rockchip.c | 5 - 1 file changed, 5 deletions(-)

Re: [PATCH v4 05/13] module: Add printk formats to add module build ID to stacktraces

On Tue 2021-04-13 15:57:49, Stephen Boyd wrote: > Quoting Petr Mladek (2021-04-13 08:01:14) > > On Fri 2021-04-09 18:52:52, Stephen Boyd wrote: > > > Let's make kernel stacktraces easier to identify by including the build > > > ID[1] of a module if the stacktrace is printing a symbol from a

Re: [PATCH] riscv: atomic: Using ARCH_ATOMIC in asm/atomic.h

On Thu, Apr 15, 2021 at 07:39:22AM +, guo...@kernel.org wrote: > - Add atomic_andnot_* operation > @@ -76,6 +59,12 @@ ATOMIC_OPS(sub, add, -i) > ATOMIC_OPS(and, and, i) > ATOMIC_OPS( or, or, i) > ATOMIC_OPS(xor, xor, i) > +ATOMIC_OPS(andnot, and, -i) ~i, surely.

Re: [PATCH 3/3] sched: Use cpu_dying() to fix balance_push vs hotplug-rollback

On Tue, Apr 13, 2021 at 08:51:23AM +0200, Peter Zijlstra wrote: > > I'm afraid I don't follow; we're replacing a read of rq->balance_push with > > cpu_dying(), and those are still written on the same side of the > > synchronize_rcu(). What am I missing? > > Yeah, I'm not sure anymnore either; I

Re: [PATCH] mmc: meson-gx: remove useless warning about scatterlist size alignment in block mode

On Wed, 14 Apr 2021 at 12:00, Neil Armstrong wrote: > > Since commit e085b51c74cc ("mmc: meson-gx: check for scatterlist size > alignment in block mode"), > support for SDIO SD_IO_RW_EXTENDED transferts are properly filtered but some > driver > like brcmfmac still gives a block sg buffer size

Re: [GIT PULL] interconnect changes for 5.13

On Thu, Apr 15, 2021 at 11:09:48AM +0300, Georgi Djakov wrote: > Hello Greg, > > This is the pull request with the interconnect changes for the 5.13-rc1 > merge window. These include two new drivers. > > Patches have been in linux-next without any reported issues. Please pull > into

[PATCH] driver: input: touchscreen: modify Raydium i2c touchscreen driver

This path makes auto-update available when IC's status is Recovery mode Signed-off-by: simba.hsu Change-Id: Icf974d59f7717da0de8bd97a06c496a32dafa1ff --- drivers/input/touchscreen/raydium_i2c_ts.c | 53 ++ 1 file changed, 45 insertions(+), 8 deletions(-) diff --git

[PATCH] platform/x86: intel_chtdc_ti_pwrbtn: Fix missing IRQF_ONESHOT as only threaded handler

From: Guangqing Zhu Coccinelle noticed: drivers/platform/x86/intel_chtdc_ti_pwrbtn.c:59:7-32: ERROR: Threaded IRQ with no primary handler requested without IRQF_ONESHOT Signed-off-by: Guangqing Zhu --- drivers/platform/x86/intel_chtdc_ti_pwrbtn.c | 2 +- 1 file changed, 1 insertion(+), 1

Re: [PATCH 04/11] mm/vmstat: Inline NUMA event counter updates

On Wed, Apr 14, 2021 at 06:26:25PM +0200, Vlastimil Babka wrote: > On 4/14/21 6:20 PM, Vlastimil Babka wrote: > > On 4/14/21 3:39 PM, Mel Gorman wrote: > >> __count_numa_event is small enough to be treated similarly to > >> __count_vm_event so inline it. > >> > >> Signed-off-by: Mel Gorman > >

Re: [PATCH bpf-next v3 3/6] bpf: Add a bpf_snprintf helper

On Thu, Apr 15, 2021 at 12:57 AM Andrii Nakryiko wrote: > > On Wed, Apr 14, 2021 at 2:46 AM Florent Revest wrote: > > > > On Wed, Apr 14, 2021 at 1:16 AM Andrii Nakryiko > > wrote: > > > On Mon, Apr 12, 2021 at 8:38 AM Florent Revest > > > wrote: > > > > + > > > > + return err + 1; > >

Re: [PATCH] ASoC: codecs: wcd934x: Fix missing IRQF_ONESHOT as only threaded handler

On 15/04/2021 08:38, zhuguangqin...@gmail.com wrote: From: Guangqing Zhu Coccinelle noticed: sound/soc/codecs/wcd934x.c:5041:7-32: ERROR: Threaded IRQ with no primary handler requested without IRQF_ONESHOT Signed-off-by: Guangqing Zhu --- Thanks for the patch, Reviewed-by: Srinivas

linux-next: manual merge of the akpm-current tree with the powerpc tree

Hi all, Today's linux-next merge of the akpm-current tree got a conflict in: arch/powerpc/kernel/module.c between commit: 2ec13df16704 ("powerpc/modules: Load modules closer to kernel text") from the powerpc tree and commit: 4930ba789f8d ("powerpc/64s/radix: enable huge vmalloc

[PATCH] direct-io: use read lock for DIO_LOCKING flag

9902af79c01a ("parallel lookups: actual switch to rwsem") changes inode lock from mutex to rwsem, however, we forgot to adjust lock for DIO_LOCKING flag in do_blockdev_direct_IO(), so let's change to hold read lock to mitigate performance regression in the case of read DIO vs read DIO, meanwhile

[PATCH V2 0/3] vDPA/ifcvf: enables Intel C5000X-PL virtio-blk

This series enabled Intel FGPA SmartNIC C5000X-PL virtio-blk for vDPA. This series requires: Stefano's vdpa block patchset: https://lkml.org/lkml/2021/3/15/2113 my patchset to enable Intel FGPA SmartNIC C5000X-PL virtio-net for vDPA: https://lkml.org/lkml/2021/3/17/432 changes from V1: (1)add

[PATCH V2 1/3] vDPA/ifcvf: deduce VIRTIO device ID when probe

This commit deduces VIRTIO device ID as device type when probe, then ifcvf_vdpa_get_device_id() can simply return the ID. ifcvf_vdpa_get_features() and ifcvf_vdpa_get_config_size() can work properly based on the device ID. Signed-off-by: Zhu Lingshan --- drivers/vdpa/ifcvf/ifcvf_base.h | 1 +

[PATCH V2 2/3] vDPA/ifcvf: enable Intel C5000X-PL virtio-block for vDPA

This commit enabled Intel FPGA SmartNIC C5000X-PL virtio-block for vDPA. Signed-off-by: Zhu Lingshan --- drivers/vdpa/ifcvf/ifcvf_base.h | 8 +++- drivers/vdpa/ifcvf/ifcvf_main.c | 10 +- 2 files changed, 16 insertions(+), 2 deletions(-) diff --git

[PATCH V2 3/3] vDPA/ifcvf: get_config_size should return dev specific config size

get_config_size() should return the size based on the decected device type. Signed-off-by: Zhu Lingshan --- drivers/vdpa/ifcvf/ifcvf_main.c | 18 +- 1 file changed, 17 insertions(+), 1 deletion(-) diff --git a/drivers/vdpa/ifcvf/ifcvf_main.c b/drivers/vdpa/ifcvf/ifcvf_main.c

Re: linux-next: manual merge of the akpm-current tree with the powerpc tree

Hi all, On Thu, 15 Apr 2021 19:44:17 +1000 Stephen Rothwell wrote: > > Today's linux-next merge of the akpm-current tree got a conflict in: > > arch/powerpc/kernel/module.c > > between commit: > > 2ec13df16704 ("powerpc/modules: Load modules closer to kernel text") > > from the powerpc

Re: linux-next: manual merge of the akpm-current tree with the powerpc tree

Le 15/04/2021 à 12:07, Christophe Leroy a écrit : Le 15/04/2021 à 11:58, Stephen Rothwell a écrit : Hi all, On Thu, 15 Apr 2021 19:44:17 +1000 Stephen Rothwell wrote: Today's linux-next merge of the akpm-current tree got a conflict in:    arch/powerpc/kernel/module.c between commit:

Re: linux-next: manual merge of the akpm-current tree with the powerpc tree

Le 15/04/2021 à 12:08, Christophe Leroy a écrit : Le 15/04/2021 à 12:07, Christophe Leroy a écrit : Le 15/04/2021 à 11:58, Stephen Rothwell a écrit : Hi all, On Thu, 15 Apr 2021 19:44:17 +1000 Stephen Rothwell wrote: Today's linux-next merge of the akpm-current tree got a conflict

[PATCH] efifb: Fix runtime pm calls for non PCI efifb device

Commit a6c0fd3d5a8b ("efifb: Ensure graphics device for efifb stays at PCI D0") added runtime pm calls to probe and remove routines to ensure the PCI device for efifb stays in D0 state. However not ever efifb is based on PCI device and efifb_pci_dev can be NULL if that is the case. In such cases,

[PATCH v1] docs: reporting-issues.rst: CC subsystem and maintainers on regressions

When reporting a regression, users ideally should CC the subsystem and its maintainers, as that will ensure they get aware of the regression quickly. And if the culprit is known, they should also CC everyone who signed if off; the text mentioned the latter in once place already, but forgot to do

[PATCH v2 1/2] dt-bindings: bcm4329-fmac: add optional brcm,ccode-map

Add optional brcm,ccode-map property to support translation from ISO3166 country code to brcmfmac firmware country code and revision. The country revision is needed because the RF parameters that provide regulatory compliance are tweaked per platform/customer. So depending on the RF path tight

[PATCH v2 2/2] brcmfmac: support parse country code map from DT

With any regulatory domain requests coming from either user space or 802.11 IE (Information Element), the country is coded in ISO3166 standard. It needs to be translated to firmware country code and revision with the mapping info in settings->country_codes table. Support populate country_codes

Re: [RFC] scripts: kernel-doc: improve parsing for kernel-doc comments syntax

On 15/4/21 12:55 am, Aditya Srivastava wrote: > Currently kernel-doc does not identify some cases of probable kernel > doc comments, for e.g. pointer used as declaration type for identifier, > space separated identifier, etc. > > Some example of these cases in files can be: > i)" * journal_t *

Re: [PATCH][next] can: etas_es58x: Fix a couple of spelling mistakes

On 15.04.2021 12:30:50, Colin King wrote: > From: Colin Ian King > > There are spelling mistakes in netdev_dbg and netdev_dbg messages, > fix these. > > Signed-off-by: Colin Ian King Applied to linux-can-next/testing. Tnx, Marc -- Pengutronix e.K. | Marc Kleine-Budde

Re: [PATCH 1/5] KVM: arm64: Divorce the perf code from oprofile helpers

Hi Marc, On 2021/4/15 18:42, Marc Zyngier wrote: > On Thu, 15 Apr 2021 07:59:26 +0100, > Keqian Zhu wrote: >> >> Hi Marc, >> >> On 2021/4/14 21:44, Marc Zyngier wrote: >>> KVM/arm64 is the sole user of perf_num_counters(), and really >>> could do without it. Stop using the obsolete API by

Re: [PATCH 0/9] kcsan: Add support for reporting observed value changes

On Wed, Apr 14, 2021 at 01:28:16PM +0200, Marco Elver wrote: > This series adds support for showing observed value changes in reports. > Several clean up and refactors of KCSAN reporting code are done as a > pre-requisite. > This series was originally prepared courtesy of Mark Rutland in >

RE: [PATCH 00/13] [RFC] Rust support

... > Besides just FP, 128-bit, etc, I remain concerned about just basic > math operations. C has no way to describe the intent of integer > overflow, so the kernel was left with the only "predictable" result: > wrap around. Unfortunately, this is wrong in most cases, and we're left > with entire

[PATCH] drm/kmb: remove unused function

Fix the following clang warning: drivers/gpu/drm/kmb/kmb_dsi.c:824:2: warning: unused function 'set_test_mode_src_osc_freq_target_hi_bits' [-Wunused-function]. Reported-by: Abaci Robot Signed-off-by: Jiapeng Chong --- drivers/gpu/drm/kmb/kmb_dsi.c | 16 1 file changed, 16

[PATCH v4 30/33] dt-bindings: media: add microchip,xisc device bindings

Add bindings for the Microchip eXtended Image Sensor Controller. Based on the atmel,isc.yaml binding. Signed-off-by: Eugen Hristev --- .../bindings/media/microchip,xisc.yaml| 129 ++ 1 file changed, 129 insertions(+) create mode 100644

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