Re: [PATCH 2/2] drm/mm: Some doc polish

On Wed, Dec 28, 2016 at 04:25:29PM +0100, Daniel Vetter wrote:

@@ -549,9 +549,11 @@ EXPORT_SYMBOL(drm_mm_replace_node);

• The DRM range allocator supports this use-case through the scanning
• interfaces. First a scan operation needs to be initialized with
• drm_mm_scan_init() or drm_mm_scan_init_with_range(). The driver adds

• • objects to the roster (probably by walking an LRU list, but this can be
• • freely implemented) (using drm_mm_scan_add_block()) until a suitable hole
• • is found or there are no further evictable objects.

• • objects to the roaster, probably by walking an LRU list, but this can be

We are not roasting them! The ordered list is "roster".

• • freely implemented. Evication candiates are added using

s/Evication/Eviction/

• • drm_mm_scan_add_block() until a suitable hole is found or there are no
• • further evictable objects. Eviction roaster metadata is tracked in struct
• • &drm_mm_scan.