From: Greg KH <gregkh@linuxfoundation.org>
To: Christopher Carbone <chris.m.carbone@gmail.com>
Cc: sudipm.mukherjee@gmail.com, teddy.wang@siliconmotion.com,
linux-fbdev@vger.kernel.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: sm750fb: split multiple assignments to lines
Date: Tue, 23 Aug 2022 08:26:44 +0200 [thread overview]
Message-ID: <YwRzJN5yORAtq8md@kroah.com> (raw)
In-Reply-To: <YwQGaLoBHH9C0aXN@valhalla>
On Mon, Aug 22, 2022 at 06:42:48PM -0400, Christopher Carbone wrote:
> Adhere to Linux kernel coding style.
>
> Reported by checkpatch:
>
> CHECK: multiple assignmentst should be avoided
>
> Signed-off-by: Christopher Carbone <chris.m.carbone@gmail.com>
> ---
> drivers/staging/sm750fb/sm750.c | 12 ++++++++----
> 1 file changed, 8 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/staging/sm750fb/sm750.c b/drivers/staging/sm750fb/sm750.c
> index dbd1159a2ef0..6f4c31635cc4 100644
> --- a/drivers/staging/sm750fb/sm750.c
> +++ b/drivers/staging/sm750fb/sm750.c
> @@ -386,7 +386,8 @@ static int lynxfb_ops_set_par(struct fb_info *info)
>
> ret = lynxfb_set_color_offsets(info);
>
> - var->height = var->width = -1;
> + var->height = -1;
Odd spacing on this new line. Did you run your change through
checkpatch?
Also, this is a new version of a previously-submitted patch, it needs to
be called "v2", and the changes you made from v1 listed below the ---
line, as the documentation asks you to do.
Please fix this up and submit a v3.
thanks,
greg k-h
next prev parent reply other threads:[~2022-08-23 6:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-22 22:42 [PATCH] staging: sm750fb: split multiple assignments to lines Christopher Carbone
2022-08-23 6:26 ` Greg KH [this message]
2022-08-25 0:16 ` Chris Carbone
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=YwRzJN5yORAtq8md@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=chris.m.carbone@gmail.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=sudipm.mukherjee@gmail.com \
--cc=teddy.wang@siliconmotion.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