From: Petr Mladek <pmladek@suse.com>
To: mohitpawar@mitaoe.ac.in
Cc: yoann.congal@smile.fr, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 2/2] Fixed: Kernel: user_c: fixed whitespace & intendation errors
Date: Thu, 25 Jul 2024 10:05:27 +0200 [thread overview]
Message-ID: <ZqIHR9LDmp8bduyn@pathway.suse.cz> (raw)
In-Reply-To: <20240713174137.125978-1-mohitpawar@mitaoe.ac.in>
Adding Andrew into Cc who usually takes patches for core kernel code
without a dedicated maintainer.
On Sat 2024-07-13 23:11:37, mohitpawar@mitaoe.ac.in wrote:
> From: Mohit0404 <mohitpawar@mitaoe.ac.in>
>
> Resolved -
> ERROR: trailing whitespace
> ERROR: space required before the open parenthesis '('
> ---
> kernel/user.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/kernel/user.c b/kernel/user.c
> index aa1162deafe4..9e07264fd6f7 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>
> @@ -249,7 +249,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);
>
> if (user_epoll_alloc(&root_user))
> --
> 2.34.1
next prev parent reply other threads:[~2024-07-25 8:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-13 17:41 mohitpawar
2024-07-25 8:05 ` Petr Mladek [this message]
2024-07-25 20:57 ` Andrew Morton
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=ZqIHR9LDmp8bduyn@pathway.suse.cz \
--to=pmladek@suse.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mohitpawar@mitaoe.ac.in \
--cc=yoann.congal@smile.fr \
/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®