From: Greg KH <gregkh@linuxfoundation.org>
To: Jarrett Knauer <jrtknauer@gmail.com>
Cc: manishc@marvell.com, GR-Linux-NIC-Dev@marvell.com,
netdev@vger.kernel.org
Subject: Re: [PATCH 00/10] qlge.h cleanup - first pass
Date: Tue, 10 Mar 2020 10:49:20 +0100 [thread overview]
Message-ID: <20200310094920.GA2516963@kroah.com> (raw)
In-Reply-To: <cover.1583647891.git.jrtknauer@gmail.com>
On Sat, Mar 07, 2020 at 11:23:14PM -0700, Jarrett Knauer wrote:
> This patchset cleans up some warnings and checks issued by checkpatch.pl
> for staging: qlge: qlge.h as an effort to eventually bring the qlge TODO
> count to zero.
>
> There are still many CHECKs and WARNINGs for qlge.h, of which some are
> false-positives or odd instances which I plan on returning to after
> getting some more experience with the driver.
>
> Jarrett Knauer (10):
> staging: qlge: removed leading spaces identified by checkpatch.pl
> staging: qlge: checkpatch.pl CHECK - removed unecessary blank line
> staging: qlge: checkpatch.pl WARNING - removed spaces before tabs
> staging: qlge: checkpatch.pl CHECK - added spaces around /
> staging: qlge: checkpatch.pl WARNING - removed spaces before tabs
> staging: qlge: checkpatch.pl CHECK - added spaces around %
> staging: qlge: checkpatch.pl CHECK - removed blank line following
> brace
> staging: qlge: checkpatch.pl CHECK - removed blank line after brace
> staging: qlge: checkpatch.pl WARNING - removed function pointer space
> staging: qlge: checkpatch.pl WARNING - missing blank line
>
> drivers/staging/qlge/qlge.h | 42 ++++++++++++++++++-------------------
> 1 file changed, 20 insertions(+), 22 deletions(-)
I only received 8 of these patches :(
Can you please fix up and resend all of them?
thanks,
greg k-h
prev parent reply other threads:[~2020-03-10 9:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-08 6:23 [PATCH 00/10] qlge.h cleanup - first pass Jarrett Knauer
2020-03-09 6:18 ` Benjamin Poirier
2020-03-10 9:49 ` Greg KH [this message]
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=20200310094920.GA2516963@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=GR-Linux-NIC-Dev@marvell.com \
--cc=jrtknauer@gmail.com \
--cc=manishc@marvell.com \
--cc=netdev@vger.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;
as well as URLs for NNTP newsgroup(s).