patch does not apply to 3.2.1 (released in late 2017). Given that it fixes the issue discussed in May 2016, most likely it shall apply only to 3.2