From: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
To: Gold Side <goldside000@outlook.com>,
"krzk@kernel.org" <krzk@kernel.org>,
"perex@perex.cz" <perex@perex.cz>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"kernel-janitors@vger.kernel.org"
<kernel-janitors@vger.kernel.org>,
"linux-sound@vger.kernel.org" <linux-sound@vger.kernel.org>
Subject: Re: [PATCH 1/3] Removed extra asterisks from comment beginnings, and removed unnecessary comment end
Date: Sun, 7 Jul 2024 07:29:49 +0200 [thread overview]
Message-ID: <7635709f-9974-4c60-9cb0-78ae7f007cc2@wanadoo.fr> (raw)
In-Reply-To: <DM4P223MB0541357D7B105C83EF9FCFD5F7D92@DM4P223MB0541.NAMP223.PROD.OUTLOOK.COM>
Le 07/07/2024 à 06:14, Gold Side a écrit :
> From 3574f0514207f9610a69d82d3dd0d018d6dce5dd Mon Sep 17 00:00:00 2001
> From: Steven Davis <goldside000@outlook.com>
> Date: Tue, 2 Jul 2024 22:57:24 -0400
> Subject: [PATCH 1/3] Removed extra asterisk from comment beginning
>
> It saves a byte. I'd imagine bytes are valuable in a project like this.
> PS: Please forgive my previous patch email, I didn't know the guidelines well.
Hi,
no-problem, newcomers are always welcomed and they have to learn. So,
IMHO, making small mistakes is part of the learning curve.
People/mailing-list should be defined according to the MAINTAINERS file.
A script helps you for that: ./scripts/get_maintainer.pl
It can be run either on a patch or on a file/directory.
Here:
./scripts/get_maintainer.pl -f kernel/module/main.c
or
./scripts/get_maintainer.pl your_patch.patch
give:
Luis Chamberlain <mcgrof@kernel.org> (maintainer:MODULE SUPPORT)
linux-modules@vger.kernel.org (open list:MODULE SUPPORT)
linux-kernel@vger.kernel.org (open list:MODULE SUPPORT)
It is perfectly fine to add other people/mailing list that are relevant,
as kernel-janitor.
If you are using git mail, it is possible to automate the creation of
the To: and cc: fields. (see
https://www.marcusfolkesson.se/blog/get_maintainers-and-git-send-email/).
If using this --identify, you still can add some other --to, --cc.,
which is really convenient.
On your commit log, here are a few comments:
- there should be a new-line before the Signed-off-by: line
- you can add whatever you want after the --- ending the commit
description. These extra comments are informational only, and won't be
part of the git history. Here, your PS should have been here.
- imperative wording is preferred when writing commit logs
You can also give a look at
https://www.kernel.org/doc/html/latest/process/submitting-patches.html,
if not already done.
Welcome and happy patching :)
CJ
> Signed-off-by: Steven Davis <goldside000@outlook.com
> ---
> kernel/module/main.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/kernel/module/main.c b/kernel/module/main.c
> index d18a94b973e102..25e456f4381c71 100644
> --- a/kernel/module/main.c
> +++ b/kernel/module/main.c
> @@ -450,7 +450,7 @@ bool __is_module_percpu_address(unsigned long addr, unsigned long *can_addr)
> return false;
> }
>
> -/**
> +/*
> * is_module_percpu_address() - test whether address is from module static percpu
> * @addr: address to test
> *
prev parent reply other threads:[~2024-07-07 5:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-07 4:14 Gold Side
2024-07-07 4:49 ` Randy Dunlap
2024-07-07 5:29 ` Christophe JAILLET [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7635709f-9974-4c60-9cb0-78ae7f007cc2@wanadoo.fr \
--to=christophe.jaillet@wanadoo.fr \
--cc=goldside000@outlook.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®