Update how-to-integrate-for-non-gki.md

Author: rifsxd

docs/pages/how-to-integrate-for-non-gki.md

@@ -287,77 +287,6 @@ index 2ff887661237..e758d7db7663 100644
  		return -EINVAL;
 ```
 
-### Safe Mode
-
-To enable KernelSU Next's built-in Safe Mode, you should modify the `input_handle_event` function in `drivers/input/input.c`:
-
-::: tip
-It's strongly recommended to enable this feature, it's very useful for preventing bootloops!
-:::
-
-```diff
-diff --git a/drivers/input/input.c b/drivers/input/input.c
-index 45306f9ef247..815091ebfca4 100755
---- a/drivers/input/input.c
-+++ b/drivers/input/input.c
-@@ -367,10 +367,13 @@ static int input_get_disposition(struct input_dev *dev,
- 	return disposition;
- }
-
-+#ifdef CONFIG_KSU
-+extern bool ksu_input_hook __read_mostly;
-+extern int ksu_handle_input_handle_event(unsigned int *type, unsigned int *code, int *value);
-+#endif
-+
- static void input_handle_event(struct input_dev *dev,
- 			       unsigned int type, unsigned int code, int value)
- {
-	int disposition = input_get_disposition(dev, type, code, &value);
-+   #ifdef CONFIG_KSU
-+	if (unlikely(ksu_input_hook))
-+		ksu_handle_input_handle_event(&type, &code, &value);
-+   #endif
- 
- 	if (disposition != INPUT_IGNORE_EVENT && type != EV_SYN)
- 		add_input_randomness(type, code, value);
-```
-
-::: info ENTERING SAFE MODE ACCIDENTALLY?
-If you're using manual integration and don't disable `CONFIG_KPROBES`, the user will be able to trigger Safe Mode by pressing the volume down button after booting! Therefore, if you're using manual integration, it's necessary to disable `CONFIG_KPROBES`!
-:::
-
-### Failed to execute `pm` in terminal?
-
-You should modify `fs/devpts/inode.c`. Reference:
-
-```diff
-diff --git a/fs/devpts/inode.c b/fs/devpts/inode.c
-index 32f6f1c68..d69d8eca2 100644
---- a/fs/devpts/inode.c
-+++ b/fs/devpts/inode.c
-@@ -602,6 +602,8 @@ struct dentry *devpts_pty_new(struct pts_fs_info *fsi, int index, void *priv)
-        return dentry;
- }
-
-+#ifdef CONFIG_KSU
-+extern int ksu_handle_devpts(struct inode*);
-+#endif
-+
- /**
-  * devpts_get_priv -- get private data for a slave
-  * @pts_inode: inode of the slave
-@@ -610,6 +612,7 @@ struct dentry *devpts_pty_new(struct pts_fs_info *fsi, int index, void *priv)
-  */
- void *devpts_get_priv(struct dentry *dentry)
- {
-+       #ifdef CONFIG_KSU
-+       ksu_handle_devpts(dentry->d_inode);
-+       #endif
-        if (dentry->d_sb->s_magic != DEVPTS_SUPER_MAGIC)
-                return NULL;
-        return dentry->d_fsdata;
-```
-
 Finally, build your kernel again, and KernelSU Next should work correctly.