On Wed, 2017-06-14 at 09:19 +0800, CK Hu wrote:
> On Mon, 2017-06-12 at 15:15 +0800, YT Shen wrote:
> > Previous patch (c5f228ef6c drm/mediatek: add *driver_data for different
> > hardware settings) calls devm_kfree() and then devm_kzalloc() to
> > reallocate color module data structure. But this
On Mon, 2017-06-12 at 15:15 +0800, YT Shen wrote:
> Previous patch (c5f228ef6c drm/mediatek: add *driver_data for different
> hardware settings) calls devm_kfree() and then devm_kzalloc() to
> reallocate color module data structure. But this reallocation cannnot
> guarantee the new address is unch
Previous patch (c5f228ef6c drm/mediatek: add *driver_data for different
hardware settings) calls devm_kfree() and then devm_kzalloc() to
reallocate color module data structure. But this reallocation cannnot
guarantee the new address is unchanged, but the caller will use the
old address, which is w
