[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YKeUd/X5tuN54o1H@kroah.com>
Date: Fri, 21 May 2021 13:07:35 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: Aviral Gupta <shiv14112001@...il.com>
Cc: viro@...iv.linux.org.uk, shuah@...nal.org,
linux-fsdevel@...r.kernel.org,
linux-kernel-mentees@...ts.linuxfoundation.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] This commit fixes the error generated due to the wrong
indentation which does not follow the codding style norms set by
Linux-kernel and space- bar is used in place of tab to give space which
causes a visual error for some compilers
On Fri, May 21, 2021 at 04:26:54PM +0530, Aviral Gupta wrote:
> ERROR: switch and case should be at the same indent
> + switch (whence) {
> + case 1:
> [...]
> + case 0:
> [...]
> + default:
> ERROR: code indent should use tabs where possible
> + void (*callback)(struct dentry *))$
>
> Signed-off-by: Aviral Gupta <shiv14112001@...il.com>
> ---
> fs/libfs.c | 20 ++++++++++----------
> 1 file changed, 10 insertions(+), 10 deletions(-)
Your subject line is very odd.
And why are you trying to change coding style issues in core kernel
code?
Please start this type of work in drivers/staging/ where it is wanted,
not in other areas of the kernel where it is not good to try to learn
the process.
good luck!
greg k-h
Powered by blists - more mailing lists