linux-kernel - Re: [PATCH v5 3/3] irqchip/plic: add support for UltraRISC DP1000 PLIC

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <87sefj179h.ffs@tglx>
Date: Thu, 16 Oct 2025 12:16:26 +0200
From: Thomas Gleixner <tglx@...utronix.de>
To: Lucas Zampieri <lzampier@...hat.com>, linux-kernel@...r.kernel.org
Cc: Charles Mirabile <cmirabil@...hat.com>, Rob Herring <robh@...nel.org>,
 Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley
 <conor+dt@...nel.org>, Paul Walmsley <paul.walmsley@...ive.com>, Samuel
 Holland <samuel.holland@...ive.com>, Palmer Dabbelt <palmer@...belt.com>,
 Albert Ou <aou@...s.berkeley.edu>, Alexandre Ghiti <alex@...ti.fr>, Vivian
 Wang <dramforever@...e.com>, devicetree@...r.kernel.org,
 linux-riscv@...ts.infradead.org, Zhang Xincheng
 <zhangxincheng@...rarisc.com>, Lucas Zampieri <lzampier@...hat.com>
Subject: Re: [PATCH v5 3/3] irqchip/plic: add support for UltraRISC DP1000 PLIC

On Thu, Oct 16 2025 at 09:42, Lucas Zampieri wrote:
> @@ -430,6 +516,8 @@ static const struct of_device_id plic_match[] = {
      ^^^^^^^^^^^^
How on earth did you manage to screw up the hunk header?

Applying: irqchip/plic: Add support for UltraRISC DP1000 PLIC
error: corrupt patch at line 116

>  	  .data = (const void *)BIT(PLIC_QUIRK_EDGE_INTERRUPT) },
>  	{ .compatible = "thead,c900-plic",
>  	  .data = (const void *)BIT(PLIC_QUIRK_EDGE_INTERRUPT) },
> +	{ .compatible = "ultrarisc,cp100-plic",
> +	  .data = (const void *)BIT(PLIC_QUIRK_CP100_CLAIM_REGISTER_ERRATUM) },
>  	{}
>  };
>  
> @@ -664,12 +752,16 @@ static int plic_probe(struct fwnode_handle *fwnode)
     ^^^^^^^^^^^^^^^
Ditto here.

I fixed it up manually. Please be more careful next time.