All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Javier F. Arias" <jarias.linux@gmail.com>
To: gregkh@linuxfoundation.org
Cc: outreachy-kernel@googlegroups.com
Subject: [PATCH v2 0/7] staging: rtl8723bs: Clean-up in rtw_security.c
Date: Wed, 16 Oct 2019 23:01:05 -0500	[thread overview]
Message-ID: <cover.1571284318.git.jarias.linux@gmail.com> (raw)

This patchset would improve the formatting, style and remove
unnecessary code. 

v2: Reworked the "Add spaces between operators" commit to add a missing
    line noticed by Julia Lawall <julia.lawall@lip6.fr>
    Added a commit to change tabs for spaces as suggested by
    Julia Lawall <julia.lawall@lip6.fr>

Javier F. Arias (7):
  staging: rtl8723bs: Replace string with identifier
  staging: rtl8723bs: Fix lines over 80 characters
  staging: rtl8723bs: Add spaces between operators
  staging: rtl8723bs: Remove commented code
  staging: rtl8723bs: Fix indentation warnings
  staging: rtl8723bs: Fix function call format
  staging: rtl8723bs: Change tabs for spaces

 drivers/staging/rtl8723bs/core/rtw_security.c | 135 ++++++++----------
 1 file changed, 57 insertions(+), 78 deletions(-)

-- 
2.20.1



             reply	other threads:[~2019-10-17  4:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-17  4:01 Javier F. Arias [this message]
2019-10-17  4:01 ` [PATCH v2 1/7] staging: rtl8723bs: Replace string with identifier Javier F. Arias
2019-10-17  4:02 ` [PATCH v2 2/7] staging: rtl8723bs: Fix lines over 80 characters Javier F. Arias
2019-10-17  4:02 ` [PATCH v2 3/7] staging: rtl8723bs: Add spaces between operators Javier F. Arias
2019-10-17  4:03 ` [PATCH v2 4/7] staging: rtl8723bs: Remove commented code Javier F. Arias
2019-10-17  4:03 ` [PATCH v2 5/7] staging: rtl8723bs: Fix indentation warnings Javier F. Arias
2019-10-17  4:04 ` [PATCH v2 6/7] staging: rtl8723bs: Fix function call format Javier F. Arias
2019-10-17  4:05 ` [PATCH v2 7/7] staging: rtl8723bs: Change tabs for spaces Javier F. Arias

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.1571284318.git.jarias.linux@gmail.com \
    --to=jarias.linux@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --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.