grammar and spelling for mm/huge_memory.c

[mdeguzis]

No description provided.

[KernelPRBot]

Hi @mdeguzis!

Thanks for your contribution to the Linux kernel!

Linux kernel development happens on mailing lists, rather than on GitHub - this GitHub repository is a read-only mirror that isn't used for accepting contributions. So that your change can become part of Linux, please email it to us as a patch.

Sending patches isn't quite as simple as sending a pull request, but fortunately it is a well documented process.

Here's what to do:

• Format your contribution according to kernel requirements
• Decide who to send your contribution to
• Set up your system to send your contribution as an email
• Send your contribution and wait for feedback

How do I format my contribution?

The Linux kernel community is notoriously picky about how contributions are formatted and sent. Fortunately, they have documented their expectations.

Firstly, all contributions need to be formatted as patches. A patch is a plain text document showing the change you want to make to the code, and documenting why it is a good idea.

You can create patches with git format-patch.

Secondly, patches need 'commit messages', which is the human-friendly documentation explaining what the change is and why it's necessary.

Thirdly, changes have some technical requirements. There is a Linux kernel coding style, and there are licensing requirements you need to comply with.

Both of these are documented in the Submitting Patches documentation that is part of the kernel.

Note that you will almost certainly have to modify your existing git commits to satisfy these requirements. Don't worry: there are many guides on the internet for doing this.

Who do I send my contribution to?

The Linux kernel is composed of a number of subsystems. These subsystems are maintained by different people, and have different mailing lists where they discuss proposed changes.

If you don't already know what subsystem your change belongs to, the get_maintainer.pl script in the kernel source can help you.

get_maintainer.pl will take the patch or patches you created in the previous step, and tell you who is responsible for them, and what mailing lists are used. You can also take a look at the MAINTAINERS file by hand.

Make sure that your list of recipients includes a mailing list. If you can't find a more specific mailing list, then LKML - the Linux Kernel Mailing List - is the place to send your patches.

It's not usually necessary to subscribe to the mailing list before you send the patches, but if you're interested in kernel development, subscribing to a subsystem mailing list is a good idea. (At this point, you probably don't need to subscribe to LKML - it is a very high traffic list with about a thousand messages per day, which is often not useful for beginners.)

How do I send my contribution?

Use git send-email, which will ensure that your patches are formatted in the standard manner. In order to use git send-email, you'll need to configure git to use your SMTP email server.

For more information about using git send-email, look at the Git documentation or type git help send-email. There are a number of useful guides and tutorials about git send-email that can be found on the internet.

How do I get help if I'm stuck?

Firstly, don't get discouraged! There are an enormous number of resources on the internet, and many kernel developers who would like to see you succeed.

Many issues - especially about how to use certain tools - can be resolved by using your favourite internet search engine.

If you can't find an answer, there are a few places you can turn:

• Kernel Newbies - this website contains a lot of useful resources for new kernel developers.
• If you'd like a step-by-step, challenge-based introduction to kernel development, the Eudyptula Challenge would be an excellent start.
• The kernel documentation - see also the Documentation directory in the kernel tree.

If you get really, really stuck, you could try the owners of this bot, @daxtens and @ajdlinux. Please be aware that we do have full-time jobs, so we are almost certainly the slowest way to get answers!

I sent my patch - now what?

You wait.

You can check that your email has been received by checking the mailing list archives for the mailing list you sent your patch to. Messages may not be received instantly, so be patient. Kernel developers are generally very busy people, so it may take a few weeks before your patch is looked at.

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.
• 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).
• 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.
  • Kernel developers often silently ignore patches that break the rules. Check for obvious violations of the the Submitting Patches guidelines, the style guidelines, and any other documentation you can find about your subsystem. Check that you're sending your patch to the right place.
  • Try again later. When you resend it, don't add angry commentary, as that will get your patch ignored. It might also get you silently blacklisted.

Further information

• Working with the kernel development community - the official documentation for new kernel contributors

Happy hacking!

This message was posted by a bot - if you have any questions or suggestions, please talk to my owners, @ajdlinux and @daxtens, or raise an issue at https://github.com/ajdlinux/KernelPRBot.

[daxtens]

Hi Michael, This looks like a good contribution; if you would like any help getting it upstream please let me know. Regards, Daniel

…

On Wed, May 17, 2017 at 5:09 PM, Michael T. DeGuzis < ***@***.***> wrote: Closed #415 <#415>. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#415 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ADJ5BXJX3y-1LXhVKI-ZSnmqP6A6gBkRks5r6p0dgaJpZM4Nc6la> .

[mdeguzis]

@daxtens , sure, I have never made a contribution yet to the kernel, even this small. Either comment here, or contact me via whatever channel suits you best. I will start trying to follow https://www.kernel.org/doc/html/latest/process/submitting-patches.html listed above.

[mdeguzis]

I think I got it, configured git send-email, tested with my email first

Send this email? ([y]es|[n]o|[q]uit|[a]ll): y
OK. Log says:
Server: smtp.SERVER.com
MAIL FROM:<NAME@SERVER.com>
RCPT TO:<linux-mm@kvack.org>
RCPT TO:<trivial@kernel.org>
RCPT TO:<XXXXXX@XXXXXX.com>
From: FNAME LNAME <XXXXXX@XXXXXX.com>
To: linux-mm@kvack.org
Cc: trivial@kernel.org,
        mdeguzis <NAME@SERVER.com>
Subject: [PATCH] Correct spelling and grammar for notification text
Date: Wed, 17 May 2017 09:38:42 -0400
Message-Id: <20170517133842.5733-1-NAME@SERVER.com>
X-Mailer: git-send-email 2.12.2

[ajdlinux]

Hey @mdeguzis,

It looks like your git send-email worked: http://marc.info/?l=linux-mm&m=149502833306198&w=2. Woot!

A few things I noticed:

1. You should configure git to use your name in commits - "git config --global user.name "Michael DeGuzis"" should work, I think. Otherwise, git send-email will add "From: professorkaos64 mdeguzis@gmail.com" to your patch and the wrong name will end up in the changelog when it's applied.

2. Per step 11 in the submitting patches document, you need a Signed-off-by: [Name] <[Email]> line at the end of your commit message. The easiest way is to use git commit -s to automatically add one.

3. Your commit title should use the right prefix to identify the subsystem you're touching. There's not really an official standard for this - the best way to figure it out would be to run git log on the files you're touching and see what other people have used. In this case, I'd recommend thp: (or alternatively mm:) based on past usage.

When you resend the patch with git send-email use the -v2 --annotate options, which will mark it as version 2 of the patch, and open up an editor for you to edit the message before you send it. After the "---" line at the bottom of the commit message, you should add a quick note saying what you fixed between version 1 and version 2.

Feel free to Cc me (andrew.donnellan@au1.ibm.com) and @daxtens (dja@axtens.net) as well.

Welcome to the kernel community. :)

[mdeguzis]

I correct my ~/.gitconfig to include my full name. I fixed it from professorkaos64 (my older username) after this. I'll add git commit -s to my notes, thanks!.

Your commit title should use the right prefix to identify the subsystem you're touching

Ok, so I did that for the subject, but I missed it in the commit title. What is the "commit title" here?Would it be the "Merge Tag" line?

commit b23afd384801711ab6dbccd259cc14cb09a1dcaf
Merge: 2b6b38b04c2e 6f61dd3aa351
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue May 16 13:29:07 2017 -0700

    Merge tag 'pstore-v4.12-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux

    Pull pstore fix from Kees Cook:
     "Fix bad EFI vars iterator usage"

    * tag 'pstore-v4.12-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux:
      efi-pstore: Fix read iter after pstore API refactor

When you resend the patch with git send-email use the -v2 --annotate options, which will mark it as version 2 of the patch, and open up an editor for you to edit the message before you send it

Are you saying need to resend this particular patch? Should I just reply via Thunderbird/Mutt on any subsequent replies?

Welcome to the kernel community. :)

Well, I only know Python well, but maybe I'll get into C someday soon :)

[mdeguzis]

oh ok, I see to resend the patch with V2.. ok. i'll resend

[ajdlinux]

By "commit title" I meant the first line of your commit message, which git send-email converts into the subject line of the email. Sorry if I was unclear!

Yes, resend the patch after fixing up those issues. When you're sending a patch, use git send-email, but you can then use your normal email client for any discussion which happens in response.

[mdeguzis]

I removed extra space so I can do another git commit -s on this. However, if I was sending again, would I just use git-rebase to edit the commit?

I documented this previously in my documents repo:
https://github.com/mdeguzis/documents/blob/master/linux-applications/git/changing-commits.md

What's annoying though, is git commit -s adds the sign off at the top, which is then used as the subject. I placed that at the bottom.

[ajdlinux]

Yeah, use git rebase or git commit --amend to edit the commit.