[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20220703181739.387584-2-dakr@redhat.com>
Date: Sun, 3 Jul 2022 20:17:39 +0200
From: Danilo Krummrich <dakr@...hat.com>
To: willy@...radead.org, linux-fsdevel@...r.kernel.org,
linux-kernel@...r.kernel.org
Cc: Danilo Krummrich <dakr@...hat.com>
Subject: [PATCH 2/2] doc/idr: adjust to new IDR allocation API
The IDR API was adjusted to match the IDA API, adjust the
documentation accordingly.
Signed-off-by: Danilo Krummrich <dakr@...hat.com>
---
Documentation/core-api/idr.rst | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/Documentation/core-api/idr.rst b/Documentation/core-api/idr.rst
index 2eb5afdb9931..53310d1a2552 100644
--- a/Documentation/core-api/idr.rst
+++ b/Documentation/core-api/idr.rst
@@ -24,9 +24,9 @@ Start by initialising an IDR, either with DEFINE_IDR()
for statically allocated IDRs or idr_init() for dynamically
allocated IDRs.
-You can call idr_alloc() to allocate an unused ID. Look up
-the pointer you associated with the ID by calling idr_find()
-and free the ID by calling idr_remove().
+You can call idr_alloc(), idr_alloc_range(), idr_alloc_min() or idr_alloc_max()
+to allocate an unused ID, look up the pointer you associated with the ID by
+calling idr_find() and free the ID by calling idr_remove().
If you need to change the pointer associated with an ID, you can call
idr_replace(). One common reason to do this is to reserve an
--
2.36.1
Powered by blists - more mailing lists