From: Greg KH <gregkh@linuxfoundation.org>
To: "Frank A. Cancio Bello" <frank@generalsoftwareinc.com>
Cc: William Hubbs <w.d.hubbs@gmail.com>,
Chris Brannon <chris@the-brannons.com>,
Kirk Reiser <kirk@reisers.ca>,
Samuel Thibault <samuel.thibault@ens-lyon.org>,
outreachy-kernel@googlegroups.com,
saiprakash.ranjan@codeaurora.org, joel@joelfernandes.org
Subject: Re: [Outreachy kernel] [PATCH] staging: speakup: Fix multiple assignments on a single line
Date: Sun, 27 Oct 2019 08:13:10 +0100 [thread overview]
Message-ID: <20191027071310.GC1704509@kroah.com> (raw)
In-Reply-To: <20191027050640.GA24283@linux-kernel-dev>
On Sun, Oct 27, 2019 at 05:06:40AM +0000, Frank A. Cancio Bello wrote:
> checkpatch message: "multiple assignments should be avoided"
>
> Signed-off-by: Frank A. Cancio Bello <frank@generalsoftwareinc.com>
> ---
>
> This is the second patch that I send for "Outreachy December 2019 to
> March 2020".
>
> drivers/staging/speakup/main.c | 21 ++++++++++++++-------
> 1 file changed, 14 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/staging/speakup/main.c b/drivers/staging/speakup/main.c
> index 488f2539aa9a..6f5a58bd1f81 100644
> --- a/drivers/staging/speakup/main.c
> +++ b/drivers/staging/speakup/main.c
> @@ -263,9 +263,12 @@ static unsigned char get_attributes(struct vc_data *vc, u16 *pos)
>
> static void speakup_date(struct vc_data *vc)
> {
> - spk_x = spk_cx = vc->vc_x;
> - spk_y = spk_cy = vc->vc_y;
> - spk_pos = spk_cp = vc->vc_pos;
> + spk_cx = vc->vc_x;
> + spk_x = spk_cx;
> + spk_cy = vc->vc_y;
> + spk_y = spk_cy;
> + spk_cp = vc->vc_pos;
> + spk_pos = spk_cp;
As Julia said, the original is better here.
thanks,
greg k-h
next prev parent reply other threads:[~2019-10-27 7:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-27 5:06 [PATCH] staging: speakup: Fix multiple assignments on a single line Frank A. Cancio Bello
2019-10-27 5:35 ` [Outreachy kernel] " Julia Lawall
2019-10-27 7:13 ` Greg KH [this message]
2019-10-27 11:10 ` Samuel Thibault
2019-10-28 2:11 ` Frank A. Cancio Bello
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=20191027071310.GC1704509@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=chris@the-brannons.com \
--cc=frank@generalsoftwareinc.com \
--cc=joel@joelfernandes.org \
--cc=kirk@reisers.ca \
--cc=outreachy-kernel@googlegroups.com \
--cc=saiprakash.ranjan@codeaurora.org \
--cc=samuel.thibault@ens-lyon.org \
--cc=w.d.hubbs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.