All of lore.kernel.org
 help / color / mirror / Atom feed
From: Manikishan Ghantasala <manikishanghantasala@gmail.com>
Cc: manikishanghantasala@gmail.com,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Michael Straube <straube.linux@gmail.com>,
	linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] staging: rtl8192u: r8192U_hw.h: fix checkpatch.pl reports
Date: Thu,  3 Jun 2021 01:03:29 +0530	[thread overview]
Message-ID: <20210602193334.11687-1-manikishanghantasala@gmail.com> (raw)

This patch series fixes all checkpatch.pl errors, warnings an some checks
on the file drivers/staging/rtl8192u/r8192U_hw.h

checkpatch.pl tail output before patches:
total: 4 errors, 1 warnings, 32 checks, 247 lines checked
checkpatch.pl tail outputt after patches:
total: 0 errors, 0 warnings, 8 checks, 246 lines checked


Manikishan Ghantasala (3):
  staging: rtl8192u: r8192U_hw.h: fix spaces preferred around that '|'
    code style error
  staging: rtl8192u: put parentheses on macros with complex values in
    r8192U_hw.h
  staging: rtl8192u: fix spaces in r8192U_hw.h

 drivers/staging/rtl8192u/r8192U_hw.h | 19 +++++++++----------
 1 file changed, 9 insertions(+), 10 deletions(-)

-- 
2.25.1


WARNING: multiple messages have this Message-ID (diff)
From: Manikishan Ghantasala <manikishanghantasala@gmail.com>
To: unlisted-recipients:; (no To-header on input)
Cc: manikishanghantasala@gmail.com,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Michael Straube <straube.linux@gmail.com>,
	linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] staging: rtl8192u: r8192U_hw.h: fix checkpatch.pl reports
Date: Thu,  3 Jun 2021 01:03:29 +0530	[thread overview]
Message-ID: <20210602193334.11687-1-manikishanghantasala@gmail.com> (raw)

This patch series fixes all checkpatch.pl errors, warnings an some checks
on the file drivers/staging/rtl8192u/r8192U_hw.h

checkpatch.pl tail output before patches:
total: 4 errors, 1 warnings, 32 checks, 247 lines checked
checkpatch.pl tail outputt after patches:
total: 0 errors, 0 warnings, 8 checks, 246 lines checked


Manikishan Ghantasala (3):
  staging: rtl8192u: r8192U_hw.h: fix spaces preferred around that '|'
    code style error
  staging: rtl8192u: put parentheses on macros with complex values in
    r8192U_hw.h
  staging: rtl8192u: fix spaces in r8192U_hw.h

 drivers/staging/rtl8192u/r8192U_hw.h | 19 +++++++++----------
 1 file changed, 9 insertions(+), 10 deletions(-)

-- 
2.25.1


             reply	other threads:[~2021-06-02 19:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-02 19:33 Manikishan Ghantasala [this message]
2021-06-02 19:33 ` [PATCH 0/3] staging: rtl8192u: r8192U_hw.h: fix checkpatch.pl reports Manikishan Ghantasala
2021-06-02 19:33 ` [PATCH 1/3] staging: rtl8192u: r8192U_hw.h: fix spaces preferred around that '|' code style error Manikishan Ghantasala
2021-06-02 19:33   ` Manikishan Ghantasala
2021-06-02 19:33 ` [PATCH 2/3] staging: rtl8192u: put parentheses on macros with complex values in r8192U_hw.h Manikishan Ghantasala
2021-06-02 19:33   ` Manikishan Ghantasala
2021-06-02 19:33 ` [PATCH 3/3] staging: rtl8192u: fix spaces " Manikishan Ghantasala
2021-06-02 19:33   ` Manikishan Ghantasala

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=20210602193334.11687-1-manikishanghantasala@gmail.com \
    --to=manikishanghantasala@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=straube.linux@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.