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] [thread-next>] [day] [month] [year] [list]
Message-ID: <d7552864-9da2-43e3-838b-837ef3fa9f0b@redhat.com>
Date: Wed, 29 Jan 2025 17:36:00 +0100
From: Hans de Goede <hdegoede@...hat.com>
To: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
 linux-gpio@...r.kernel.org, linux-kernel@...r.kernel.org
Cc: Mika Westerberg <mika.westerberg@...ux.intel.com>,
 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

Hi,

On 29-Jan-25 3:49 PM, 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

Thanks, patches looks good to me:

Reviewed-by: Hans de Goede <hdegoede@...hat.com>

For the series.

Regards,

Hans


> 
>  drivers/pinctrl/intel/pinctrl-baytrail.c  | 5 ++++-
>  drivers/pinctrl/intel/pinctrl-lynxpoint.c | 5 ++++-
>  2 files changed, 8 insertions(+), 2 deletions(-)
> 


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ