Hello, I was looking into the use of devm_spi_register_master. This function seems to take care of registering and unregistering, but not allocation and freeing. I have the impression that that is done with spi_alloc_master and and spi_master_put, which are not managed functions. But then I wonder how this can work? It seems that the spi_master_put function should remain in the probe or remove function, and then the object could be freed before it is unregistered?
The patch 2fe7e4add3e53df7c1b97e32076f8390dd81c6b3 introduces a call to devm_spi_register_master and also removes a call to spi_master_put. By my reasoning, this would cause a memory leak. Am I missing something? thanks, julia -- To unsubscribe from this list: send the line "unsubscribe linux-spi" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
