linux-kernel - [PATCH] textsearch: clarify how to clean up in doc

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Thu,  9 Oct 2014 14:11:57 -0700
From:	Omar Sandoval <osandov@...ndov.com>
To:	Andrew Morton <akpm@...ux-foundation.org>,
	Fabian Frederick <fabf@...net.be>, linux-kernel@...r.kernel.org
Cc:	Omar Sandoval <osandov@...ndov.com>
Subject: [PATCH] textsearch: clarify how to clean up in doc

textsearch_put() doesn't exist; this comment appears to be referring to
textsearch_destroy().

Signed-off-by: Omar Sandoval <osandov@...ndov.com>
---
This patch applies to 3.17. There was a patch submitted previously which got
rid of this documentation (https://lkml.org/lkml/2014/9/6/128), but this is a
little more clear, as clean up is still required.

 lib/textsearch.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lib/textsearch.c b/lib/textsearch.c
index 0c7e9ab..7f52c8f 100644
--- a/lib/textsearch.c
+++ b/lib/textsearch.c
@@ -251,7 +251,7 @@ EXPORT_SYMBOL(textsearch_find_continuous);
  * Looks up the search algorithm module and creates a new textsearch
  * configuration for the specified pattern. Upon completion all
  * necessary refcnts are held and the configuration must be put back
- * using textsearch_put() after usage.
+ * using textsearch_destroy() after usage.
  *
  * Note: The format of the pattern may not be compatible between
  *       the various search algorithms.
-- 
2.1.2

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/