aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python
diff options
context:
space:
mode:
authorSeongJae Park <[email protected]>2024-05-03 11:03:18 -0700
committerAndrew Morton <[email protected]>2024-05-11 15:41:35 -0700
commit3974345f269c2701d4cad7bd3f2ed4445bdbbfbb (patch)
tree5b99b25ca81a4f01179b9f07a88f45d535683dea /tools/perf/scripts/python
parent437f7960d043bdce0eb6abe1c57232bc90a55fa9 (diff)
Docs/mm/damon/maintainer-profile: allow posting patches based on damon/next tree
The document mentions any patches for review should based on mm-unstable instead of damon/next. It should be the recommended process, but sometimes patches based on damon/next could be posted for some reasons. Actually, the DAMON-based tiered memory management patchset[1] was written on top of 'young page' DAMOS filter patchset, which was in damon/next tree as of the writing. Allow such case and just ask such things to be clearly specified. [1] https://lore.kernel.org/[email protected] Link: https://lkml.kernel.org/r/[email protected] Signed-off-by: SeongJae Park <[email protected]> Cc: Jonathan Corbet <[email protected]> Cc: Shuah Khan <[email protected]> Signed-off-by: Andrew Morton <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions