X-Git-Url: https://jxself.org/git/?a=blobdiff_plain;f=README.md;h=77addd324312ae606e241a6b7203800edacd16ae;hb=22bb83e27f6846becf47ef6e274b7af43799d690;hp=68829b1ad5c910bf4c87590529e46241d3448e8c;hpb=87db8c4fc519a655380aefe635de41e6df1568e3;p=kconfig-hardened-check.git

diff --git a/README.md b/README.md
index 68829b1..77addd3 100644
--- a/README.md
+++ b/README.md
@@ -18,7 +18,7 @@ against my security hardening preferences, which are based on the
   - [CLIP OS kernel configuration][2],
   - Last public [grsecurity][3] patch (options which they disable),
   - [SECURITY_LOCKDOWN_LSM][5] patchset,
-  - Direct feedback from Linux kernel maintainers (see [#38][6], [#53][15], [#54][16]).
+  - Direct feedback from Linux kernel maintainers (see [#38][6], [#53][15], [#54][16], [#62][17]).
 
 I also created [__Linux Kernel Defence Map__][4] that is a graphical representation of the
 relationships between security hardening features and the corresponding vulnerability classes
@@ -347,3 +347,4 @@ I highly recommend using [spectre-meltdown-checker][13] tool maintained by Stép
 [14]: https://github.com/speed47
 [15]: https://github.com/a13xp0p0v/kconfig-hardened-check/issues/53
 [16]: https://github.com/a13xp0p0v/kconfig-hardened-check/pull/54
+[17]: https://github.com/a13xp0p0v/kconfig-hardened-check/pull/62