From: Joe Perches <joe@perches.com>
To: carlosteniswarrior@gmail.com, gregkh@linuxfoundation.org
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: kernel: user: fixed some coding style issues
Date: Sat, 11 Apr 2020 12:53:57 -0700 [thread overview]
Message-ID: <aef59a0b1364b0058a183f0e913a828b1b80f1b8.camel@perches.com> (raw)
In-Reply-To: <20200411194242.11336-1-carlosteniswarrior@gmail.com>
On Sat, 2020-04-11 at 21:42 +0200, carlosteniswarrior@gmail.com wrote:
> From: porfavorde <carlosteniswarrior@gmail.com>
Hello.
> Fixed a coding style issue with a for loop and a trailing whitespace in
> the comments
>
> Signed-off-by: Carlos Guerrero Álvarez <carlosteniswarrior@gmail.com>
A From: line is generally used when sending a patch authored
by someone else.
It would be better here not to use a From: line at all as you
are both the author and sender.
Also please make your first patch somewhere in drivers/staging
and not any other directory until you are familiar with the
kernel styles and tools. kernel/ isn't really a good place
for a first patch to be accepted, though I don't see anything
wrong with this patch other than the From: line.
But whitespace only changes outside of drivers/staging and a
few other directories are generally not accepted unless sent
as a patch series along with some other change such as
refactoring or a logical change for a defect.
cheers, Joe
---
> kernel/user.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/kernel/user.c b/kernel/user.c
> index 5235d7f49982..4228ec04678d 100644
> --- a/kernel/user.c
> +++ b/kernel/user.c
> @@ -6,7 +6,7 @@
> *
> * We have a per-user structure to keep track of how many
> * processes, files etc the user has claimed, in order to be
> - * able to have per-user limits for system resources.
> + * able to have per-user limits for system resources.
> */
>
> #include <linux/init.h>
> @@ -216,7 +216,7 @@ static int __init uid_cache_init(void)
> uid_cachep = kmem_cache_create("uid_cache", sizeof(struct user_struct),
> 0, SLAB_HWCACHE_ALIGN|SLAB_PANIC, NULL);
>
> - for(n = 0; n < UIDHASH_SZ; ++n)
> + for (n = 0; n < UIDHASH_SZ; ++n)
> INIT_HLIST_HEAD(uidhash_table + n);
>
> /* Insert the root user immediately (init already runs as root) */
prev parent reply other threads:[~2020-04-11 19:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-11 19:42 carlosteniswarrior
2020-04-11 19:53 ` Joe Perches [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=aef59a0b1364b0058a183f0e913a828b1b80f1b8.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=carlosteniswarrior@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
/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®