Hi Corey, >> - use the spinlock patch as a temporary workaround, until 4.15 where >> this series replaces it. What were the issues around that change? > > They could be more easily done with a temporary variable and memory > barriers. But that wasn't the main issue I ended up fixing. > > There is a patch near the end of the series that changes the BMC > naming to not use the product and device id in the name, which should > cover a lot of the issues that might show up with name collisions. > However, that is a functional change that I'm a little worried about. > > But I could use that patch and the dynamic device id patch, and the > worst thing that could happen is the same BMC could show up as two > different BMCs on two different interfaces. I think. The changes > wouldn't be that large.
Yep, that should cover our case - the main thing is that the device/product/ipmi version is available in sysfs. The name doesn't matter much in this case. Cheers, Jeremy ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Openipmi-developer mailing list Openipmi-developer@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openipmi-developer
