From: Horatiu Vultur <hvultur@gmail.com>
To: netdev@vger.kernel.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Cc: Horatiu Vultur <hvultur@gmail.com>
Subject: [PATCH] Fix partial warnings of checkpatch.pl for ipx_route.c
Date: Mon, 5 Mar 2018 20:19:23 +0100 [thread overview]
Message-ID: <1520277563-3825-1-git-send-email-hvultur@gmail.com> (raw)
Fix partial warnings of checkpatch.pl for ipx_route.c
Signed-off-by: Horatiu Vultur <hvultur@gmail.com>
---
drivers/staging/ipx/ipx_route.c | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/drivers/staging/ipx/ipx_route.c b/drivers/staging/ipx/ipx_route.c
index 3cf93aa9..bd26fbb 100644
--- a/drivers/staging/ipx/ipx_route.c
+++ b/drivers/staging/ipx/ipx_route.c
@@ -71,8 +71,8 @@ int ipxrtr_add_route(__be32 network, struct ipx_interface *intrfc,
goto out_put;
}
- rt->ir_net = network;
- rt->ir_intrfc = intrfc;
+ rt->ir_net = network;
+ rt->ir_intrfc = intrfc;
if (!node) {
memset(rt->ir_router_node, '\0', IPX_NODE_LEN);
rt->ir_routed = 0;
@@ -207,7 +207,7 @@ int ipxrtr_route_packet(struct sock *sk, struct sockaddr_ipx *usipx,
ipx = ipx_hdr(skb);
ipx->ipx_pktsize = htons(len + sizeof(struct ipxhdr));
IPX_SKB_CB(skb)->ipx_tctrl = 0;
- ipx->ipx_type = usipx->sipx_type;
+ ipx->ipx_type = usipx->sipx_type;
IPX_SKB_CB(skb)->last_hop.index = -1;
#ifdef CONFIG_IPX_INTERN
@@ -280,6 +280,7 @@ int ipxrtr_ioctl(unsigned int cmd, void __user *arg)
break;
case SIOCADDRT: {
struct ipx_route_definition f;
+
f.ipx_network = st->sipx_network;
f.ipx_router_network = sg->sipx_network;
memcpy(f.ipx_router_node, sg->sipx_node, IPX_NODE_LEN);
--
2.7.4
next reply other threads:[~2018-03-05 19:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-05 19:19 Horatiu Vultur [this message]
2018-03-05 19:23 ` [PATCH] Fix partial warnings of checkpatch.pl for ipx_route.c Eric Dumazet
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=1520277563-3825-1-git-send-email-hvultur@gmail.com \
--to=hvultur@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--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).