From: Danilo Krummrich <dakr@redhat.com>
To: willy@infradead.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: Danilo Krummrich <dakr@redhat.com>
Subject: [PATCH 2/2] doc/idr: adjust to new IDR allocation API
Date: Sun, 3 Jul 2022 20:17:39 +0200 [thread overview]
Message-ID: <20220703181739.387584-2-dakr@redhat.com> (raw)
In-Reply-To: <20220703181739.387584-1-dakr@redhat.com>
The IDR API was adjusted to match the IDA API, adjust the
documentation accordingly.
Signed-off-by: Danilo Krummrich <dakr@redhat.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
next prev parent reply other threads:[~2022-07-03 18:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-03 18:17 [PATCH 1/2] treewide: idr: align IDR and IDA APIs Danilo Krummrich
2022-07-03 18:17 ` Danilo Krummrich [this message]
2022-07-03 20:49 ` Matthew Wilcox
2022-07-03 22:33 ` Danilo Krummrich
2022-07-04 0:28 ` Danilo Krummrich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220703181739.387584-2-dakr@redhat.com \
--to=dakr@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=willy@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®