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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sat, 16 Jan 2021 19:12:07 -0800 From: Jakub Kicinski <kuba@...nel.org> To: Alex Elder <elder@...aro.org> Cc: davem@...emloft.net, evgreen@...omium.org, bjorn.andersson@...aro.org, cpratapa@...eaurora.org, subashab@...eaurora.org, netdev@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH net-next 7/7] net: ipa: allow arbitrary number of interconnects On Fri, 15 Jan 2021 06:50:50 -0600 Alex Elder wrote: > Currently we assume that the IPA hardware has exactly three > interconnects. But that won't be guaranteed for all platforms, > so allow any number of interconnects to be specified in the > configuration data. > > For each platform, define an array of interconnect data entries > (still associated with the IPA clock structure), and record the > number of entries initialized in that array. > > Loop over all entries in this array when initializing, enabling, > disabling, or tearing down the set of interconnects. > > With this change we no longer need the ipa_interconnect_id > enumerated type, so get rid of it. Okay, all the platforms supported as of the end of the series still have 3 interconnects, or there is no upstream user of this functionality, if you will. What's the story?
Powered by blists - more mailing lists