netdev - Re: [PATCH net-next 0/8] net: ipa: determine GSI register offsets differently

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]

Date:   Mon, 13 Feb 2023 10:00:20 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     Alex Elder <elder@...aro.org>
Cc:     davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org,
        pabeni@...hat.com, caleb.connolly@...aro.org, mka@...omium.org,
        evgreen@...omium.org, andersson@...nel.org,
        quic_cpratapa@...cinc.com, quic_avuyyuru@...cinc.com,
        quic_jponduru@...cinc.com, quic_subashab@...cinc.com,
        elder@...nel.org, netdev@...r.kernel.org,
        linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next 0/8] net: ipa: determine GSI register offsets
 differently

Hello:

This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@...emloft.net>:

On Fri, 10 Feb 2023 13:36:47 -0600 you wrote:
> This series changes the way GSI register offset are specified, using
> the "reg" mechanism currently used for IPA registers.  A follow-on
> series will extend this work so fields within GSI registers are also
> specified this way.
> 
> The first patch rearranges the GSI register initialization code so
> it is similar to the way it's done for the IPA registers.  The
> second identifies all the GSI registers in an enumerated type.
> The third introduces "gsi_reg-v3.1.c" and uses the "reg" code to
> define one GSI register offset.  The second-to-last patch just
> adds "gsi_reg-v3.5.1.c", because that version introduces a new
> register not previously defined.  All the rest just define the
> rest of the GSI register offsets using the "reg" mechanism.
> 
> [...]

Here is the summary with links:
  - [net-next,1/8] net: ipa: introduce gsi_reg_init()
    https://git.kernel.org/netdev/net-next/c/3c506add35c7
  - [net-next,2/8] net: ipa: introduce GSI register IDs
    https://git.kernel.org/netdev/net-next/c/8f0fece65d9e
  - [net-next,3/8] net: ipa: start creating GSI register definitions
    https://git.kernel.org/netdev/net-next/c/d2bb6e657f16
  - [net-next,4/8] net: ipa: add more GSI register definitions
    https://git.kernel.org/netdev/net-next/c/76924eb92801
  - [net-next,5/8] net: ipa: define IPA v3.1 GSI event ring register offsets
    https://git.kernel.org/netdev/net-next/c/d1ce6395d464
  - [net-next,6/8] net: ipa: define IPA v3.1 GSI interrupt register offsets
    https://git.kernel.org/netdev/net-next/c/7ba51aa2d09b
  - [net-next,7/8] net: ipa: add "gsi_v3.5.1.c"
    https://git.kernel.org/netdev/net-next/c/465d1bc9823d
  - [net-next,8/8] net: ipa: define IPA remaining GSI register offsets
    https://git.kernel.org/netdev/net-next/c/5791a73c8916

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html