From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Rohit Chavan <roheetchavan@gmail.com>
Cc: Martyn Welch <martyn@welchs.me.uk>,
Manohar Vanga <manohar.vanga@gmail.com>,
linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev
Subject: Re: [PATCH] staging: vme_user: Fixing coding style issues reported by checkpatch
Date: Thu, 23 Mar 2023 05:55:21 +0100 [thread overview]
Message-ID: <ZBvbufoYo/wPp4qY@kroah.com> (raw)
In-Reply-To: <20230322142923.723-1-roheetchavan@gmail.com>
On Wed, Mar 22, 2023 at 07:59:23PM +0530, Rohit Chavan wrote:
> Fixing alignment should match open parenthesis issue on multiple lines,
> reported by checkpatch script.
You might want to mention on the subject line that this is a parenthesis
issue, right?
> Signed-off-by: Rohit Chavan <roheetchavan@gmail.com>
> ---
> drivers/staging/vme_user/vme_tsi148.c | 102 +++++++++++++-------------
> 1 file changed, 51 insertions(+), 51 deletions(-)
>
> diff --git a/drivers/staging/vme_user/vme_tsi148.c b/drivers/staging/vme_user/vme_tsi148.c
> index 2f5eafd50934..716de1d7fe21 100644
> --- a/drivers/staging/vme_user/vme_tsi148.c
> +++ b/drivers/staging/vme_user/vme_tsi148.c
> @@ -55,14 +55,14 @@ static struct pci_driver tsi148_driver = {
> };
>
> static void reg_join(unsigned int high, unsigned int low,
> - unsigned long long *variable)
> + unsigned long long *variable)
For many of these, you can just move the line to the previous one,
making it a single line, right? That would make the code much more
readable.
thanks,
greg k-h
prev parent reply other threads:[~2023-03-23 4:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 14:29 [PATCH] staging: vme_user: Fixing coding style issues reported by checkpatch Rohit Chavan
2023-03-23 4:55 ` Greg Kroah-Hartman [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=ZBvbufoYo/wPp4qY@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=manohar.vanga@gmail.com \
--cc=martyn@welchs.me.uk \
--cc=roheetchavan@gmail.com \
/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