From: "Gustavo A. R. Silva" <garsilva@embeddedor.com>
To: linux-hams@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: "David S. Miller" <davem@davemloft.net>,
Ralf Baechle <ralf@linux-mips.org>, walter harms <wharms@bfs.de>,
Kevin Dawson <hal@kd.net.au>,
"Gustavo A. R. Silva" <garsilva@embeddedor.com>
Subject: [PATCH v3 0/2] refactor code and mark expected switch fall-throughs
Date: Fri, 27 Oct 2017 00:50:57 -0500 [thread overview]
Message-ID: <cover.1509080630.git.garsilva@embeddedor.com> (raw)
In-Reply-To: <20171022203942.Horde.vHHdAHmZbpcBFTJEP0yIy9k@gator4166.hostgator.com>
The aim of this patchset is firstly to refactor code in nr_route.c in order to make it
easier to read and maintain and, secondly, to mark some expected switch fall-throughs
in preparation to enabling -Wimplicit-fallthrough.
I have to mention that I did not implement any unit test.
If someone has any suggestions on how I could test this piece of code
it'd be greatly appreciated.
Thanks
Changes in v2:
- Make use of the swap macro and remove inline keyword as suggested by
Walter Harms and Kevin Dawson.
Changes in v3:
- Update subject for both patches.
- Add this cover letter as suggested by David Miller.
Gustavo A. R. Silva (2):
net: netrom: nr_route: refactor code in nr_add_node
net: netrom: nr_route: mark expected switch fall-throughs
net/netrom/nr_route.c | 62 ++++++++++++++++-----------------------------------
1 file changed, 19 insertions(+), 43 deletions(-)
--
2.7.4
next prev parent reply other threads:[~2017-10-27 5:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-19 17:21 [PATCH 1/2] net: netrom: mark expected switch fall-throughs Gustavo A. R. Silva
2017-10-19 17:27 ` [PATCH 2/2] net: netrom: refactor code in nr_add_node Gustavo A. R. Silva
2017-10-20 8:57 ` walter harms
2017-10-20 16:06 ` Gustavo A. R. Silva
2017-10-20 16:54 ` walter harms
2017-10-20 23:09 ` Kevin Dawson
2017-10-23 0:41 ` Gustavo A. R. Silva
2017-10-23 1:08 ` [PATCH v2 " Gustavo A. R. Silva
2017-10-23 1:18 ` David Miller
2017-10-23 1:39 ` Gustavo A. R. Silva
2017-10-27 5:50 ` Gustavo A. R. Silva [this message]
2017-10-27 5:51 ` [PATCH v3 1/2] net: netrom: nr_route: " Gustavo A. R. Silva
2017-10-27 5:51 ` [PATCH v3 2/2] net: netrom: nr_route: mark expected switch fall-throughs Gustavo A. R. Silva
2017-10-27 14:47 ` [PATCH v3 0/2] refactor code and " David Ranch
2017-10-27 19:48 ` Gustavo A. R. Silva
2017-10-28 17:53 ` David Ranch
2017-10-29 1:45 ` David Miller
2017-10-29 4:15 ` David Ranch
2017-11-08 22:02 ` f6bvp
2017-11-01 11:46 ` David Miller
2017-11-01 17:34 ` Gustavo A. R. Silva
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.1509080630.git.garsilva@embeddedor.com \
--to=garsilva@embeddedor.com \
--cc=davem@davemloft.net \
--cc=hal@kd.net.au \
--cc=linux-hams@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ralf@linux-mips.org \
--cc=wharms@bfs.de \
/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).