Skip to content

Conversation

@ghost
Copy link

@ghost ghost commented Feb 2, 2023

No description provided.

@tiann tiann merged commit 199f5cc into tiann:main Feb 2, 2023
@ghost ghost deleted the for-typo-fixes branch February 2, 2023 20:01
tiann pushed a commit that referenced this pull request Feb 6, 2023
i didn't realize these typos in #181

Signed-off-by: Ookiineko <[email protected]>
itswill00 pushed a commit to itswill00/KernelSU-Next-4.14 that referenced this pull request Jan 19, 2025
Signed-off-by: Ookiineko <[email protected]>
Co-authored-by: f19 <[email protected]>
Co-authored-by: Scirese <[email protected]>
itswill00 pushed a commit to itswill00/KernelSU-Next-4.14 that referenced this pull request Jan 19, 2025
i didn't realize these typos in tiann#181

Signed-off-by: Ookiineko <[email protected]>
chenzhu005774 pushed a commit to chenzhu005774/KernelSU that referenced this pull request Sep 12, 2025
Signed-off-by: Ookiineko <[email protected]>
Co-authored-by: f19 <[email protected]>
Co-authored-by: Scirese <[email protected]>
chenzhu005774 pushed a commit to chenzhu005774/KernelSU that referenced this pull request Sep 12, 2025
i didn't realize these typos in tiann#181

Signed-off-by: Ookiineko <[email protected]>
LeCmnGend pushed a commit to LeCmnGend/KernelSU that referenced this pull request Nov 2, 2025
…iann#181)

* Pre Linux 5.9, handle_inode_event did not exist. This is was covered by handle_event.
* handle_event have a lot of changes, neither in arguments counts and arguments arrangements.
* Use fsnotify_add_mark_locked instead of fsnotify_add_inode_mark for kernel pre 4.12

NOTE: fsnotify_add_mark_locked is not tested! Report bugs if you found it!

Signed-off-by: Faris <[email protected]>
LeCmnGend pushed a commit to LeCmnGend/KernelSU that referenced this pull request Nov 3, 2025
…iann#181)

* Pre Linux 5.9, handle_inode_event did not exist. This is was covered by handle_event.
* handle_event have a lot of changes, neither in arguments counts and arguments arrangements.
* Use fsnotify_add_mark_locked instead of fsnotify_add_inode_mark for kernel pre 4.12

NOTE: fsnotify_add_mark_locked is not tested! Report bugs if you found it!

Signed-off-by: Faris <[email protected]>
LeCmnGend pushed a commit to LeCmnGend/KernelSU that referenced this pull request Nov 7, 2025
…iann#181)

* Pre Linux 5.9, handle_inode_event did not exist. This is was covered by handle_event.
* handle_event have a lot of changes, neither in arguments counts and arguments arrangements.
* Use fsnotify_add_mark_locked instead of fsnotify_add_inode_mark for kernel pre 4.12

NOTE: fsnotify_add_mark_locked is not tested! Report bugs if you found it!

Signed-off-by: Faris <[email protected]>
LeCmnGend pushed a commit to LeCmnGend/KernelSU that referenced this pull request Nov 8, 2025
…iann#181)

* Pre Linux 5.9, handle_inode_event did not exist. This is was covered by handle_event.
* handle_event have a lot of changes, neither in arguments counts and arguments arrangements.
* Use fsnotify_add_mark_locked instead of fsnotify_add_inode_mark for kernel pre 4.12

NOTE: fsnotify_add_mark_locked is not tested! Report bugs if you found it!

Signed-off-by: Faris <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants