Re: [PATCH v3 02/12] clk: Check that ops of composite clock components, exist before calling

2020-02-06 Thread Lukasz Majewski
Hi Sean, > clk_composite_ops was shared between all devices in the composite > clock driver. If one clock had a feature (such as supporting > set_parent) which another clock did not, it could call a null pointer > dereference. > > This patch does three things > 1. It adds null-pointer checks to

[PATCH v3 02/12] clk: Check that ops of composite clock components, exist before calling

2020-02-02 Thread Sean Anderson
clk_composite_ops was shared between all devices in the composite clock driver. If one clock had a feature (such as supporting set_parent) which another clock did not, it could call a null pointer dereference. This patch does three things 1. It adds null-pointer checks to all composite clock