From a9bc7747dc2edb25ca2e9a2c02b5b669ce36c9c7 Mon Sep 17 00:00:00 2001
From: 4lDO2 <4lDO2@protonmail.com>
Date: Thu, 2 Jul 2020 20:41:42 +0200
Subject: [PATCH] Add link to opcodes.

---
 content/news/io_uring-1.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/content/news/io_uring-1.md b/content/news/io_uring-1.md
index 04ebf744..84e0ee65 100644
--- a/content/news/io_uring-1.md
+++ b/content/news/io_uring-1.md
@@ -12,8 +12,8 @@ imporantly how the kernel is going to be involved in `io_uring` operation.
 
 I also came up with a set of standard opcodes, that schemes are meant to use
 when using `io_uring`, unless in some special scenarios (like general-purpose
-IPC between processes).<!-- The opcodes at this point in time, can be found
-[here](0.0.0.0).-->
+IPC between processes). The opcodes at this point in time, can be found
+[here](https://doc.redox-os.org/io_uring/syscall/io_uring/v1/enum.StandardOpcode.html).
 
 ## The three attachment modes
 The most notable change that I made, is that instead of always attaching an
-- 
GitLab