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: <20250130124743.GX3713119@black.fi.intel.com>
Date: Thu, 30 Jan 2025 14:47:43 +0200
From: Mika Westerberg <mika.westerberg@...ux.intel.com>
To: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Cc: Hans de Goede <hdegoede@...hat.com>, linux-gpio@...r.kernel.org,
	linux-kernel@...r.kernel.org, Andy Shevchenko <andy@...nel.org>,
	Linus Walleij <linus.walleij@...aro.org>
Subject: Re: [PATCH v1 0/2] pinctrl: intel: Unify the way of handling chained
 IRQ

On Wed, Jan 29, 2025 at 04:49:38PM +0200, Andy Shevchenko wrote:
> Some of the drivers are using the dedicated helpers (chained_irq_enter(),
> chained_irq_exit() helpers) and some relies on the specific implementations
> of the parent IRQ chip and its configuration. Update the latter ones to
> use dedicated helpers that cover all possible scenarios.
> 
> Andy Shevchenko (2):
>   pinctrl: baytrail: Use dedicated helpers for chained IRQ handlers
>   pinctrl: lynxpoint: Use dedicated helpers for chained IRQ handlers

Both,

Acked-by: Mika Westerberg <mika.westerberg@...ux.intel.com>

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ