linux-kernel - Re: [PATCH v2] pinctrl: mcp23s08: Check only GPIOs which have interrupts enabled

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: <0dab8d77-ea4e-4cea-99dd-2ffe7c9051d5@gmail.com>
Date: Wed, 7 Feb 2024 12:50:51 +0200
From: Arturas Moskvinas <arturas.moskvinas@...il.com>
To: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Cc: linus.walleij@...aro.org, biju.das.jz@...renesas.com,
 akaessens@...il.com, thomas.preston@...ethink.co.uk,
 preid@...ctromag.com.au, u.kleine-koenig@...gutronix.de,
 linux-gpio@...r.kernel.org, linux-kernel@...r.kernel.org,
 arturas.moskvinas@...il.com
Subject: Re: [PATCH v2] pinctrl: mcp23s08: Check only GPIOs which have
 interrupts enabled

On 2/5/24 15:56, Andy Shevchenko wrote:
>> Do you want that information to be added as part of commit message or
>> information in the mailing thread will be enough?
> Up to maintainers. I'm fine with this email. If Linus uses b4 to generate
> a Link tag to this discussion it will be enough (in my opinion).

Is there anything left for me to update/change? Or we're waiting for 
other reviewers and/or Linus to chime in?

Arturas Moskvinas