Outreachy Linux Kernel Community
 help / color / mirror / Atom feed
From: Hunter Chasens <hunter.chasens18@ncf.edu>
To: outreachy@lists.linux.dev
Cc: johan@kernel.org, elder@kernel.org, gregkh@linuxfoundation.org,
	hvaibhav.linux@gmail.com, vireshk@kernel.org,
	pure.logic@nexus-software.ie,
	Hunter Chasens <hunter.chasens18@ncf.edu>
Subject: [PATCH v3 0/2] Staging: greybus: Code style cleanup
Date: Sun, 13 Nov 2022 22:26:44 -0500	[thread overview]
Message-ID: <cover.1668395762.git.hunter.chasens18@ncf.edu> (raw)

These two patches address some Errors, Warnings, and Checks reported 
by `./scripts/checkpatch.pl`

v1 -> v2
Separates the patch into a small patchset with the delimitation of syntactical
styling vs whitespace styling. (I plan on sending to the maintainers if 
Outreach thinks this is an appropriate patch.)
v2 -> v3
CCs maintainers.
I now know I should have CCed the maintainers from v1. I apologise for my error. 

Hunter Chasens (2):
  Staging: greybus: Whitespace cleanup
  Staging: greybus: Removes redundant 'int'

 .../Documentation/firmware/authenticate.c     |  4 +--
 .../greybus/Documentation/firmware/firmware.c | 34 +++++++++----------
 drivers/staging/greybus/arche-platform.c      |  2 +-
 .../staging/greybus/greybus_authentication.h  |  1 -
 drivers/staging/greybus/loopback.c            |  3 +-
 drivers/staging/greybus/tools/loopback_test.c | 16 +--------
 6 files changed, 22 insertions(+), 38 deletions(-)

-- 
2.38.1


             reply	other threads:[~2022-11-14  3:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-14  3:26 Hunter Chasens [this message]
2022-11-14  3:26 ` [PATCH v3 1/2] Staging: greybus: Whitespace cleanup Hunter Chasens
2022-11-14  3:37   ` Viresh Kumar
2022-11-14  7:20   ` Greg KH
2022-11-14  3:26 ` [PATCH v3 2/2] Staging: greybus: Removes redundant 'int' Hunter Chasens
2022-11-14  7:22   ` Greg KH

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.1668395762.git.hunter.chasens18@ncf.edu \
    --to=hunter.chasens18@ncf.edu \
    --cc=elder@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hvaibhav.linux@gmail.com \
    --cc=johan@kernel.org \
    --cc=outreachy@lists.linux.dev \
    --cc=pure.logic@nexus-software.ie \
    --cc=vireshk@kernel.org \
    /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