[skip ci] Remove obsolete references in crypto_request(9)

They were missed by 68f6800ce0.

Sponsored by:	Axcient
MFC with:	68f6800ce0
Reviewed by:	markj
Differential Revision: https://reviews.freebsd.org/D37239

share/man/man9/crypto_request.9

@@ -30,7 +30,7 @@
 .\"
 .\" $FreeBSD$
 .\"
-.Dd January 4, 2022
+.Dd November 2, 2022
 .Dt CRYPTO_REQUEST 9
 .Os
 .Sh NAME
@@ -441,17 +441,12 @@ the callback is invoked synchronously if the request was processed by a
 software driver or asynchronously if the request was processed by a
 hardware driver.
 .Pp
-If a request was scheduled to the taskqueue via
-.Dv CRYPTO_F_ASYNC ,
+If a request was scheduled to the taskqueue with
+.Dv CRYPTO_ASYNC_ORDERED ,
 callbacks are always invoked asynchronously ignoring
 .Dv CRYPTO_F_CBIMM
 and
 .Dv CRYPTO_F_CBIFSYNC .
-In this case,
-.Dv CRYPTO_F_ASYNC_KEEPORDER
-may be set to ensure that callbacks for requests on a given session are
-invoked in the same order that requests were queued to the session via
-.Fn crypto_dispatch .
 This flag is used by IPsec to ensure that decrypted network packets are
 passed up the network stack in roughly the same order they were received.
 .Ss Other Request Fields

sys/opencrypto/crypto.c

@@ -149,8 +149,8 @@ SYSCTL_NODE(_kern, OID_AUTO, crypto, CTLFLAG_RW, 0,
     "In-kernel cryptography");
 
 /*
- * Taskqueue used to dispatch the crypto requests
- * that have the CRYPTO_F_ASYNC flag
+ * Taskqueue used to dispatch the crypto requests submitted with
+ * crypto_dispatch_async .
  */
 static struct taskqueue *crypto_tq;