It's quite a long time ago. I cannot fully remember the whole picture now. I
remembered the last status was to push some unit tests and with the last part
of patch. Currently I think you can revert this if it causes troubles, we can
purpose this again if we need this in future.
Thanks,
Zhi.
--
On 2019.07.12 11:06:01 +0300, Joonas Lahtinen wrote:
> + Zhenyu as FYI
>
> Quoting Chris Wilson (2019-07-02 14:56:04)
> > Quoting Michał Winiarski (2019-07-02 12:31:48)
> > > This reverts commit 4395890a48551982549d222d1923e2833dac47cf.
> > >
> > > It's been over a year since this was merged, and
+ Zhenyu as FYI
Quoting Chris Wilson (2019-07-02 14:56:04)
> Quoting Michał Winiarski (2019-07-02 12:31:48)
> > This reverts commit 4395890a48551982549d222d1923e2833dac47cf.
> >
> > It's been over a year since this was merged, and the actual users of
> > intel_ppat_get / intel_ppat_put never mate
Quoting Michał Winiarski (2019-07-02 12:31:48)
> This reverts commit 4395890a48551982549d222d1923e2833dac47cf.
>
> It's been over a year since this was merged, and the actual users of
> intel_ppat_get / intel_ppat_put never materialized.
>
> Time to remove it!
>
> v2: Unbreak suspend (Chris)
> v
This reverts commit 4395890a48551982549d222d1923e2833dac47cf.
It's been over a year since this was merged, and the actual users of
intel_ppat_get / intel_ppat_put never materialized.
Time to remove it!
v2: Unbreak suspend (Chris)
v3: Rebase, drop fixes tag to avoid confusion
Signed-off-by: Mich