Alex,
On Mon, Nov 23 2020 at 17:56, Alex Belits wrote:
why are you insisting on adding 'task_isolation: ' as prefix to every
single patch? That's wrong as I explained before.
The prefix denotes the affected subsystem and 'task_isolation' is _NOT_
a subsystem. It's the project name you are using but the affected code
belongs to the memory management subsystem and if you run
git log mm/vmstat.c
you might get a hint what the proper prefix is, i.e. 'mm/vmstat: '
> In commit f01f17d3705b ("mm, vmstat: make quiet_vmstat lighter")
> the quiet_vmstat() function became asynchronous, in the sense that
> the vmstat work was still scheduled to run on the core when the
> function returned. For task isolation, we need a synchronous
This changelog is useless because how should someone not familiar with
the term 'task isolation' figure out what that means?
It's not the reviewers job to figure that out. Again: Go read and adhere
to Documentation/process/*
Aside of that your patches are CR/LF inflicted. Please fix your work
flow and tools.
Thanks,
tglx
