Message ID | 20220615165929.5924-1-elder@linaro.org (mailing list archive) |
---|---|
Headers | show |
Series | net: ipa: more multi-channel event ring work | expand |
Hello: This series was applied to netdev/net-next.git (master) by Jakub Kicinski <kuba@kernel.org>: On Wed, 15 Jun 2022 11:59:24 -0500 you wrote: > This series makes a little more progress toward supporting multiple > channels with a single event ring. The first removes the assumption > that consecutive events are associated with the same RX channel. > > The second derives the channel associated with an event from the > event itself, and the next does a small cleanup enabled by that. > > [...] Here is the summary with links: - [net-next,1/5] net: ipa: don't assume one channel per event ring https://git.kernel.org/netdev/net-next/c/dd5a046cbbed - [net-next,2/5] net: ipa: don't pass channel when mapping transaction https://git.kernel.org/netdev/net-next/c/8eec78319585 - [net-next,3/5] net: ipa: pass GSI pointer to gsi_evt_ring_rx_update() https://git.kernel.org/netdev/net-next/c/2f48fb0edc0d - [net-next,4/5] net: ipa: call gsi_evt_ring_rx_update() unconditionally https://git.kernel.org/netdev/net-next/c/9f1c3ad65406 - [net-next,5/5] net: ipa: move more code out of gsi_channel_update() https://git.kernel.org/netdev/net-next/c/81765eeac1b0 You are awesome, thank you!