You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/Contributing.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,7 +40,7 @@ For this reason, early on, there are a few extra notes to have in mind when cont
40
40
41
41
All patches containing Rust code should be sent to both the maintainers/reviewers/mailing lists of the relevant kernel subsystem they touch as well as the Rust one.
42
42
43
-
This applies even if the files that the patch modifies are all under `rust/` (e.g. currently all abstractions live under `rust/`, but the plan is to change this in the future as Rust grows in the kernel) and the files are referenced by the `MAINTAINERS` entry of the relevant subsystem.
43
+
This applies even if the files that the patch modifies are all under `rust/` (e.g. currently all abstractions live under `rust/`, but the plan is to change this in the future as Rust grows in the kernel) and the files are referenced by the `MAINTAINERS` entry of the relevant subsystem. Scripts like `scripts/get_maintainers.pl` may not provide the complete list.
44
44
45
45
The goal with this procedure is that everybody interested in Rust can follow what is going on with Rust in the entire kernel in the early stages, to avoid duplicate work, and to make it easier for everybody to coordinate.
0 commit comments