netdev - Re: [PATCH 13/20] octeontx2-af: Add FLR interrupt handler

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]

Date:   Thu, 8 Nov 2018 21:50:11 +0100
From:   Arnd Bergmann <arnd@...db.de>
To:     Sunil Kovvuri <sunil.kovvuri@...il.com>
Cc:     Networking <netdev@...r.kernel.org>,
        David Miller <davem@...emloft.net>, linux-soc@...r.kernel.org,
        Geetha sowjanya <gakula@...vell.com>,
        Sunil Goutham <sgoutham@...vell.com>
Subject: Re: [PATCH 13/20] octeontx2-af: Add FLR interrupt handler

On Thu, Nov 8, 2018 at 7:37 PM <sunil.kovvuri@...il.com> wrote:
>
> From: Geetha sowjanya <gakula@...vell.com>
>
> All RVU PF's upon receiving a FLR will trigger an IRQ to RVU AF.
> This patch enables all RVU PF's FLR interrupt and registers a
> handler. Upon receiving an IRQ a workqueue is scheduled to
> cleanup all RVU blocks being used by the PF/VF which received
> the FLR.

I assume this all makes sense, but I find it hard to read the changelog
text with all those acronyms. I probably knew what an FLR and a RVU
is in the earlier review rounds, but it would be nice to reword changelogs
like this one so they make more sense to readers that are not already
familiar with the rest of the driver.

      Arnd