titanz/Kernel-Module-Blacklist
1
0
Fork 0
mirror of https://github.com/TommyTran732/Kernel-Module-Blacklist.git synced 2025-02-23 21:11:15 +01:00
Code Issues Packages Projects Releases Wiki Activity

Typo fix

Browse Source 
Signed-off-by: Tommy <contact@tommytran.io>
This commit is contained in:
Tommy 2024-06-03 00:08:32 -07:00
parent a6f93249e2
commit a8a06c476c
No known key found for this signature in database
GPG Key ID: 555C902A34EC968F
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@ -29,7 +29,7 @@ Additionally, the output of `lshw`, information on your workload, etc will be gr
## Supported hardwware/Workload ## Supported hardwware/Workload
Reasonably new and common hard hardware and will be added to the `sample-data` dictory and used to generate the kernel module blacklist. The same goes for server workloads - if it is a reasonably common workload, it will be supported. Reasonably new and common hard hardware and will be added to the `sample-data` directory and used to generate the kernel module blacklist. The same goes for server workloads - if it is a reasonably common workload, it will be supported.
One exception for this is the use of technologies that are known to be vulnerable, such as Thunderbolt. Their kernel module will always remain blacklisted and whichever workload relies on them will not be supported. One exception for this is the use of technologies that are known to be vulnerable, such as Thunderbolt. Their kernel module will always remain blacklisted and whichever workload relies on them will not be supported.