All of lore.kernel.org
 help / color / mirror / Atom feed
From: Briana Oursler <briana.oursler@gmail.com>
To: gregkh@linuxfoundation.org, forest@alittletooquiet.net,
	julia.lawall@inria.fr, outreachy-kernel@googlegroups.com
Cc: Briana Oursler <briana.oursler@gmail.com>
Subject: [PATCH 0/4] staging: vt6655: Simplify statement logic.
Date: Sun, 29 Mar 2020 21:47:58 -0700	[thread overview]
Message-ID: <cover.1585542564.git.briana.oursler@gmail.com> (raw)

Reduce code duplication and complexity within switch case statement. The
goal is to improve the readability of the statement so that the outcome
of the statement is more clear. Checkpatch identified long lines and
other formatting issues within some nested logic. The last commit in this
patch series addresses checkpatch warnings that were not fixed by other
means within the series. Some long lines were left under the rationale
that removing them rendered the output more confusing. 

Briana Oursler (4):
  Staging: vt6655: Limit return statements.
  Staging: vt6655: Raise rate determination logic.
  Staging: vt6655: Create new variable len.
  Staging: vt6655: Format spaces.

 drivers/staging/vt6655/rxtx.c | 118 +++++++++++++++++-----------------
 1 file changed, 58 insertions(+), 60 deletions(-)

-- 
2.24.1



             reply	other threads:[~2020-03-30  4:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-30  4:47 Briana Oursler [this message]
2020-03-30  4:47 ` [PATCH 1/4] Staging: vt6655: Limit return statements Briana Oursler
2020-03-30 18:01   ` [Outreachy kernel] " Stefano Brivio
2020-03-30  4:48 ` [PATCH 2/4] Staging: vt6655: Raise rate determination logic Briana Oursler
2020-03-30 18:02   ` [Outreachy kernel] " Stefano Brivio
2020-03-30  4:48 ` [PATCH 3/4] Staging: vt6655: Create new variable len Briana Oursler
2020-03-30 18:03   ` [Outreachy kernel] " Stefano Brivio
2020-03-30  4:48 ` [PATCH 4/4] Staging: vt6655: Format spaces Briana Oursler
2020-03-30 18:02   ` [Outreachy kernel] " Stefano Brivio

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=cover.1585542564.git.briana.oursler@gmail.com \
    --to=briana.oursler@gmail.com \
    --cc=forest@alittletooquiet.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=julia.lawall@inria.fr \
    --cc=outreachy-kernel@googlegroups.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.