From: Sathya Perla <sathya.perla@emulex.com>
To: <netdev@vger.kernel.org>
Subject: [PATCH net-next 00/12] be2net: patch set
Date: Fri, 19 Sep 2014 15:46:50 +0530 [thread overview]
Message-ID: <1411121822-25842-1-git-send-email-sathya.perla@emulex.com> (raw)
Patches 1 and 2 fix sparse warnings (static declaration needed and endian
declaration needed) introduced by the earlier patch set.
Patches 3 and 4 add 20G/40G speed reporting via ethtool for the Skyhawk-R
chip.
Patches 5 to 12 fix various style issues and checkpatch warnings in the
driver such as:
- removing unnecessary return statements in void routines
- adding needed blank lines after a declaration block
- deleting multiple blank lines
- inserting a blank line after a function/struct definition
- removing space after typecast
- fixing multiple assignments on a single line
- fixing alignment on a line wrap
Please consider applying this patch set to the net-next tree. Thanks!
Kalesh AP (10):
be2net: fix a sparse warning in be_cmd_modify_eqd()
be2net: add speed reporting for 40G/KR interface
be2net: remove return statements for void functions
be2net: add blank line after declarations
be2net: remove multiple blank lines
be2net: insert a blank line after function/struct//enum definitions
be2net: remove unnecessary blank lines after an open brace
be2net: remove space after typecasts
be2net: remove multiple assignments on a single line
be2net: fix alignment on line wrap
Suresh Reddy (1):
be2net: fix sparse warnings in be_cmd_req_port_type{}
Vasundhara Volam (1):
be2net: add speed reporting for 20G-KR interface
next reply other threads:[~2014-09-19 10:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-19 10:16 Sathya Perla [this message]
2014-09-19 10:16 ` [PATCH net-next 01/12] be2net: fix a sparse warning in be_cmd_modify_eqd() Sathya Perla
2014-09-19 10:16 ` [PATCH net-next 02/12] be2net: fix sparse warnings in be_cmd_req_port_type{} Sathya Perla
2014-09-19 10:16 ` [PATCH net-next 03/12] be2net: add speed reporting for 40G/KR interface Sathya Perla
2014-09-19 10:16 ` [PATCH net-next 04/12] be2net: add speed reporting for 20G-KR interface Sathya Perla
2014-09-19 10:16 ` [PATCH net-next 05/12] be2net: remove return statements for void functions Sathya Perla
2014-09-19 10:16 ` [PATCH net-next 06/12] be2net: add blank line after declarations Sathya Perla
2014-09-19 10:16 ` [PATCH net-next 07/12] be2net: remove multiple blank lines Sathya Perla
2014-09-19 10:16 ` [PATCH net-next 08/12] be2net: insert a blank line after function/struct//enum definitions Sathya Perla
2014-09-19 10:16 ` [PATCH net-next 09/12] be2net: remove unnecessary blank lines after an open brace Sathya Perla
2014-09-19 10:17 ` [PATCH net-next 10/12] be2net: remove space after typecasts Sathya Perla
2014-09-19 10:17 ` [PATCH net-next 11/12] be2net: remove multiple assignments on a single line Sathya Perla
2014-09-19 10:17 ` [PATCH net-next 12/12] be2net: fix alignment on line wrap Sathya Perla
2014-09-22 19:01 ` [PATCH net-next 00/12] be2net: patch set David Miller
-- strict thread matches above, loose matches on Subject: below --
2014-09-01 6:24 Sathya Perla
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=1411121822-25842-1-git-send-email-sathya.perla@emulex.com \
--to=sathya.perla@emulex.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).