Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix typo. #6

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Fix typo. #6

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
aff7dc0
Fix typo.
naviji Feb 17, 2021
465a988
Update message.md
naviji Feb 18, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion message.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -73,7 +73,7 @@ You can check that your email has been received by checking the mailing list arc

Then, you keep waiting. Three things may happen:

* You might get a response to your email. Often these will be comments, which may require you to make changes to your patch, or explain why your way is the best way. You should respond to these comments, and you may need to submit another revision of your patch to address the issues raised.
* You might get a response to your email. Often these will be comments, which may require you to make changes to your patch. You might be asked to explain why your way is the best. You should respond to these comments, and you may need to submit another revision of your patch to address the issues raised.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* You might get a response to your email. Often these will be comments, which may require you to make changes to your patch. You might be asked to explain why your way is the best. You should respond to these comments, and you may need to submit another revision of your patch to address the issues raised.
* You might get a response to your email. Often these will be comments, which may require you to make changes to your patch. You also might be asked to explain why your way is the best. You should respond to these comments, and you may need to submit another revision of your patch to address the issues raised.

* Your patch might be merged into the subsystem tree. Code that becomes part of Linux isn't merged into the main repository straight away - it first goes into the subsystem tree, which is managed by the subsystem maintainer. It is then batched up with a number of other changes sent to Linus for inclusion. (This process is described in some detail in [the kernel development process guide](https://www.kernel.org/doc/html/latest/process/development-process.html)).
* Your patch might be ignored completely. This happens sometimes - don't take it personally. Here's what to do:
* Wait a bit more - patches often take several weeks to get a response; more if they were sent at a busy time.
Expand Down